Related
Motorola Moto G7 Play
Codename: CHANNEL
Boost Mobile Variant
Model No. XT1952-4
OBSOLETE THREAD
IMPORTANT NOTE:
At the time this thread was created, Motorola Mobility had not yet released the official stock Android 10 update for this variant of the CHANNEL. Because this variant has long since received the official Android 10 update, this thread is beneficial only for experimental or educational purposes. While you may certainly install RETAIL Android 10 firmware on the Sprint compatible xt1952-4, it is recommended always to install the latest official Android 10 firmware package released exclusively for this variant. Official Motorola stock firmware packages are available for the Boost Mobile/Sprint variant here https://mirrors.lolinet.com/firmware/motorola/channel/official/Sprint/
COMPATIBILITY:
Although this guide specifies the Boost Mobile (xt1952-4) variant of the CHANNEL, device owners have tested and confirmed that this Android 10 firmware is compatible with other variants/models. Namely, the MetroPCS xt1952-6 and the T-Mobile xt1952-T are confirmed. It is safe to assume that, because this is a RETAIL based official firmware build, compatibility should be universal for all region based retail models.
DISCLAIMER:
By proceeding further, you are assuming full responsibility for the operability and integrity of your device. Although this is an official firmware package, installation of firmware has an inherent risk of damaging your device or otherwise rendering it inoperable if the instructions are not followed carefully. Follow this detailed guide carefully and concisely and the installation should go smoothly. However, I am absolved of any liability in the event you break something. If you do mess something up, either myself or one of the many knowledgeable members herein will try to assist you.
OFFICIAL ANDROID 10:
For owners of the Moto G7 Play, it's no secret that the official Android 10 OTA update has already began rolling out to device owners in Brazil. As such, it probably will not be long before device owners in the US begin seeing a notification for the Android 10 update. In the meantime, for owners of the Boost Mobile variant (xt1952-4) who want to manually update to Android 10 by flashing the official Android 10 retail firmware package, I have put this simple guide together to assist you. In essence, to update manually, you will need to install the Android 10 firmware package via fastboot or RSD-Lite. This guide is premised upon the fastboot mode method. This Android 10 firmware is stable and may be used for your daily driver ROM. Look to the end of this guide for reported bugs.
BUILD INFO:
Android Version: Android 10
Build Region: RETAIL
Build No. QPY30.52-22
Kernel Version: 4.9.206-perf+
Radio Version: M632_41.178.01.156R
FSG Version: FSG-8953-25.163
Bootloader Version:2.1-channel_retail-315bc626c6-200423
System Version: 30.1.24.channel.retail.en.US
Build Date: April 13, 2020
Security Patch Level: April 1, 2020
ANDROID 10 UPDATE FEATURES:
• Optimized Fast Charging
• Bug Fixes for Battery Drain Issues
• Power Optimizations
• System-Wide Dark Theme
• Gesture-Based Navigation
• Privacy & Location Controls
• Sound Effects -- Stock Equalizer & Amplifier
• Smart Reply w/Messaging Apps
• Incognito Mode w/Google Maps
• Focus Mode
• Live Caption
• New Parental Controls
• New Moto Actions
INSTALLATION:
For those members who are not familiar with installing official firmware via fastboot mode, I will outline the exact steps below, including links to the files you'll need for the job. This guide requires a Windows PC or laptop, running Windows 7, 8.1 or 10 (32 or 64-bit). While fastboot can be used with other operating systems, this guide is outlined for Windows based systems only:
1. First, on your Windows PC or laptop, you will need to download and install the latest version of Motorola Device Manager, to ensure installation of up-to-date USB device drivers. Motorola Device Manager can be downloaded here: https://support.motorola.com/us/en/solution/MS88481
2. Next, download and install the latest fastboot and ADB utilities for flashing the firmware to your device. We will be using the Minimal ADB & Fastboot tools, version 1.4.3. On your PC or laptop, visit this link https://mega.nz/file/dVR3xCJL#GjcIXtNcCoB7R9DJtyqJ3dfOmeuGuPUvx6FKgp23yrc
3. Now download the official Android 10 retail firmware package from the Downloads section below;
4. Extract the contents of the firmware package zip you just downloaded to your Minimal ADB & Fastboot directory;
5. Boot your Moto G7 Play into AP Fastboot mode. With the device powered off, hold the power button along with the volume down button for around 8 seconds or until AP Fastboot mode appears on your device display;
6. Connect your device to your PC or laptop using the OEM supplied -- or quality equivalent -- USB to USB type C charging/syncing cable;
7. Open a command prompt in the path of your Minimal ADB & Fastboot directory. Execute the following command: fastboot devices
If your PC/laptop & device are properly synced, the command window will return an alphanumeric string synonymous with your device serial number. If you are not properly synced, try another USB syncing cable, change USB ports on your computer, or try reinstalling the USB device drivers.
**NOTES: by following these installation instructions, you will wipe your device of all userdata. Before proceeding further, make a backup of any important files and media.
Once you have confirmed proper syncing between your device and PC/laptop, execute the following fastboot commands, preferably in this order:
fastboot oem fb_mode_set
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 logo logo.bin
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
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
fb oem config fsg-id boost
fb oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your Boost Mobile Moto G7 Play will be running stock Android 10. During setup, select the "Use Mobile Data" option instead of using WiFi. This will allow your device to establish its initial 4G/LTE data connection on the Boost Mobile network. Once setup is complete, your cellular data, voice and messaging services should be functioning normally. Make a test phone call and send a test text message to confirm.
DOWNLOADS:
Android 10 Retail Firmware:
•Build No. QPY30.52-22 (April 1 SPL): https://mega.nz/file/YIZnwAAZ#17HH-vbEsbxQVPNLjvgNqdTHFI4Ow2ah6SNC4Nnw9ec
•Build No. QPYS30.52-22-2 (June 1 SPL): https://mega.nz/file/lB5gkaqK#BD-r7dSTw8dgZAfI90pJq7LB_XJvqcvSVshXbLo-yic
Android 9 Pie Stock Firmware:
• Official Firmware Builds: https://mirrors.lolinet.com/firmware/moto/channel/official/Sprint/
BUGS:
• PRL/Domestic Roaming:
When roaming outside of the home network, the device may give a mobile IP registration response error (MIP Error 67-- Mobile Node Failed Authentication), and the cellular signal may become unstable. This is most likely due to the lack of an integrated PRL (Preferred Roaming List) provisioning service within the retail firmware. I am looking for a workaround: possibly implementing the Boost Mobile radio firmware from Android 9, or including the SprintDM mobile provisioning service as an add-on;
• Gesture/Navigation Features:
As XDA Member @JohnSmith8786 has pointed out, some of the native Gesture Navigation features in the RETAIL Android 10 firmware are somewhat unstable and buggy at times. This bug has been reported to Motorola Mobility via official bug report. Since this issue does not appear to be specific to a particular variant/model, and has been reported on various different models, this issue is likely unique to the RETAIL Android 10 firmware builds, and will likely be resolved by stability improvements/bug fixes in a future OTA(s).
Please report any bugs or instabilities in comments below. Also, please provide confirmation regarding compatibility of this Android 10 firmware on specific Moto G7 Play models. In theory, this firmware should work on any model with an unlocked bootloader. As all Android enthusiasts, modders and devs know, confirmation is always better than theory.
Could it work on XT1952-6 from MetroPCS?
mickem said:
Could it work on XT1952-6 from MetroPCS?
Click to expand...
Click to collapse
Can confirm working on XT1952-6 & XT1952-T
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
mickem said:
I tested stock AndroidQ for XT1952-2 ATTMX QPYS30.52-22-2 from lollinet mirrors on MPCS XT1952-6 and flashed with RSDLite. Until now everything works fine. Still testing.
Click to expand...
Click to collapse
I used RETAIL, only issue is the baked in gesture navigation gets squirrely sometimes
JohnSmith8786 said:
Can confirm working on XT1952-6 & XT1952-T
Click to expand...
Click to collapse
Thank you very much. I will add that to my OP heading. Yeah I've noticed some slight buggy behavior on the RETAIL Android 10 gesture navigation features too. Motorola Mobility has been notified of this issue, so perhaps a future OTA will fix this.
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
GRiZZ91 said:
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
Click to expand...
Click to collapse
Correct. Flashing this firmware to a device active on the Boost Mobile network will continue to function normally. I have noticed some buggy behavior when roaming outside of the home network. Other than that, your device should function just as if you were using the Sprint firmware build.
Sorry I was rusty
Does anyone know if in this Android version call recording goes back to our Motorola? On Android 9 I had to root phone for enable call recording. How is it now?
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1. For anybody needing it, I will try to post a link for the entire firmware package this weekend. Here is a link to the latest full firmware package for the Sprint/Boost Mobile xt1952-4 https://mega.nz/file/SmAEwRZL#M4KP8hHHEtBw5fOtHGRuGfDV8F0SUkFENVGctzJagFw
Viva La Android said:
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1.
Click to expand...
Click to collapse
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
veryspecialagent said:
Were you able to get Magisk running and the device rooted?
I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
Click to expand...
Click to collapse
I have a patched boot.image that will root your device.
Viva La Android said:
Ill have a patched boot.image that will root your device.
Click to expand...
Click to collapse
Correction I mean a patched recovery image
Viva La Android said:
You can I stall it via TWRP or fastboot
Click to expand...
Click to collapse
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk.
Viva La Android said:
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk
Click to expand...
Click to collapse
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
veryspecialagent said:
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.
I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
Click to expand...
Click to collapse
Cool. Yeah let me know. Follow the install instructions for LOS 18.1 directly from the Lineage WiKi. The install is not standard TWRP like most Lineage builds. This has to be done using.adb sideload in TWRP mode with a PC.
That should have posted 2 hours ago.
This is what I f'ing loathe about this process because it happens virtually EVERY time regardless of the device or OS or mod that I'm doing.
The first thing I did was make sure sdk tools were updated. There were updates for Android 6 and 10, as well as two new modules to install. It took about a half hour to go through them all, but everything is updated.
Downloaded LoS, latest version, and the recovery image.
Go to the first step on the LoS install, which is to sideload a specific zip file. kay...
-reboot into bootloader, then from there to recovery
-adb sideload <the file>
-on computer: error:closed
-on phone: Error 21, footer is wrong
This nearly ALWAYS happens, and I have yet to find a fix. I google for an answer, keeping results to just within the last year, and someone on Reddit had suggested a fix that worked for the poster. His problem was that he was in stock recovery. He needed to be in LoS recovery.
I think "well, they give you a recovery image separate with the OS download, maybe it's to boot with, like TWRP." So I boot into the bootloader and try to fastboot boot <lineage recovery.img>..........and it just starts up normal. I go to settings and check the build, and it's still the Android 10 version I started with. Tried it again, same results.
So then I get the bright idea to stay where I'm at in stock OS and adb reboot <lineage recovery.img>
Now, on my phone it's in a weird Android Recovery screen. "Can't load Android system. Your data may be corrupted. If you continue to get this message...." Then it gives me two options: Try again or factory reset.
Well, my mama didn't raise no quitter, so I hit Try Again. It goes to the black screen with "N/A" on it (which is what it would do back when I had this thing rooted and everything was peachy until I forgot the lock screen pattern), but then I get that error message again.
I'm going to factory reset and see what happens. Anyone with a solution, feel free to chime in anytime.
Factory reset complete. Now I'm.....still in Android 10, build QPYS30.85-18-11.
Lol, just to clarify where we're at: The process I'd "be much better doing" took three hours to implement just half of the first step, and it led to me having to factory reset because it wouldn't boot.
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever.
I upgraded from OOS 11.2.10.10 to OOS 12-C36. I understand that I need to get to C36 before upgrading to C40.
Here are the steps I tried:
1. Downloaded C36 full upgrade zip and placed on root of internal storage.
2. Started local upgrade with this file.
3. System rebooted and touch screen won't work at all.
I also tried it through Fastboot:
1. Downloaded C36 full upgrade zip and extracted all images from payload.bin.
2. Followed all fastboot command steps from this post.
3. Rebooted to system and touch screen still won't work.
Only option I have is to downgrade to OOS 11 with the downgrade zip.
Anyone have any suggestions?
Sometimes a downgrade is an upgrade... better get while the getting's good.
I was having the same issue until I MSM'd back to stock 11.2.2.4 and relocked the bootloader. Then I upgraded through the system update menu normally. I just unlocked the bootloader once I was fully upgraded to Android 12. Hopefully it'll be there same for you
jshinn1 said:
I was having the same issue until I MSM'd back to stock 11.2.2.4 and relocked the bootloader. Then I upgraded through the system update menu normally. I just unlocked the bootloader once I was fully upgraded to Android 12. Hopefully it'll be there same for you
Click to expand...
Click to collapse
Thanks for responding.
Which MSM tool did you use?
TikiThePug said:
Thanks for responding.
Which MSM tool did you use?
Click to expand...
Click to collapse
I initially used the 9 Pro Indian MSM tool,, but Ive been using the Global MSM with no issues recently, I was finally able to get the Global MSM working consistently by disable the "Auto-reboot" and "SHA-256 check" options and also selecting "O2" as the "Target"
Try this Msm tool
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
jshinn1 said:
I initially used the 9 Pro Indian MSM tool,, but Ive been using the Global MSM with no issues recently, I was finally able to get the Global MSM working consistently by disable the "Auto-reboot" and "SHA-256 check" options and also selecting "O2" as the "Target"
Click to expand...
Click to collapse
badreddine uday said:
Try this Msm tool
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
TikiThePug said:
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
Click to expand...
Click to collapse
Well i tried both of 9 and pro i got succed . About 9 proi i had to intall magisk root for oxygen updater apk i gave it the permissions then i choose the full global os 12 then wipe the data and have a fun. About sahara failed tru to uninstal drivers then reboot pc and instal it again i mean qualcom snapdragon usb drivers. I think you should desactive the antivirus protection and choose os on msm tool . Dont give up dude .
TikiThePug said:
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
Click to expand...
Click to collapse
Read this it may help you a lot
How to Unbrick OnePlus 9/9 Pro/9R using MSM Download Tool
In this guide, we will show you the steps to unbrick the OnePlus 9/9 Pro/9R devices using MSM Download Tool.
www.droidwin.com
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
TikiThePug said:
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
Click to expand...
Click to collapse
Here follow this guide which showed me how to get back to Global firmware after flashing the Indian MSM tool: https://www.droidwin.com/msm-tool-unable-to-recognize-oneplus-9-sahara-connection-error/
CHeck under the FAQ section titled "FAQ: Switch From OnePlus 9 Pro to OnePlus 9 Firmware". That should at least get you back to stock firmware for your region and then you can update from there before unclocking the bootloader
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also move all other OPS files out of this folder.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
TikiThePug said:
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
Click to expand...
Click to collapse
I had same issues well try the 9 pro msm with previous steps
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also remove all other OPS files.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
I told you . Happy for you dude good work. It needs little patience
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also remove all other OPS files.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
Awesome! Happy you got it working I think we've all been at this point with this phone. I like it but this might be my last OnePlus phone
jshinn1 said:
Awesome! Happy you got it working I think we've all been at this point with this phone. I like it but this might be my last OnePlus phone
Click to expand...
Click to collapse
Hi, i have a same problem with my LE2110, but it's possible you share your package modified with a good .xml please ?
coolporteur84 said:
Hi, i have a same problem with my LE2110, but it's possible you share your package modified with a good .xml please ?
Click to expand...
Click to collapse
Sorry it was @TikiThePug that posted about that I never used that method on my device
jshinn1 said:
Sorry it was @TikiThePug that posted about that I never used that method on my device
Click to expand...
Click to collapse
OK i'm sorry, I thought you also used this method.
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also move all other OPS files out of this folder.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
Hi, Could you share the finished package with the modified .XML ?
coolporteur84 said:
Hi, Could you share the finished package with the modified .XML ?
Click to expand...
Click to collapse
You can get it from here: https://easyupload.io/8aafk2
Link will expire in 6 days.
TikiThePug said:
You can get it from here: https://easyupload.io/8aafk2
Link will expire in 6 days.
Click to expand...
Click to collapse
Thank you very much !!! I'm trying this evening.
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
What's this?This is a stock oxygen os fastboot Rom for OnePlus9 adapted from https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/ .I really appreciate @Valdem for his flashing script for OnePlus 9RT.And I modified his script according to OnePlus 9 partitions and changed some flashing order in script.
Note that this is only for the device which is unlocked bootloader.And internal storge may be cleaned if you downgrade from higher oxygen rom or come from other rom like custom rom.
The ROM's image is extracted from oos11.2.10.10BA and oos12(LE2113_C47) ota package.Note that the ROM is only for ONEPLUS9(LEMONADE).
For full package oxygen os:
Flashing instructions:
- On your PC, install bootloader drivers for OP9 and check if device is recognized in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode.
- Connect the OP9 to your PC
- On your PC open command line window in the uncompressed folder,
- double click flash-all.bat
- wait till PC shows "pause" on terminal.
-Whether to format data is depend on which rom you stayed before. If upgrade from older oxygen os or on the same version oxygen os,no need to format data.Otherwise format data and reboot phone.
For firmware package:
Firmware package is used for whom wants to install custom ROM.And flashing firmware package by using this instead of MSM can streamline the procedure.After the PC shows "pause"on termianl,firmware package has been installed completely.Then following the custom rom install procedure-flash boot boot.img.If not boot into recovery,replace phone into bootloader mode,flashing dtbo and vendor_boot partitions will work.
The using procedure is same as full package.
NOTE:Before using this fastboot ROM and Firmware,you must have a compatible boot.img which can flashing images in fastbootd mode.Oherwise,install the "boot.img","dtbo.img"and"vendor_boot.img"by using "fastboot flash boot boot.img","fastboot flash dtbo dtbo.img"and"fastboot flash vendor_boot vendor_boot.img"in phone's bootloader mode.If phone don't boot into recovery or fastbootd mode,flashing firmware(If target is OOS11,then flashing oos11.2.10.10 firmware;If target is OOS12,then flashing firmware OOS12C47).After this,reflashing boot,dtbo and vendor_boot.
Download link:
Oxygen os 11.2.10.10:OOS11.2.10.10(FULL PACKAGE)
Oxygen os 12(LE2113_C47):OOS12(LE2113_C47)(FULL PACKAGE)
Firmware package:
Oxygen os 11.2.10.10 firmware:OOS11.2.10.10firmware package
Oxygen os 12(LE2113_C47) firmware:OOS12(LE2113_C47)firmware package
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
jmadiaga said:
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
Click to expand...
Click to collapse
This script uses fastboot, not recovery. Custom ROMs typically post the recovery image to use for flashing them in the thread if you're asking about that.
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
cbrown666 said:
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
Click to expand...
Click to collapse
Fastboot scripts are the quickest path to bricking and having to use MSM in my experience so I'm not trying it. If you do, make sure you switch to slot A first because for some reason, slot B really doesn't like to cooperate on this device.
NOTICE : As of June 15, 2022 you no longer NEED this method as the OTA for Android 11 has been released. This is here for those who don't get the OTA or need an upgrade from a clean reset manually using only the RSA tool.
Credits to : morpheus092511 over on the Lenovo Forums for tricking the Moto Tool into installing the stock firmware, and Chepr29 from the Lenovo Forums for the fastboot method that doesn't require the tool.
In fastboot on your PC after your extract the Android 11 firmware and have your device in recovery mode enter the following commands (back up your data this will clean wipe it!) :
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot erase userdata
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
1. BACK UP ANY IMPORTANT FILES OR INFORMATION! DON'T FORGET TO BACK UP YOUR TWO FACTOR AUTHENTICATION CODES AS WELL! This method can be done with other firmwares, but I have only tested a clean wipe upgrade from stock Android 10 to 11 RETUS on the Motorola One Ace 5G (Unlocked from Amazon) and can't comment on other firmwares.
2. Windows ONLY! DOWNLOAD THE RSA software from Motorola that allows you to recover, backup, or flash stock firmware to your device.
https://download.lenovo.com/lsa/Releases/Rescue_and_Smart_Assistant_v6.1.1.9_signed_setup.exe
3. DOWNLOAD the retail Android 11 firmware for the Motorola One Ace 5G (Kiev) Retail USA / Unlocked from here :
https://mirrors.lolinet.com/firmware/moto/kiev/official/RETUS/XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip
4. Go to C:\ProgramData\RSA\Download\RomFiles and extract the .zip folder here. You may need 7Zip, or WinRAR to do so. I recommend 7Zip as it's open source and free without nag popups.
https://www.7-zip.org/a/7z2107-x64.exe
5. Connect your phone to the PC via USB-C and shut it off. Hold volume down, and power on at the same time until the recovery screen shows.
6. The RSA software will detect your proper "latest" firmware automatically in fastboot mode, allow it time to download and wait until it's done, give it some time after it hits 100.00% because the program will begin decompressing and unzipping the stock firmware, but it will NOT tell you this, keep that in mind!
7. Under the same directory in Step 4, you should now have two folders. One that says 10 and 11 with almost the same naming convention, delete ALL of the files in the folder that RSA downloaded (the 10 folder), and copy and paste all of the files from (the 11 folder), but LEAVE the name of the folder the same as what it was when RSA downloaded it, don't change the name or you'll either have to re-name it back, or re-download the firmware once more and let it extract.
8. Go back to the RSA program and hit the yellow "Rescue" button. Don't touch your phone and leave it alone! All data will be erased and it will begin flashing the firmware from Android 11 without a single issue. If you have PIN or password locked your phone previously, upon first boot up Android will ask you for your previous device PIN before you can begin setting up the device initially.
NOTE : This should preserve your warranty, mine expired a few months ago and I haven't been able to confirm this 100% because of this. (we waited a LONG time for this update!) Since the process does NOT require your bootloader to be unlocked or modified in anyway whatsoever, I do NOT see how you could possibly void the warranty. As of this writing, I have NEVER attempted to even unlock my bootloader for stability purposes, and because rooting isn't a concern to me on this device. In fact, to my knowledge you are NO LONGER able to unlock the bootloader on Android 11, so proceed with caution if this is something you require! There may be a 3-day wait of being connected to the Internet before you are allowed to use the OEM Unlock function, please keep that in mind if this is an issue.
Since it is stock firmware, there are no functionality issues to be concerned with. Calling, 5G, camera, Bluetooth, NFC and other basic sensors and extra functionality work 100% to my knowledge after testing most functions myself for the better duration of a day, even my Fossil Gen 6 Android Wear 2.0 (updating to 3.0 soon) watch is functioning flawlessly over WiFI and Bluetooth with the new update.
Please note this method is now outdated, as the OTA has been released for Android 11.
TheLastSidekick said:
Please note this method is now outdated, as the OTA has been released for Android 11.
Click to expand...
Click to collapse
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Moondroid said:
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Click to expand...
Click to collapse
Yeah the whole thing is strange the way the way each firmware is slightly a different size between what is evidently the same Retail build.
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
mingkee said:
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
Click to expand...
Click to collapse
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
TheLastSidekick said:
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
Click to expand...
Click to collapse
After rescue, check C:\Program Data\RSA\Download\romfiles\
Check Kiev folder