So, many people including me are searching for all the stock software for ALL Style/Pure variants.
There is a thread which helps you going back to stock but only for the US version of the XT1572.
So i thought i'll open a new thread where you can grab all software files which belong to your phone.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this SOFTWARE
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Android 5.1.1
For Europe users: X_Style_XT1572_CLARK_RETEU_5.1.1_LPH23.116-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- Google Drive -- credits to @gokart2 thanks for that
For Asian DualSIM users: X_Style_XT1572_CLARK_RETASIA_DS_5.1.1_LPH23.116-18_cid7_subsidy-DEFAULT_CFC.xml.zip
For Asian SingleSIM users: X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- Google Drive -- credits to @seedubya thanks for that
For LA DualSIM users: X_Style_XT1572_CLARK_RETLA_DS_5.1.1_LPH23.116-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For LA SingleSIM users: X_Style_XT1572_CLARK_RETLA_5.1.1_LPH23.116-18_cid12_subsidy-DEFAULT_CFC.xml.zip
Credits to @fdc77 and @lohanbarth.
Android 6.0
For Asian DualSIM users: XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
For LA DualSIM users: XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For LA SingleSIM users: XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
For Europe users: XT1572_CLARK_RETEU-UK-FR_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Mirrors: -- STACK -- thanks @arnoslag
Credits to @fdc77, @lohanbarth and @fdc77.
Additional files that you maybe need.
@fdc77 provided some usefull stuff. In this folder you can find stock EU MM rom, and some MM/LL single zipped part of the rom, like boot.img, recovery.img and modem.
--Link--
Here is how to install:
you need adb/fastboot drivers installed
you need to backup all your data on your phone, the tool will erease everything
reboot your phone into bootloader mode and plug in your usb cable which is connected to your PC. (power off your device then press the POWER and VOLUME DOWN button for 3-4 seconds)
then you need to open a command prompt in the folder where you unpacked the zip file you downloaded before (press SHIFT + RIGHT CLICK on a empty space then "open command prompt here")
now you have to check the functionality of the adb drivers, simply type "fastboot devices" and you will see a list with your connected devices in bootloader mode.
now you need to type every single command in the command prompt window from the list below.
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
NOTE: You will still have the "Warning" screen when you boot up your phone. If you dont want that, head over to this THREAD
XDA user @ban.codrut has provided us the logos available. thanks for that
Simply flash them in fastboot with the command "fastboot flash logo logo.bin"
If you have any questions, please write them in the comments and I'll answer you.
Android 6
RETLA http://www.filefactory.com/file/1hbb9jckeiwr/XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETLA_DS http://www.filefactory.com/file/22wwvy6nklfd/XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETASIA_DS http://www.filefactory.com/file/2ne81eh1ru9/XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Hello maj 6.0
XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
5.1.1
X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
fdc77 said:
Android 6
RETLA http://www.filefactory.com/file/1hbb9jckeiwr/XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETLA_DS http://www.filefactory.com/file/22wwvy6nklfd/XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
RETASIA_DS http://www.filefactory.com/file/2ne81eh1ru9/XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
lohanbarth said:
Hello maj 6.0
XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_DS_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml.zip
5.1.1
X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks, i will add them to the first post
Dude, change all those links. Those are lame ass slow. 8+ hours.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Isn't this a duplicate thread? There's another one about 3 threads down
Jay794 said:
Isn't this a duplicate thread? There's another one about 3 threads down
Click to expand...
Click to collapse
Nope it isnt. I think you mean this Thread? This one only contains the XT1575 builds which are'nt for all phones on that planet.
Settler11 said:
Dude, change all those links. Those are lame ass slow. 8+ hours.
Click to expand...
Click to collapse
yea FileFactory is low as f*k, which file did you try to download? I may upload the EU version to another hoster.
It has the XT1572 as well. Also how about uploading to zippyshare? That's a really fast mirror
Here, I've got mine from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I figure I'll take care of the XT1575 "PURE" firmwares if you take care of the XT1572 "Style" firmwares.....?
gokart2 said:
I figure I'll take care of the XT1575 "PURE" firmwares if you take care of the XT1572 "Style" firmwares.....?
Click to expand...
Click to collapse
You had listed individual parts, e.g. only recovery.img, that's missing now. Still im the zip tho, was nice before, specially on slow file hoster.
Also the twrp backups. Which btw I am waiting to get for RetEU 6.0 :l
dedors said:
You had listed individual parts, e.g. only recovery.img, that's missing now. Still im the zip tho, was nice before, specially on slow file hoster.
Also the twrp backups. Which btw I am waiting to get for RetEU 6.0 :l
Click to expand...
Click to collapse
Yeah, the slow host was what ruined it for me to post them, or pull the recovery, etc. I can't do the twrp backups for anything other then the xt1575, cause that's all I own.
Settler11 said:
Dude, change all those links. Those are lame ass slow. 8+ hours.
Click to expand...
Click to collapse
^^LMAO^^ Times 2! That filefactory hosting is junk,there are a million better places .
Hi all is it possible to just use a single file. For example can I just flash the recovery image.
seedubya said:
Hi all is it possible to just use a single file. For example can I just flash the recovery image.
Click to expand...
Click to collapse
Ofc you can but be careful that you flash the correct file
lAndroXl said:
Ofc you can but be careful that you flash the correct file
Click to expand...
Click to collapse
Is that the image file called recovery, so i would flash with command
fastboot flash recovery recovery.img
??
seedubya said:
Is that the image file called recovery, so i would flash with command
fastboot flash recovery recovery.img
??
Click to expand...
Click to collapse
yup
lAndroXl said:
yup
Click to expand...
Click to collapse
Worked perfectly, thanks a million. Now im prepared for the marshmallow update.
Settler11 said:
Here, I've got mine from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Click to expand...
Click to collapse
Xt1572 removed from op due to other member taking care of that
dude...those links are too slow....
Related
The day of the N is upon us!
In typical developer preview tradition since lollipop - I will try and keep this thread up to date with the latest and greatest
Factory Images:
NPC56P
Factory Image Mirror:
https://www.androidfilehost.com/?w=files&flid=51765
To do a dirty flash official factory image files on marshmallow:
- Open flash-all.sh or flash-all.bat in a text editor (depending on which you use)
- Change fastboot -w update image-angler-npc56p.zip to fastboot update image-angler-npc56p.zip
- Run flash-all script
Click to expand...
Click to collapse
Flashables:
Preview 3: http://forum.xda-developers.com/showpost.php?p=66949607&postcount=1423
OTAs:
To sideload OTA via ADB:
On Windows: adb sideload android.zip
On Mac/Linux: ./adb sideload android.zip
Click to expand...
Click to collapse
Google's Preview page: https://developer.android.com/preview/download.html
Google IMG files (manual installation):
Instructions:
A clean install is highly recommended when coming from 5.x.x to "M"
DOES NOT wipe your SD card.
via flashable file:
- Boot into recovery (TWRP/CWM)
- Un-mount /system in TWRP/CWM
- Wipe: system, data, dalvik and cache
- Flash bootloader (optional - only needed if new)
- Flash ROM (be patient - takes a while)
- Flash SuperSU (optional)
- Flash radio (optional - only needed if new)
- Reboot (first boot takes a while)
Click to expand...
Click to collapse
via fastboot (manual installation):
SYSTEM PREP (skip if you already have fastboot/adb setup):
Let's setup ADB and fastboot
Windows:
- Automated: http://forum.xda-developers.com/showthread.php?t=2588979 (follow the steps in the software)
- Manual Method:
Download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
You will need to open a command prompt window using this method:
Code:
- Go to the C:\adb\ folder
- hold down SHIFT key and RIGHT-CLICK
- select "Open command window here".
In order to use ADB & Fastboot from anywhere - use the following steps to setup windows environment variables:
Navigate to & click on Start > Right-Click on Computer > click on Advance System Settings >
Click on Environment Variables (under the advanced tab) > Click on New (User Variables) >
Variables Name: ADB (Or anything you want) Variables Value: ;C:\adb (this is the Path of my adb.exe file)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mac & Linux:
Install ADB & fastboot using: this file
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
----
Now that you're setup, let's do the flashing:
Boot into TWRP to wipe cache, dalvik, data (not internal storage/SD) and system.
Reboot to bootloader and flash the following:
fastboot flash bootloader <insert bootloader img name>
fastboot reboot-bootloader
fastboot flash radio <insert radio img name>
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img // OR // fastboot flash boot <insert name of unecrypt boot.img>
fastboot flash cache cache.img
fastboot reboot
After you finish the above - reboot in to recovery (TWRP/CWM) and factory reset - then reboot
Click to expand...
Click to collapse
-------
FAQ
Disclaimer & Copyrights:
I test everything before I share - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
Stay tuned!
that was quick. FIRST
abbz123 said:
that was quick. FIRST
Click to expand...
Click to collapse
as is tradition
Waiting for flashable zip, thanks!
Th3PorTuGa said:
Waiting for flashable zip, thanks!
Click to expand...
Click to collapse
lots of investigation needed first
looks like I'll be flashing this weekend.
btw the first link says "shamu" ?
hmillos said:
looks like I'll be flashing this weekend.
btw the first link says "shamu" ?
Click to expand...
Click to collapse
fixed, it was a typo
@vomer Your link in the OP is for Shamu. It should be Angler.
El Daddy said:
@vomer Your link in the OP is for Shamu. It should be Angler.
Click to expand...
Click to collapse
has been fixed already
If I follow this method, and make a TWRP backup before fastboot flashing everything, is it possible to restore the backup? Also do I loose my photos on the device etc with this method?
Some preview shots showing quick reply & split screen view: http://imgur.com/a/b4O6L
andresantos said:
If I follow this method, and make a TWRP backup before fastboot flashing everything, is it possible to restore the backup? Also do I loose my photos on the device etc with this method?
Click to expand...
Click to collapse
you should be able to restore the full twrp backup - however, do not use the flash all script in this case. Flash the images manually
Wait, is this a preview of N, as in Android 7?
so cool ! Thanks for this
floepie said:
Wait, is this a preview of N, as in Android 7?
Click to expand...
Click to collapse
yes
Btw before anybody ask
New Radio and Bootloader work also with M
vomer said:
you should be able to restore the full twrp backup - however, do not use the flash all script in this case. Flash the images manually
Click to expand...
Click to collapse
Thanks for the info. Which partitions should I backup thenm? Also bootloader and vendor etc? I will prepare for losing everything but most likely I won't be sticking with the version and would save much time if TWRP restore would work accordingly.
Btw, how stable does the preview seem? Does it look like you could possibly use it as a daily driver?
I dirty flashed and it worked so... But hey I know what I'm getting into.
Sent from my Nexus 6P using Tapatalk
Tylog said:
yes
Btw before anybody ask
New Radio and Bootloader work also with M
Click to expand...
Click to collapse
I'd be curious to see if this radio fixes any of the weird LTE/Signal hang issues the 6P has had the past few months..
N Beta Program OTA link: https://android.googleapis.com/pack...aeae3556.signed-signed-angler-ota-2659757.zip
I'm just going to wait for the flashable zip
Motorola Moto E (6th Gen)Stock Firmware Installation Guide
Basic Specs:
Motorola Moto E (6th Gen)
Codename: Surfna
Base SKU: XT2005
Android Version: 9 (Pie)
API: 28
SoC: Qualcomm® Snapdragon™ 435
CPU: Octa-core 1.4 GHz Cortex-A53
GPU: Qualcomm® Adreno™ 505
eMMC: 16 GB
RAM: 2 GB
Arch: armv7l (32-bit)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OVERVIEW:
First and foremost, when installing a stock firmware package on your Moto E6 -- or any Motorola smartphone, for that matter -- the simplest and most efficient method is to use the Lenovo-Moto Rescue & Smart Assistant (LMSA) via the firmware rescue option. Whether you are restoring your device to full stock condition, or restoring a device stuck in a boot loop, or that is otherwise unable to boot into the Android OS, the LMSA tool is your best route. The tool will download the most current stock firmware package available for your model and will systematically install the package, all by following a few simple steps. The latest version of the LMSA for Windows can be downloaded here, from Lenovo's official support page: https://support.lenovo.com/us/en/downloads/ds101291, as well as a downloadable and easy-to-follow user guide.
DISCLAIMER:
Flashing the partitions of your device carries with it the inherent risk of bricking or damaging your phone. By proceeding further, you assume sole responsibility for the integrity and operability of your device. I am not responsible for any good or bad that may occur from the use of this guide. Follow the instructions carefully, and things should go smoothly.
PREREQUISITES:
You will need a PC or laptop running on Windows 7/8/10/11, and the Motorola supplied (or quality equivalent) micro USB charging/syncing cable. Make sure your PC/laptop has the latest Motorola USB device drivers installed. The latest Motorola Device Manager can be downloaded from the official support page: https://support.motorola.com/us/en/solution/MS88481
This will install the most current Motorola USB device drivers. You'll need to install the Minimal ADB & Fastboot tools on your PC or laptop as well. Here is a direct link to the latest version https://mega.nz/file/z6gyzJya#TZWk0wuVuq5nJSnwsUx0KZClyj7M9BiEvqFdYH_dd6Q
Finally, you will need to download a stock firmware package for your particular model and carrier variant of the Moto E6. A full repo of Moto E6 Surfna official stock firmwares can be found here on the Lolinet mirror site: https://mirrors.lolinet.com/firmware/moto/surfna/official/. Take care to download the firmware for your model and branded carrier, if applicable. It should be noted here that you may install a stock firmware package on your device regardless of whether the bootloader is unlocked. If your bootloader is locked, however, you may only install a firmware build newer than, or the same as, the build currently running on your device. In sum, you cannot downgrade firmware in a bootloader locked state.
INSTRUCTIONS:
NOTE: The fastboot flashing instructions below have been outlined verbatim from the flashfile.xml of the most current firmware package available for this device. Because the Surfna will not be receiving an official update to Android 10, and because the Surfna's allotted /system partition has been sized for a maximum of ten sparsechunk files (0 thru 9), there is no likelihood of these instructions changing in the future. Moreover, these instructions have been thoroughly tested.
1. Extract the contents of the stock firmware package to the ADB/Fastboot directory on your PC/laptop;
2. Boot your device into AP Fastboot mode. With the phone powered on or off, hold the power and volume down buttons simultaneously for 8 to 10 seconds, or until you see AP Fastboot mode on your device display;
3. Connect your phone to your PC/laptop using your charging/syncing cable. To ascertain a proper connection, open a command window in the path of your ADB/Fastboot directory and execute this command:
Code:
fastboot devices
If properly connected, the command window will display an alphanumeric string synonymous with your device serial number. If you do not see your device serial number, try changing USB ports, use a different charge/sync cable, or try reinstalling your device drivers;
4. Once a proper connection has been verified, execute the following fastboot commands, preferably in this order (NOTE: the following procedure will erase all userdata on your device. Be sure, if possible, to back up any data or files you want to keep):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dtbo dtbo.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 logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.9
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Upon reboot, your device will be reverted to its stock factory configuration and running official Motorola firmware. It should be noted that this process will not relock your bootloader if it was in an unlocked state at the time you used this guide. Moreover, you do not need a locked bootloader in order to install future OTA updates.
Much thanks to @sd_shadow for his feedback.
I encourage anyone that is going to flash firmware to their device to get the flash commands from the flashfile.xml
The commands do change from time to time, moto may add another system sparsechunk.
There is a nice online flashfile converter, see link in my thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
I encourage anyone that is going to flash firmware to their device to get the flash commands from the flashfile.xml
The commands do change from time to time, moto may add another system sparsechunk.
There is a nice online flashfile converter, see link in my thread.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Always a great tip @sd_shadow Thanks for your input & guidance.
so extract stock firmware to be inside adb min folder n ie:c:\program files (x86)minimal adb and fastboot is that right?
Nagle91 said:
so extract stock firmware to be inside adb min folder n ie:c:\program files (x86)minimal adb and fastboot is that right?
Click to expand...
Click to collapse
That is correct. Then open your command window inside of that directory when ready to start flashing.
its seemed to work but it says bad key when booting up do you have any insight to that
Supr3me_Z_FBLive said:
its seemed to work but it says bad key when booting up do you have any insight to that
Click to expand...
Click to collapse
Yes. The "Bad Key" and "N/A" notifications are not errors. They are simply indicators that you flashed a stock firmware package with your bootloader in an unlocked state. Although annoying, these dialogues do not have any effect on the functionality of the device. In fact, there are custom boot logos you can flash to get rid of the annoyance. Otherwise it has no impact whatsoever on normal operations.
This thread provides what you need to get rid of the "Bad Key" screen and restore the original stock boot logo
Boot Logos!
Flash this using fastboot to remove the black screen on boot. This is the original boot logo. I will update this with more logos very soon. fastboot flash logo logo.bin
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for OnePlus9R[lemonades]
What is this?PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
(fix finger in display)
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download
MOD EDIT: LINK REMOVED DUE TO GPL VIOLATION
Credits
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
Installation1. Download PE Fastboot ROMinstaller ( These zip inciude both payload_dumper and fastboot_installer ) and extract zip in pc
2. Copy the playload.bin file from Rom.zip file to payload_dumper >> payload_input folder
3. On the command window, type the following commands one by one:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot reboot
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 4.8
Stable Release Date: 2021-07-05
Created 2021-08-26
Last Updated 2021-09-01
Thank you.
Only reason one would stay away from Pixel experience is a lack of Vanilla versions and forced Gapps being shoved down people's throats. Otherwise I've only heard great things about PE everywhere.
Does this break fingerprint reader for anyone else? its mentioned as working, but i cant seem to get it to work
hamppter said:
Does this break fingerprint reader for anyone else? its mentioned as working, but i cant seem to get it to work
Click to expand...
Click to collapse
This problem does exist, and I will fix it in the next version.
Thanks dude, everything else works really smooth and amazing +rep
hamppter said:
Does this break fingerprint reader for anyone else? its mentioned as working, but i cant seem to get it to work
Click to expand...
Click to collapse
The problem has been fixed and a new version has been uploaded
thanatos2057 said:
The problem has been fixed and a new version has been uploaded
Click to expand...
Click to collapse
Thanks dude! I'm going to try it as soon as I get home
Can we use havoc-os recovery to flash this? Also what's different in this compared to official PixelExperience for oneplus 8t? Is there an advantage of using this over the official build?
Is it Plus edition?
Sorry to bother, but does anyone know this error :
It seems that the device doesnt have enough space to resize, so i attempted factory reset + attempted the install steps manually ( currently using PE Rom installer ), and the same issue exists when flashing system.
Thanks.
Seems like the output files from payload dumper are extremely large
hamppter said:
Sorry to bother, but does anyone know this error :
It seems that the device doesnt have enough space to resize, so i attempted factory reset + attempted the install steps manually ( currently using PE Rom installer ), and the same issue exists when flashing system.
Thanks.
Seems like the output files from payload dumper are extremely large
View attachment 5400755
Click to expand...
Click to collapse
You need to flash in fastbootd, not fastboot
thanatos2057 said:
You need to flash in fastbootd, not fastboot
Click to expand...
Click to collapse
Hey sorry to bother you again, but isnt the recovery mode says this is fastbootd
I'm pretty new to this stuff so im sorry!
Same error! Followed steps/commands in same order as Original Post
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot reboot
Click to expand...
Click to collapse
hamppter said:
Hey sorry to bother you again, but isnt the recovery mode says this is fastbootd
I'm pretty new to this stuff so im sorry!
View attachment 5401299
Same error! Followed steps/commands in same order as Original Post
Click to expand...
Click to collapse
I just have same problem with you.First I suggest you ignore it,just do the followed commands.Then enter the recovery mode.Use the factory reset(what's means wipe data).reboot it,and you'll find it can't boot or it will enter fastboot.Don't worry about that.Enter fastboot(or it boot fastboot automatically) and do the followed commands again.You can find the command-line don't report errors.Lastly,enter recovery mode and do the factory reset.The phone will boot normally.
hamppter said:
Hey sorry to bother you again, but isnt the recovery mode says this is fastbootd
I'm pretty new to this stuff so im sorry!
View attachment 5401299
Same error! Followed steps/commands in same order as Original Post
Click to expand...
Click to collapse
Also I suggest you use the ROM install tool in this post .
tokimasa said:
I just have same problem with you.First I suggest you ignore it,just do the followed commands.Then enter the recovery mode.Use the factory reset(what's means wipe data).reboot it,and you'll find it can't boot or it will enter fastboot.Don't worry about that.Enter fastboot(or it boot fastboot automatically) and do the followed commands again.You can find the command-line don't report errors.Lastly,enter recovery mode and do the factory reset.The phone will boot normally.
Click to expand...
Click to collapse
I remember i had this same problem with the older version of this rom.
Somehow it was fixed from some procedure like you mentioned.
Currently it is not working.
I guess i will just continue using havoc for now
thanks for your help! much appreciated!
EDIT: weirdly enough, this works for the older build? I'm so confused lol
Update : I flashed OP8T pixel experience on this device, including OP8T TWRP.
the process for This rom(when i last tried, before installing OP8T PE ) still failed.
a lot of weird **** and weird QualComm errors and i decided to run msmtool.
Held power button + vol up (thinking it would throw me out of the fastboot loop after the OP8T PE rom install)
but lo and behold, this just sent me into system LOL
Im not sure, but is this correct? (the device name being Oneplus 8T)
Yet, the build number seems to align correctly with THIS Rom
PixelExperience_lemonades-11.0-20210901-0343-UNOFFICIAL
Im not even sure what i did, but its working LOL.
@thanatos2057
OP, please check your message from me and feedback. Thanks.
Trying To Find A Full Software Download To Correctly Flash OnePlus Nord N20 5G (MetroPcs/TMobile)
Before starting this process, my phone had just updated to 11_A07. I got my bootloader code from OnePlus, Even though my phone won't be unlocked for another month or 2. Anyways, I used the code, unlocked the bootloader, and decided I'd try to root it, figured it wouldn't be that complicated.
Starting off, I Flashed an A06 Boot.img to it, as well as The "JulyModemsBackup.zip" acquired from someone else on here, and I ran into the same problem as others on here, I lost all Radios (Service, Wifi, Bluetooth, NFC), even lost Flashlight and other key things. After trying and trying I ended up running into a screen saying something like "the Boot/Recovery image have been destroyed, please repair" so after that speed bump, I found I had to flash another boot.img, and use the fastboot --disable-verity flash vbmeta vbmeta.img trick, it worked, and after trying to fix the radios, I ran into another speed bump of the phone going straight into fastboot and would never actually boot, so I had to keep trying more and more combinations of files and fastboot commands, until ultimately, I got passed that, and back to having no radio.
Now somewhere, I went in a better direction, because this last time I booted it, I had successfully gained back: Wifi, NFC, Flashlight, Bluetooth, and everything else EXCEPT Actual Cell Service. I was even able to use Magisk to patch the boot.img and root my device. So all I need now Is my Cell Service. I will try to find the exact combination of files I used to get this far, so others may be able to gain a little of the phone back as well, I know that it says my phone is on version A06, so it successfully downgraded, at least it thinks so.
But Im hoping someone has the solution, or may find out how to completely fix the cell service issue. It would be perfect to have a COMPLETE Software File with everything needed, rather than multiple files with just few in each, all of which may be for different versions.
So If anyone has a complete file, please post it, or if you have all the files and can make a complete file to share, that would be just as great. I will look and post all the files I've used to get this far as well
This is just showing What Version my phone landed on after all the flashing and everything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NordN205G.rar
drive.google.com
DrScrad said:
IIO
Click to expand...
Click to collapse
How do I actually install it though? Is there a batch file or a step by step thing?
DrScrad said:
NordN205G.rar
drive.google.com
Click to expand...
Click to collapse
Also, I have this one too, but no where does it say how to actually flash to the device. I have been looking all day trying to figure that out but am having no luck. I would think there would be a Payload.bin, a .bat, or some kind of tip to tell you how to flash, but I can't figure it out
How to use Qualcomm Flash Image Loader (QFIL) to Install Firmware
Step-by-Step guidelines on How to use Qualcomm Flash Image Loader (QFIL) to flash stock firmware on any Qualcomm Smartphone and tablet.
androidmtk.com
fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot reboot bootloader
fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
DrScrad said:
fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot reboot bootloader
fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
PsYk0n4uT said:
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
Click to expand...
Click to collapse
Yeah, besides editing just a few of the syntax errors, I made, I'd say that the only thing he'd need to double=check would be tthe names of the partitions and like you said, to add the disable vbmeta syntax line to his clusterfuck of a list I made..
DrScrad said:
How to use Qualcomm Flash Image Loader (QFIL) to Install Firmware
Step-by-Step guidelines on How to use Qualcomm Flash Image Loader (QFIL) to flash stock firmware on any Qualcomm Smartphone and tablet.
androidmtk.com
Click to expand...
Click to collapse
im trying to use it but it wont find the device. is there a specifiv way to find it?
PsYk0n4uT said:
i would go ahead and add disable dm-verity and verification switches to vbmeta just to make sure that things have a chance of working with the rest of the partitions that might still be on a different patch.
might actuallly try to backup your originals from the inactive slot if you havent already flashed those
Click to expand...
Click to collapse
i keep trying this but i dont have the odm.img or even the system.img or vendor.img unless its talking about the files i have called Vbmeta_system.img and vbmeta_vendor.img files i have
dustinsmock20 said:
i keep trying this but i dont have the odm.img or even the system.img or vendor.img unless its talking about the files i have called Vbmeta_system.img and vbmeta_vendor.img files i have
Click to expand...
Click to collapse
Yes there should be a vbmeta.img and the two you listed
Does anyone have the odn.img, system.img, vendor, or maybe an updated modem file?
DrScrad said:
NordN205G.rar
drive.google.com
Click to expand...
Click to collapse
re-upload please? or AndoidFileHost link?
File folder on MEGA
mega.nz
reukiodo said:
re-upload please? or AndoidFileHost link?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
dustinsmock20 said:
Does anyone have the odn.img, system.img, vendor, or maybe an updated modem file?
Click to expand...
Click to collapse
which security patch
dustinsmock20 said:
im trying to use it but it wont find the device. is there a specifiv way to find it?
Click to expand...
Click to collapse
13.04 MB file on MEGA
mega.nz
download this driver, then with your phone turned off, plug it in while holding vol down or volume up or volume down and volume up.. forgot which combination and you;ll see in your device manager that it'll show up under your ports
DrScrad said:
13.04 MB file on MEGA
mega.nz
download this driver, then with your phone turned off, plug it in while holding vol down or volume up or volume down and volume up.. forgot which combination and you;ll see in your device manager that it'll show up under your ports
Click to expand...
Click to collapse
Awesome Scrad. Im glad to see ur still helping with this device. here is a link to May firmware for GN2200...... Someone said they would upload to AFH. this is most liekly rooted firmware tho
Opo nord N20 may newdevice - Google Drive
drive.google.com
Mine is most definitely unrooted and October security patch
Has anyone out there installed a GSI rom on the DITING? @tze_vitamin
I would like to try gsi rom if srgb color space is working...
I would like to try it also but i didnt really check how to, it look pretty unlogical the way it instal
Próbálkoztam különböző gsi ROM-okkal, indul az eea firmware és mix firmware is, nem tudom kisebb hibák vannak-e, amit az elején találtam, az ujjlenyomat nem megy, de nekem az a fő hiba, hogy sms üzenetek nem jönnek, és ez nekem néhány programnál probléma, pl: távirat belépéskor visszamentem a miuiba, messenger, facebook kétfaktoros hitelesítés. Kipróbáltam az ezen az oldalon leírt modot. fastboot parancs....-
fastboot eszközök
fastboot getvar all
fastboot set_active a
fastboot újraindítás fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot.img
fastboot törlési rendszer
fastboot flash rendszer gsi.img
fastboot -w
fastboot flash boot boot.img
fastboot reboot ugyanúgy indul, a hibák ugyanazok, de ha twrp recovery-t akarsz rá rakni, akkor a bootloop lesz a másik módszer xiaomi 11t pro gsi telepítés fastboot --disable-verity --disable-verification flash vbmeta vbmeta. img fastboot reboot fastboot fastboot erase system fastboot flash system gsi.img fastboot reboot recovery gyári alaphelyzetbe állítás reboot system ha nem törődnek ezek a hibákkal, akkor megpróbálhatod megnézni, hogy továbbra is fennállnak-e ezek a hibák, tudom, hogy nem volt hiba az előző mobilom, xiaomi 11t pro, se android 12, se android 13 gsi, a meglévő hibák pph beállításokkal javítható volt benne
I've tried different gsi ROMs, eea firmware and mix firmware also start, I don't know if there are minor errors, which I found at the beginning, the fingerprint doesn't work, but for me the main error is that sms messages don't come, and this is a problem for me with some programs, e.g.: telegram I went back to miui when logging in, messenger, facebook two-factor authentication. I tried the mod described on this page. fastboot command....-
fastboot devices
fastboot getvar all
fastboot set_active a
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot.img
fastboot erase system
fastboot flash system gsi.img
fastboot -w
fastboot flash boot boot.img
fastboot reboot it starts the same, errors are the same, but if you want to put a twrp recovery on it, bootloop will be the other method xiaomi 11t pro gsi installation fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img fastboot reboot fastboot fastboot erase system fastboot flash system gsi.img fastboot reboot recovery factory reset reboot system if you don't care about these errors, you can try to see if these errors are still there, I know that there were no errors on my previous mobile phone, xiaomi 11t pro, neither android 12 nor android 13 gsi, the existing errors are it could be fixed with pph settings in it
sorry for the stupid question, what alternative do we have that works with few bugs? EliteRom only? Thanks for replying so soon guys!
ronniecalipsis said:
sorry for the stupid question, what alternative do we have that works with few bugs? EliteRom only? Thanks for replying so soon guys!
Click to expand...
Click to collapse
or Xiaomi EU rom.
I tried crDroid GSI.
lagg, slow,
No fingerprint, bad sound.
I wish Kernel would come.
edit:
The installation description above is GENERAL! I did it based on that. (Not model dependent) I think.
user2332 said:
I tried crDroid GSI.
lagg, slow,
No fingerprint, bad sound.
I wish Kernel would come.
edit:
The installation description above is GENERAL! I did it based on that. (Not model dependent) I think.
Click to expand...
Click to collapse
General problem,thanks Xiaomi.
https://forum.xda-developers.com/t/xiaomi-12-xiaomi-12-pro-oss-kernel-sources.4470899/
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
Thanks @NOSS8
I check Xiaomi_Kernel_OpenSource every 4-5 days and wait for the diting kernel.
Maybe after the Xiaomi 13 presentation at the end of February... maybe...
user2332 said:
Thanks @NOSS8
I check Xiaomi_Kernel_OpenSource every 4-5 days and wait for the diting kernel.
Maybe after the Xiaomi 13 presentation at the end of February... maybe...
Click to expand...
Click to collapse
Maybe, but since it's incomplete, there will always be bugs or missing features.
Solved.
If you want to use fastbootd mode to flash GSI in this phone, You have to flash a third-party recovery first (such as TWRP).
now if you run
Code:
fastboot reboot fastboot
You will go to TWRP's fastbootd mode. It works well. The xiaomi official fastbootd mode have something wrong. Please use a third-party recovery
Original problem:
=============================
I used k50Ultra China version. I have unlocked . In bootloader mode (the screen shows FASTBOOT) I can flash boot.img I can set active slot. I have all permission. BUT in fastbootd mode(the screen shows FASTBOOTD), I do not have permission to flash any image or set active slot.
(super.img=system.img+vendor.img+product.img)
After a new super partition was used on Android. We can not flash system.img in bootloadr mode because it can only flash the whole super.img. Fortunately, we can still flash system.img in fastbootd mode. BUT it looks like Xiaomi didn't give users enough permissions in fastbootd mode.
Fastbootd is the only way to simply flash system.img. bootloader and TWRP can flash super.img can not flash system.img.
So I flash GSI faild.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On screens, fails because the bootloader is locked.
NOSS8 said:
On screens, fails because the bootloader is locked.
Click to expand...
Click to collapse
It is unlocked. In bootloader mode is unlocked, in fastbootd mode is locked.
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
NOSS8 said:
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
Click to expand...
Click to collapse
Useless. I found the problem. It is neccessary to flash a third-party recovery such as TWRP.
Dispossible said:
Useless. I found the problem. It is neccessary to flash a third-party recovery such as TWRP.
Click to expand...
Click to collapse
TWRP
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
NOSS8 said:
TWRP
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Click to expand...
Click to collapse
Thanks. Use the TWRP's fastbootd mode. It work well
NOSS8 said:
Can be useful
https://forum.xda-developers.com/t/how-to-install-custom-roms-gsi-11t-pro.4396021/
Click to expand...
Click to collapse
does this process work for diting? I'm looking for information and I don't quite understand how GSI roms work. Any help to understand is greatly appreciated.
Dispossible said:
Thanks. Use the TWRP's fastbootd mode. It work well
Click to expand...
Click to collapse
does the rom work? Could you please give a short summary of the installation process. Thanks a lot in advance.
ronniecalipsis said:
does the rom work? Could you please give a short summary of the installation process. Thanks a lot in advance.
Click to expand...
Click to collapse
Hello!
My method. (This works for me so far, but an expert will tell you what is right!)
Starting point: EEA V13.0.13.0
What did I install from GSI? ProjectElixir_3.5
How?
Enable USB debugging on an active system
PC connection
start adb, there are the following commands:
- adb reboot bootloader
- fastboot devices
- fastboot flash recovery_ab twrp.img
- fastboot getvar all
- fastboot set_active a
- fastboot reboot fastboot
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash vendor_boot vendor_boot.img
- fastboot erase system
- fastboot flash system GSI_rom_name.img
- fastboot -w
- fastboot flash boot boot.img
- fastboot reboot recovery
- TWRP -> Wipe -> Format Data -> Yes -> Reboot System
*twrp.img, boot.img, vendor_boot.img, vbmeta.img, GSI_rom_name.img files to the adb folder.
(boot.img, vendor_boot.img, vbmeta.img -> V13.0.13.0 EEA fastboot rom.zip)
I do not use!
I just tried it!
Waiting for AOSP and Kernel!