I just bought a G7 Plus on amazon for $122 which is produced in 11/05/2020 with the latest version of rom. Model XT1965-T
Currentlly, I already unlock the bootloader. I have installed the mokee rom and lineage os for more than 15 times.
The biggest issue is NO SERVICE on my phone. But the IMEI is exist. I can connect to wifi.
I also tried to flash the stock baseband which leads to IMEI 0.
Hope someone faced the same issue could helpe me to fix it.
Thank you very much.
I am faced with the same issue. Have you found the Motorola stock rom? Please let me know if have resolved this. I may buy another XT1965-T and save the stock rom from it.
I once had the same issue. Flashing the stock baseband is not enough. Your EFS is fckd and you probably have no backup.
You have to install the complete stock ROM again, reboot and see if your IMEI and stuff gets restored.
You can get the stock ROM from Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I dont know the correct folder for your 1965 model, this is the US version? Maybe the RETAIL folder?
Oh, there is an older version from LineageOS from November 2020 that works with cell network and does not kill the IMEI, you can get it from this thread: if you try this version, you may not need to flash the stock ROM.
LineageOS-17.1--2020-11-24
Tip:
Once you have your IMEI and cell network working again, you might try the command reboot nvbackup to have a backup created. And in case of losing IMEI and cell network again you might try reboot nvrestore.
I have only tried the reboot nvbackup so far, I have no experience with reboot nvrestore.
A good thread to learn about the EFS is there on xda:
efs-modemst-Guide
Learn about EFS. On Play Store there is an app that promises to create backups of the EFS, I dont know how reliable that tool is, never used, you can get it there:
wanam partitions backup tool
papperlapapp said:
I once had the same issue. Flashing the stock baseband is not enough. Your EFS is fckd and you probably have no backup.
You have to install the complete stock ROM again, reboot and see if your IMEI and stuff gets restored.
You can get the stock ROM from Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I dont know the correct folder for your 1965 model, this is the US version? Maybe the RETAIL folder?
Oh, there is an older version from LineageOS from November 2020 that works with cell network and does not kill the IMEI, you can get it from this thread: if you try this version, you may not need to flash the stock ROM.
LineageOS-17.1--2020-11-24
Tip:
Once you have your IMEI and cell network working again, you might try the command reboot nvbackup to have a backup created. And in case of losing IMEI and cell network again you might try reboot nvrestore.
I have only tried the reboot nvbackup so far, I have no experience with reboot nvrestore.
A good thread to learn about the EFS is there on xda:
efs-modemst-Guide
Learn about EFS. On Play Store there is an app that promises to create backups of the EFS, I dont know how reliable that tool is, never used, you can get it there:
wanam partitions backup tool
Click to expand...
Click to collapse
First off, that is the firmware that caused the trouble. It is for the T_Mobile version NOT the Motorola version. The only version for XT1965-T on lolinet is for T-Mobile. The version in the RETAIL directory does not boot at all.
i faced the same issue.
first install the new version of lineageOS 20210105, no servicer avilable.
then change to 20201124, it's ok.
youzi0335 said:
i faced the same issue.
first install the new version of lineageOS 20210105, no servicer avilable.
then change to 20201124, it's ok.
Click to expand...
Click to collapse
Sorry, still no WIfi or cell service.
bakshi12 said:
Sorry, still no WIfi or cell service.
Click to expand...
Click to collapse
maybe you can try to install copy Partitions AB.zip
=========================
Pre-install instructions
In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional.
To do this, sideload the copy-partitions-20200903_1329.zip package by doing the following:
Download the copy-partitions-20200903_1329.zip file from here.
Sideload the copy-partitions-20200903_1329.zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload copy-partitions-20200903_1329.zip
info_outline
NOTE: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz, but isn’t signed with LineageOS’s official key, and therefore when it is sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
===========================
I have already tired that. As a matter of fact I used that when I first loaded Lineage.
OK. I restored the XT1965-T (US Version) with stock firmware. The phone now works as stock, radio, WiFi, and all.
Here's what I did:
1) Bought an identical phone,
2) I did not unlock the bootloader on the new phone,
3) I used Rescue and Smart Assistant and did NOT register the phone,
4) I used Rescue mode and it correctly identified the device,
5) RSA allowed me to download the correct stock rom (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip),
6) I closed RSA and extracted the zipped file,
7) I converted the flashfile.xml to a batch file,
8) I ran the batch job and the phone rebooted as stock.
So, does anyone want the proper stock rom? I will send it to you if you have a server to host it on for other to download. Does anyone want to buy my extra Moto g7 Plus?
Below is the build info file for the rom.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPW30.61-21-18-7 86588 release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-201120
Build Fingerprint: motorola/lake/lake:10/QPW30.61-21-18-7/86588:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.301.10.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPW30.61-21-18-7
SW Display Build ID: QPW30.61-21-18-7
Build Date: Fri Nov 20 01:56:29 CST 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.301.10.lake.retail.en.US
Version when read from CPV: lake-user 10 QPW30.61-21-18-7 86588 release-keys
AB Update Enabled: True
Full Treble Enabled: True
good to see you got the stock rom, i just flashed the RETAIL rom on lolinet（LAKE_RETAIL_10_QPWS30.61-21-18-5） and it is work well.
I'm glad I'm not the only one who has had these problems. I have a moto g7 plus xt1965-T but the motorola version not the T-mobile version. I tried lineageos only to hard brick the phone on the first try. Still learning. Lol. I tried going back to stock only to find out the only one available was the T-mobile version. I would very much like to have a copy of the stock firmware but I am unable to put it on a server anywhere.
By the way, I am having the same problem as op no imei and WiFi not working.
Hillbillytech said:
By the way, I am having the same problem as op no imei and WiFi not working.
Click to expand...
Click to collapse
I will be glad to upload it to any server that will host it for anyone that wants it.
Did you find a way to make LineageOS work? It seems the LineageOS build is for the Revvlry+ so I tried to flash that ROM/firmware before installing LineageOS and still could not get wifi or cellular to work. Is there a way to swap in the required non T-Mobile version files into the LineageOS folder and then re-zip it for twrp insallation?
I got /e os working after I got the original Lenovo firmware reinstalled. That loaded the proper configs for radios. I then installed the /e os version from NOV20. That worked and so did the updates installed since. The T-Mobile XT1965-T firmware never worked on the Motorola version for some reason. All works fine now.
bakshi12 said:
OK. I restored the XT1965-T (US Version) with stock firmware. The phone now works as stock, radio, WiFi, and all.
Here's what I did:
1) Bought an identical phone,
2) I did not unlock the bootloader on the new phone,
3) I used Rescue and Smart Assistant and did NOT register the phone,
4) I used Rescue mode and it correctly identified the device,
5) RSA allowed me to download the correct stock rom (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip),
6) I closed RSA and extracted the zipped file,
7) I converted the flashfile.xml to a batch file,
8) I ran the batch job and the phone rebooted as stock.
So, does anyone want the proper stock rom? I will send it to you if you have a server to host it on for other to download. Does anyone want to buy my extra Moto g7 Plus?
Below is the build info file for the rom.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPW30.61-21-18-7 86588 release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-201120
Build Fingerprint: motorola/lake/lake:10/QPW30.61-21-18-7/86588:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.301.10.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPW30.61-21-18-7
SW Display Build ID: QPW30.61-21-18-7
Build Date: Fri Nov 20 01:56:29 CST 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.301.10.lake.retail.en.US
Version when read from CPV: lake-user 10 QPW30.61-21-18-7 86588 release-keys
AB Update Enabled: True
Full Treble Enabled: True
Click to expand...
Click to collapse
Can you show where that I can down load the firmware (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip). Thanks
bakshi12 said:
OK. I restored the XT1965-T (US Version) with stock firmware. The phone now works as stock, radio, WiFi, and all.
Here's what I did:
1) Bought an identical phone,
2) I did not unlock the bootloader on the new phone,
3) I used Rescue and Smart Assistant and did NOT register the phone,
4) I used Rescue mode and it correctly identified the device,
5) RSA allowed me to download the correct stock rom (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip),
6) I closed RSA and extracted the zipped file,
7) I converted the flashfile.xml to a batch file,
8) I ran the batch job and the phone rebooted as stock.
So, does anyone want the proper stock rom? I will send it to you if you have a server to host it on for other to download. Does anyone want to buy my extra Moto g7 Plus?
Below is the build info file for the rom.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPW30.61-21-18-7 86588 release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-201120
Build Fingerprint: motorola/lake/lake:10/QPW30.61-21-18-7/86588:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.301.10.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPW30.61-21-18-7
SW Display Build ID: QPW30.61-21-18-7
Build Date: Fri Nov 20 01:56:29 CST 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.301.10.lake.retail.en.US
Version when read from CPV: lake-user 10 QPW30.61-21-18-7 86588 release-keys
AB Update Enabled: True
Full Treble Enabled: True
Click to expand...
Click to collapse
I founf it on https://androidfilehost.com/?fid=17248734326145715796
bakshi12 said:
OK. I restored the XT1965-T (US Version) with stock firmware. The phone now works as stock, radio, WiFi, and all.
Here's what I did:
1) Bought an identical phone,
2) I did not unlock the bootloader on the new phone,
3) I used Rescue and Smart Assistant and did NOT register the phone,
4) I used Rescue mode and it correctly identified the device,
5) RSA allowed me to download the correct stock rom (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip),
...
Click to expand...
Click to collapse
Anybody has this newer version for XT1965-T by any chance:
LAKE_QPWS30.61-21-18-7-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I found it on some arabic sites, but they want me to login.
Edit: There is actually the latest ROM file in here:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This should be exactly what is needed for XT1965-T.
bakshi12 said:
OK. I restored the XT1965-T (US Version) with stock firmware. The phone now works as stock, radio, WiFi, and all.
Here's what I did:
1) Bought an identical phone,
2) I did not unlock the bootloader on the new phone,
3) I used Rescue and Smart Assistant and did NOT register the phone,
4) I used Rescue mode and it correctly identified the device,
5) RSA allowed me to download the correct stock rom (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip),
6) I closed RSA and extracted the zipped file,
7) I converted the flashfile.xml to a batch file,
8) I ran the batch job and the phone rebooted as stock.
So, does anyone want the proper stock rom? I will send it to you if you have a server to host it on for other to download. Does anyone want to buy my extra Moto g7 Plus?
Below is the build info file for the rom.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPW30.61-21-18-7 86588 release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-201120
Build Fingerprint: motorola/lake/lake:10/QPW30.61-21-18-7/86588:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.301.10.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPW30.61-21-18-7
SW Display Build ID: QPW30.61-21-18-7
Build Date: Fri Nov 20 01:56:29 CST 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.301.10.lake.retail.en.US
Version when read from CPV: lake-user 10 QPW30.61-21-18-7 86588 release-keys
AB Update Enabled: True
Full Treble Enabled: True
Click to expand...
Click to collapse
I have a server that is usually accessable that has plenty of storage space. I would host some files for download for the XDA. Bakshi 12 you can send me an email at [email protected]
I also have an email service of my own too.
Thanks for all the assistance! Worked for me!!!
1)Flashed the lastest frimware from https://mirrors.lolinet.com/firmware/motorola/lake/official/RETLA/
Boot your device into bootloader mode.
Connect your REVVLRY Plus XT1965-T to the PC using the USB Cable.
Download Stock ROM/Firmware and extract it inside the adb and fastboot folder
Inside the ADB folder, open the command window and enter the following command
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash dsp dspso.bin
fastboot flash bootloader bootloader.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase ddr
Now your device will reboot into bootloader with the firmware you installed.
2) Booted phone with the retail installed firmware and verfied LTE connection
3) Loaded LineageOS 19.1 for Moto G7 Plus
Follow LineageOS 19.1 installation guide on their website
4) Booteed LineagoOS 19.1, had no service
5) Reflashed modem firmware extractted from lastest retail firmware above:
Boot your device into bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
6) Working cellular connection, (LTE support)
Related
hi... it is my first time...i am ignorant about updating the ROM...
so I will write here my script...
I live in brazil, i have a lg-d410hn v20c, lollipop, dual sim and nfc...
according to IMEI in lg-phone-firmware.com:
Version: V20c
Country: BRA/BRAZIL
Model: LGD410HN
according my own phone:
android version: 5.0.2
baseband version: M862A-AAAANAZM-1.0.6063
kernel: 3.4.0+
model: LG-D410hn
montage number: LRX22G.A1440649755
software: V20c-SCA-XXX
1. general
1.1 root access (in my case, with kingroot)
1.2 enable USB debugging
1.3 install Terminal
1.4 install twrp recovery
2. backup
2.1 backup some important files ( http://forum.xda-developers.com/lg-l90/general/warning-d410hn-users-brazilian-dual-sim-t3223091 )
2.1.1 run in terminal:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/aboot.bin
dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=512 count=323583
3. unlock-bootloader
3.1 download and extract the appropriate version of aboot for my phone ( http://forum.xda-developers.com/showpost.php?p=63688084&postcount=12 )
3.2 extract this aboot.bin on root of an external sd
3.3 run this command on terminal
Code:
su
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3 twrp - backup actual rom
3.1 reboot with twrp recovery img
3.2 wipe dat: data system boot
3.3 backu rom to sd-card
4. cyanogenmod rom
4.1 wipe data: cache, data, system, interal
4.2 install from sd card
5. install http://opengapps.org/
it´s all ok... but... i have a problem in 3.1 step...
when i reboot, appears:
Secure booting Error! Cause: boot certification verify
i remove the battery, turn on the phone, and it works normally.
this message only appears when the phone restarts in recovery mode (with the volume down + the power button)
any ideas?
Nevermind.
someone?
Well, probably it matters the order you flash things. I have always rooted, then flashed unlocked bootloader first and only then TWRP using an app like Hashr. I would recommend that you flash stock kdz to go back to whatever ROM you were using before, test if 3G and Wi-Fi works, then root and start again (unlocked aboot and then TWRP). My guess is that flashing custom recovery with locked bootloader triggered some security measure, it seems...
lfom said:
Well, probably it matters the order you flash things. I have always rooted, then flashed unlocked bootloader first and only then TWRP using an app like Hashr. I would recommend that you flash stock kdz to go back to whatever ROM you were using before, test if 3G and Wi-Fi works, then root and start again (unlocked aboot and then TWRP). My guess is that flashing custom recovery with locked bootloader triggered some security measure, it seems...
Click to expand...
Click to collapse
thank you...
i did that... when was rooted, then i replace the aboot to the unlocked bootloader... and after i try to reboot with hashr...
where i can find the stock kdz for this model? lollipop 410hn v20c?
fluiz said:
thank you...
i did that... when was rooted, then i replace the aboot to the unlocked bootloader... and after i try to reboot with hashr...
where i can find the stock kdz for this model? lollipop 410hn v20c?
Click to expand...
Click to collapse
Search the forum, there is a thread to unroot/restore to factory, it has links to the kdz downloads IIRIC.
Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx
VooDooCC said:
Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx
Click to expand...
Click to collapse
It's entirely possible you are having some kind of hardware failure, but as we can't help you fix that let's focus on software for now.
Is your bootloader unlocked and do you have TWRP recovery? If you have TWRP, have you tried to restore any backups of your system?
Have you tried reflashing firmware, either lastest stock via ADB or custom ROM? (choice depending on whether your bootloader is unlocked or not)
bootloader is locked, everything is stock.
VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).
ChazzMatt said:
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).
Click to expand...
Click to collapse
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.
VooDooCC said:
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.
Click to expand...
Click to collapse
See section 0 (zero) of this thread.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
realbbb said:
Flash with RSD or FASTBOOT.
BUILD REQUEST INFO:
SW Version: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keysMDM9625_41.51.07.22.04R
MBM Version: 70.96
Modem Version: MDM9625_41.51.07.22.04R
FSG Version: UNKNOWN
Build Fingerprint: motorola/quark_verizon/quark:6.0.1/MCG24.251-5-5/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.91.5.quark_verizon.verizon.en.US
Model number: DROID TURBO
Android Version: 6.0.1
Baseband Version: MDM9625_41.51.07.22.04R
Build Number: MCG24.251-5-5
Build Date: Mon Jan 30 08:40:14 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_default_v1.0.nvm
Regulatory Info (eLabel): None
Blur Version: Blur_Version.24.91.5.quark_verizon.verizon.en.US
Version when read from CPV: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keys
QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
Download Link : https://mega.nz/#!dd4wXYiI!sRgo3aathlCDcg4YqBLxrRrd2ZK4u8BbnvHSCDoP7hE
SHA1 hash : 723f1d2b40f21343ecd87ebf4bb36c0f921e01e3
Recovery Only
Download Link : https://mega.nz/#!EFZFRKoC!G62yatqnQMJI4lEFZPlYHtMEIvUCgLYBjFE-p5uZ4Tw
SHA1 hash : 670b3830bc990f78a223273a99b42b9b9d5c74c8
Radio Only
Download Link : https://mega.nz/#!pJIFGCpS!CbyB1S3kDUKvh81-TjcDB-f_TKaP1XFSiN7JISwDU0o
SHA1 hash : 4eaea2d55f5fab1048b78598500d47c4fd3ca063
BBB
Threw Nead
Click to expand...
Click to collapse
Edit 1: Read faster than I was understanding. Trying it now.
Edit 2: Didn't understand how to flash the one you linked, so I used the one supplied in the guide and flashed everything. Still getting the same issue though.
VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
whoa, I somehow mis-read this. Your bootloader is locked? Do you want to unlock your bootloader? If so, if you do not have the latest firmware, then don't flash the latest firmware. Ignore my last post.
However, if you are already on the latest firmware, then you can't unlock your bootloader anyway, so you might as well re-flash that firmware to fix whatever is corrupted.
---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------
VooDooCC said:
Read faster than I was understanding. Trying it now.
Click to expand...
Click to collapse
I read too fast also. I thought your bootloader was UNlocked and you were still stock.
What firmware were you on before you had this trouble?
If you were on the very latest already, then you can't flash that firmware in that thread -- because you can't downgrade with a locked bootloader. You can only flash same version or higher.
I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.
VooDooCC said:
I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.
Click to expand...
Click to collapse
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
TheSt33v said:
Section 0: Installing Firmware Version MCG24.251-5 (instead you would be installing Official Stock Firmware 6.0.1 MCG24.251-5-5. Note the extra "5" on the end. It's the very latest stock firmware, but cannot be unlocked as of this date by Sunshine.)
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you are probably out of luck. This guide will not work for you. If it says anything else, continue reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
(instead download THIS VERSION: Official Stock Firmware 6.0.1 MCG24.251-5-5)
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows). (INSTEAD you would extract the firmware version I linked to.)
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data. (This will instead install MCG24.251-5-5 if you downloaded that version, but yes it will erase all your data.)
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
Click to expand...
Click to collapse
ChazzMatt said:
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
Click to expand...
Click to collapse
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.
VooDooCC said:
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.
Click to expand...
Click to collapse
I fixed the download link, so should work now.
As for the bat.file, I don't know.
I searched and found some more download versions, like this:
https://easy-firmware.com/index.php?a=browse&b=file-info&id=80611
Sweet Sassafrass, it works! I simply copied the .bat file from the -5 zip to the -5-5 (newest FW) took almost 5 minutes on the Droid splash screen, but it's alive. Thank you so much @ChazzMatt for all your help.
Updated my new x522 to 5.8.021s now I have no phone or data. It sees the sim and my phone number on the sim but it won't go on the network. Everything else is fine so have 2 questions.
1. Can and how can I flash a new modem to the 5.8.021s firmware?
2. What modem should I use I am in California on T-mobile?
Baseband MPSS TA 2.1 c700008-8976 GEN PACK-1.85233.30.76286.2
EUI version 5.8.021S
Thanks in advance.
Rick
dainbramage said:
Bought this phone last week off ebay thought I would update the firmware so I found the 5.8.021s file and did the update ZIP. It updated fine and everything worked except the phone. It shows the sim card as t-mobile with my phone number and cellular data calls and messages as t-mobile but when I try search for network I get "error searching for network". I tried different sims that I know are good and nothing works. I would return it to the original firmware but I wasn't smart enough to back it up. I would flash a new modem if I knew how maybe that is the problem. I have an x829 as my daily driver this was going to be a birthday gift.
Baseband MPSS TA 2.1 c700008-8976 GEN PACK-1.85233.30.76286.2
EUI version 5.8.021S
Thanks in advance.
Rick
Click to expand...
Click to collapse
Seems like you flash a wrong ROM that is meant for different country.
Download EUI stock official ROM which is meant for your country then flash it with chinese twrp once you flash it
Fixed it. Installed the small EUI by aurel. He had a note about my predicament on the first page. Great ROM for me and a big thank you to him. So here is what I did. Probably would have worked on the 21s too.
1. Download the adb, fastboot drivers
2. Install it on your PC.
3. Restart the phone in fastboot mode (power + vol down)
4. Type this commands in the terminal:
Quote:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5. Done.
Thanks again
I got this problem fixed after using fastboot erase persist, and fastboot flash persist /directory/persist.img.
I Got stocked after trying used fastboot erase (each of my partitions) and well not remember what more i did. Just tried installing a lot of stock custom rooms (that not worked) and also remember that the twrp keeping said not able to mount persist partition.
Realme XT Wiki
For convenience : https://www.androidfilehost.com/?w=files&flid=304989
First things first.
DISCLAIMER : Use this guide at your own risk. I won't be responsible for you bricking your device due to following this guide. It's also necessary to back up your data before you attempt anything.
Realme XT is not really a developer friendly device as they claim to be for the following reasons.
- Bootloader restricts flashing critical partitions and certain fastboot options are disabled like
Code:
fastboot boot recovery.img
- The flash tool is only available to service centres.
- Kernel sources are not actively updated by realme.
- Nil response to developer's queries.
Code:
[B][U]Table of contents :[/U][/B]
- Unlocking the bootloader
- Unbrick guide
- TWRP guide
- Upgrade guide
- Downgrade guide
- Project Treble for Realme XT
- Links
For unlocking the bootloader, follow the official instrutions from here :
https://c.realme.com/in/post-details/1184740422732218368
As of 28/03/20, you can unlock the bootloader in Realme UI. The official guide for XT is still not updated by realme, but the bootloader unlock app tool that was released for realme3pro works for XT.
UNBRICK GUIDE FOR REALME XT : (FASTBOOT)
Most bricks that happen with devices are softbricks. This means you can boot into stock recovery using key combination or you can access fastboot.
Hardbricks are where your device basically does nothing no matter what you do.
If you are on Color OS 6 or realme UI on locked bootloader :
- Switch off your device
- Press volume up + power button hold it until it finishes starting up.
- You will see the recovery menu now
- Press online update and connect it to wifi and follow instructions
If you are on color os 6 on unlocked bootloader :
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
Since custom ROMS don't deal with critical partitions, there is very less chance that the critical partitions are messed up. Majority of the times you would be fine with just flashing the boot image, system image, vendor image, vbmeta.
Instructions for color os 6 (Android pie firmware) :
Download the stock pie A16 fastboot image from the links section and extract it :
Just flash by executing the following commands :-
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
If you are on Realme UI on unlocked bootloader :
Prerequisite :
Download the stock Realme UI fastboot image from the links section and extract it :
Note : The zip file has other partitions too. Hopefully, you shouldn't need them.
Just flash the boot,system,vendor and vbmeta by executing the following commands
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
Guide to Custom Recovery:
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
TWRP Recovery
Orangefox Recovery
Instructions to install TWRP recovery:
Run this command
Code:
fastboot flash recovery TWRP.img
You can install orangefox recovery by flashing it via TWRP recovery or by extracting the recovery.img from orangefox recovery.zip file.
Upgrade guide :
You can always find the latest update from here : https://www.realme.com/in/support/software-update
Upgrading from android pie to android 10 carries the risk of bricking your device. Be it locked or unlocked. Thus proceed with caution and ONLY use stock recovery to update from android pie to android 10.
If you are on locked bootloader,
Step 1 :Simply download the update of your choice from the Links section and try to open it in stock file manager.
Note : If it doesn't show the update option in stock file manager, just rename the file from *.zip to *.ozip and try again
Step 2 : Press reboot immediately after the flashing is done
Step 3 (Very important) : Pray that everything works. Bricks can happen to anyone.
If you are on unlocked bootloader,
Step 1:In case you already have TWRP working on pie, simply flash the official stock android pie A16 through twrp and let it boot.
Step 2:Now, let it fully boot into the system
Step 3: Go to stock file manager and follow similar instructions as is for locked bootloader that's written above.
Downgrade guide :
Prerequisite:
In case you are in realme UI (Android 10) and want to roll back to android pie for any reason, you need to backup your data and flash stock pie A16 via TWRP
Step 0 : Back up your data and download stock A16 firmware from the links section below
Step 1 : Go to TWRP and flash stock pie
Step 2 : Flash stock pie again
Step 3 : Format data and reboot
Project Treble for Realme XT :-
You could refer here for what works and what doesn't
https://github.com/phhusson/treble_experimentations/wiki/realme-XT
Prerequisite :
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
3. You need to be on realme UI (Android 10)
Typically, you could install GSI without even using TWRP.
Step 1: Download any A/B arm64 GSI of your choice
Step 2: Erase userdata using the command
Code:
fastboot -w
Step 3: Flash system.img using fastboot command
Code:
fastboot erase system && flash system system.img
Step 4: Flash RUI vbmeta with flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Optional : Flashing TWRP helps with installing magisk and device specific treble fixes and is highly recommended.
USEFUL LINKS :
Recovery (Both stock and TWRP), Fastboot images and Official Updates
https://www.androidfilehost.com/?w=files&flid=304989
Realme XT Android 10 C01 (Realme UI)
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_1010_all_yuEH87qmmZhw.ozip
Realme XT Android pie A16
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_0160_all_CcmkxwAnmByA.ozip
Realme XT stock vbmeta Android 10 C01 (Realme UI)
Help!!
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
mehtakush007 said:
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
Click to expand...
Click to collapse
Use the stock recovery for update and wait for official OTA.
Reset Device
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
Unfortunately no. you must input password or your data is a lost cause.
krizhiel said:
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Click to expand...
Click to collapse
The tutorial is already there in the wiki. Although make sure you backup your data first.
PS C:\adb> fastboot flash recovery C:\adb\TWRP_RMX1921_pjgowtham_290320.img
sending 'recovery' (65536 KB)...
it did not flash it just stayed there forever
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
Same problem i have..Any help please..
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
You locked manually?
akashavel said:
You locked manually?
Click to expand...
Click to collapse
yes, me too. And now i have hardbrick and dont know how to fix this without service centre
bro Did You fixed it ?
I am on RMX1921_11_C.04 is there anyway to install custom recovery?
I bought a realme xt and upgraded it to realme ui version c04 but I get some random crash reports I don't know what is it they just randomly pop up 1-2 times per day along with a screenshot I am uploading those please can someone check.
My device bootloop'ed after following your downgrade tutorial. Tried boot unbrick it like your tutorial to no avail
Anyone who is now used to with this device and have done all these steps from Unlocking bootloader to flashing recoveries to installing custom & Stock Roms, can you please tell me what are the senarios in which this device can brick and only restored by Realme service center? I mean what possible error we can make that gives error of boot/recovery destroyed and only needs to visit realme service center?
I am very new to realme, before getting started with unlocking bootloader, i want to be sure about my steps, actually all i need is to use titanium backup for old data transfer of apps, my phone records etc, and most importantly using viper4android. This is all i am going to do after unlocking bootloader.
Raju Sah said:
Same problem i have..Any help please..
Click to expand...
Click to collapse
A reply this late isnt probably useful. But for others who refer this thread, once locked, it can be saved only by flashtool if you cant access stock recovery.
Fastboot commands not working
Hey there.
I am using realme xt with realme UI and i tried to unlock the bootloader. The bootloader is unlocked successfully but the fastboot commands arent working now on the device. This is whats happened while relocking the bootloader and same error for flashing recovery.
D:\Root\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
f40db298 device
D:\Root\platform-tools>adb reboot bootloader
D:\Root\platform-tools>fastboot devices
f40db298 fastboot
D:\Root\platform-tools>fastboot flashing lock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
D:\Root\platform-tools>fastboot flashing lock
< waiting for any device >
^C
D:\Root\platform-tools>fastboot devices
D:\Root\platform-tools>
this also happened while flashing recovery also. And I am kind of stuck i cant relock the bootloader and cant install custom recovery to root the device.
Kindly, guide me to solve this problem. Thanks in Advance.
Hi, anybody can help me? I want to sell my phone so i wanted to flash stock rom and lock the bootloader. But i dont find any post or something like that to do so... Do you know how can i flash the stock rom and relock the bootloader like we can do with xiaomi phones?
I have a G7 Plus Retail version on stock ROM, rooted and Magisk installed. Via other threads, I have learned how to manually flash updates by extracting the zip file and then running fastboot command lines. Yesterday, I received an alert that QPWS30.61-21-18-7-8 update is available, via OTA updates on my phone - of course I know I can't run the OTA update, even if I uninstall magisk and restore boot image, etc., but I am wondering if anyone knows where to find this update as a downloadable zip so I can manually flash it? It doesn't seem to be on the mirrors.lolinet.com site where all the other g7 plus stock ROMs are.
I've been into custom ROMs in the past but to me this stock ROM is reliable and un-bloated enough that it's acceptable for my needs.
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
bibikalka said:
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
Click to expand...
Click to collapse
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
cllewis1 said:
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
Click to expand...
Click to collapse
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
bibikalka said:
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
Click to expand...
Click to collapse
Yeah, I have TWRP. Therefore I think my only option for the update is to get hold of the zip file, extract it, and manually install it piece by piece (which takes all of 10 minutes to do once I have the file downloaded.)
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
cllewis1 said:
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
Click to expand...
Click to collapse
Oh, could you back up /system for QPWS30.61-21-18-7-3 as an image if that's what you have? And put it somewhere?
Is your channel RETLA in settings?
I think if you back up your /data (unencrypted I assume?) in TWRP, you could just flash the entire new OS from here:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Backup of the /data is important in case things go south. You could later pull programs from the TWRP backup using TitaniumBackup. For /sdcard, use TotalCommander, zip it, and if you unpack later, TotalCommander can even restore time stamps if you give it root.
These versions are a bit confusing, that's why I'd rather restore /system, and let it OTA instead of flashing the full ROM. But it does not seem you have this option anymore (if you decrypted /data, your /vendor is probably modified).
Update: If you want, I could give you stock /boot, /recovery, /vendor. But if you are decrypted, you are better off just loading that entire new ROM. If you find a good guide for A/B Moto phones, please let me know (it's important not to mess up A/B stuff).
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
cllewis1 said:
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
Click to expand...
Click to collapse
Good news! Did you wipe /data too? Or did you keep it? Did you keep the log of commands by any chance? I am still a bit hazy with this A/B business, and as such, want to proceed more carefully than usual
For storage, you can use one of the free options (something like Dropbox or Mediafire, or even Google Drive):
15 Best FREE Cloud Storage & Online Unlimited Drive Space
Cloud storage is a way of storing data online. It requires an internet connection in order to maintain, manage, and share documents, presentations, spreadsheets, images, audio, video, etc. with others
www.guru99.com
You can just PM the file link to me (not in the forum).
Thanks for the effort!
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot reboot
Note that this is a "dirty" flash and will leave all your apps, all your data, all your settings intact. Note that you will lose TWRP recovery by doing this.
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
fastboot boot twrp.img (fill in whatever the name of your twrp boot image is)
This will boot you into TWRP. From there you can install twrp recovery and magisk.
Note - do not do:
fastboot flash twrp.zip - attempting to flash twrp recovery from fastboot will soft brick your phone and you'll have to go back and run all these commands again.
cllewis1 said:
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
...
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
Click to expand...
Click to collapse
OK!
It looks like TWRP can read /data partition now, which is different from when I tried it last time for a moto g6.
I could not use your TWRP system backup since it is not a bit-for-bit "system image" version (it was just a straight system backup with files). It would not restore "dm-verify" checksum to enable OTA. To have a bit for bit one gotta do "system image" in TWRP.
Your list of commands is slightly different compared to flashfile.xml file. You may want to double check that since it seems you've missed some partitions.
I think your original system image may be gone from your phone - depending on A/B situation, so I better use the full ROM and just install it directly (as you did).
Is everything working fine for you with the updated ROM?
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
cllewis1 said:
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
Click to expand...
Click to collapse
YES! It's great if you still have it!!! Could you upload it to your drive that you shared before?
Thank you in advance!
It's good thing I checked - I was already on the way to start getting ready for a more laborious update.
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Interesting ... Could you still upload that system image file for QPWS30.61-21-18-7-3 to your file storage? I have not updated yet - too busy with other things, and wanted to do it carefully. Much appreciated!
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Alright, I restored my system with your system image (many thanks!), and put back the stock boot. So it goes through the update (meaning the checksums are good), but then I get the dreaded "software update unsuccessful" message.
You could try this too, put back stock boot/recovery from the ROM, and see if it would update.
Edit: It looks like simply unlocking bootloader makes OTA fail:
"verity mode set to disabled"
I unlocked the bootloader of my G7plus, installed TWRP and then used TWRP to install Magisk. So far, everything is working, root hiding is working as it should and Magisk's "SafetyNet Check" is reporting success. Yay. Almost. a) During the boot...
forum.xda-developers.com
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
bibikalka said:
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks, got it installed. Works fine.
cllewis1 said:
Thanks, got it installed. Works fine.
Click to expand...
Click to collapse
Looks like 7-12 is available:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Way too many updates, LOL
Is that 7-12 fie working on your xt1965-T (cause on lolinet its labled xt1965-2) and that doesnt seem right.