Database Develop

[ROM][STOCK][6.0.1] xt1548 Unmodified Stock 6.0.1 ROM with April, 2017 Security Patch

Moto G (3rd Gen) xt1548
Sprint/Boost/Virgin Mobile
TWRP Flashable Unmodified 6.0.1 Stock ROM
SPECIFICATIONS
Model No: XT1548
Carrier(s): Sprint, Virgin Mobile, Boost Mobile
Android Version: 6.0.1 Marshmallow
Build No: MCIS24.107-82-18
System Version: 24.221.18.en.US
Android Security Patch Level: April 1, 2017
Kernel Version: 3.10.49
Baseband Version: M8916_2020632.44.03.21.54.01R
DISCLAIMER:
Your warranty is now void. As always, please be reminded that flashing the partitions of your device involves an inherent risk of bricking or otherwise rendering your device inoperable. I will not be held responsible for any good or bad that results from flashing the files from the herein link. You - and you alone - are solely responsible for your device.
NOTE: If you are coming from stock Android 5.1.1 Lollipop or from an earlier build of stock 6.0.1, the bootloader and partition index were updated with this build. It is strongly recommended, to ensure stability and optimized performance, that you flash the Bootloader & Partition Index updater in the downloads link below. In addition, this recent 6.0.1 build for the xt1548 includes an updated Baseband. While not absolutely required, it is recommended that you update your Baseband prior to flashing this ROM. I have compiled an updater zip which will update your Baseband (Modem & Radio Firmware) to the most recent version. Simply flash this zip using the current TWRP recovery. This updater zip can be downloaded here: https://drive.google.com/file/d/0B1Sfod4HWfk2blpURnRIVjg3WDQ/view?usp=sharing
REQUIREMENTS:
1. Unlocked Bootloader
2. TWRP Recovery (preferably @squid2's current version)
SOURCE INFORMATION:
KERNEL: https://github.com/moto8916/android_kernel_motorola_msm8916
DEVICE TREE: https://github.com/MotoG3/android_device_motorola_osprey
MENTIONS & THANKS:
I would like to say thank you to @squid2 for his hard work in building the Squid TWRP custom recoveries and Squid Kernels for our Osprey devices. I would also like to thank @lost101 for taking the time to educate me on the subjects of update-binary and updater-script.
INSTRUCTIONS:
1. Download the ROM zip from the below link and store it either on the internal storage of your device, or on an external micro SD card;
2. Boot your device into TWRP recovery. Perform a full wipe(/system, /data, /cache, /dalvik cache);
3. It is strongly recommended that you install the bootloader & partition index updater from the below link. NOTE: If you install the updater, NEVER ATTEMPT TO DOWNGRADE YOUR BOOTLOADER OR PARTITION INDEX. You can always downgrade to an earlier version of Android without issues; simply avoid bootloader.img and gpt.mbn;
4. Install the Baseband updater (OPTIONAL);
4. Select "INSTALL" from TWRP's main screen and navigate to the location in which you saved the ROM zip. Commence with installation. Flashing will complete in approximately 2 to 3 minutes. Wipe dalvik cache. Reboot system. NOTE: first boot can take several minutes. Just be patient and don't interrupt the process.
You should now have the latest stock Android 6.0.1 installed on your Osprey.
DOWNLOAD LINK:
Unmodified Stock 6.0.1 ROM:https://drive.google.com/file/d/0B1Sfod4HWfk2dnE5d1FNQk5INUk/view?usp=sharing
Bootloader/Partition Index Updater: https://drive.google.com/file/d/0B1Sfod4HWfk2TTNDY2VKMWJRSkk/view?usp=drivesdk
Stock Recovery image: https://drive.google.com/file/d/0B1Sfod4HWfk2Nm42QUJ5NklDdHM/view?usp=sharing

any updates for XT1550?

Crimsongrey said:
any updates for XT1550?
Click to expand...
Click to collapse
Been having trouble with the update-binary file on xt1550. Because I don't own the device it makes it difficult.

R u working on xt1550 Also....

abhi8939 said:
R u working on xt1550 Also....
Click to expand...
Click to collapse
Yes. I've been trying it. Where I don't own an xt1550, I've had a difficult time writing a working updater-script.

stock recovery image google drive link broken
thank you.

[ROM][STOCK][TEXTNOW][6.0.1] TextNow Moto G (3rd Gen) Stock Android 6.0.1

Moto G (3rd Gen) xt1548
TextNow Wireless
TWRP Flashable Android 6.0.1 Stock ROM
SPECIFICATIONS
Model No: XT1548
Carrier(s): TextNow Wireless
Android Version: 6.0.1 Marshmallow
Build No: MCIS24.107-82-18
System Version: 24.221.18.en.US
Android Security Patch Level: April 1, 2017
Kernel Version: 3.10.49
Baseband Version: M8916_2020632.44.03.21.54.01R
DISCLAIMER:
Your warranty is now void. As always, please be reminded that flashing the partitions of your device involves an inherent risk of bricking or otherwise rendering your device inoperable. I will not be held responsible for any good or bad that results from flashing the files from the herein link. You - and you alone - are solely responsible for your device.
NOTE: This 6.0.1 Stock ROM is from the Sprint compatible variant, xt1548. I have added the official TextNow app to /system/apps/, and have modified eri.xml and apns-config.xml to support TextNow voice, MMS & data services. Otherwise, this ROM is pure stock and completely unmodified. This recent 6.0.1 build for the xt1548 includes an updated Baseband. While not absolutely required, it is recommended that you update your Baseband prior to flashing this ROM. I have compiled an updater zip which will update your Baseband (Modem & Radio Firmware) to the most recent version. Simply flash this zip using the current TWRP recovery. This updated firmware can increase signal strength and/or download/upload speeds. This updater zip can be downloaded here: https://drive.google.com/file/d/0B1Sfod4HWfk2blpURnRIVjg3WDQ/view?usp=sharing
For users coming from 5.1.1 Lollipop, or users who have never flashed a stock 6.0.1 firmware package, it is strongly recommended that you flash this Bootloader & Partition Index Updater via TWRP. Simply install the zip and wipe dalvik cache once it installs. WARNING: Ensure you have at least 50% battery life prior to installing this zip, and never, under any circumstances, interrupt the process. A battery going dead or user interruption during this installation will almost certainly hard brick your device. NOTE: Should you ever wish to downgrade back to stock 5.1.1, do not attempt to downgrade the bootloader (bootloader.img) or the partition index (gpt.mbn). Simply skip these two files during the fastboot flashing queue, and downgrading should go smoothly.
I want to give my thanks to @FlashnRom for his thorough testing of this ROM and the updaters. His testing made the current stable version possible.
Bootloader/Partition Updater: https://drive.google.com/file/d/0B1Sfod4HWfk2TTNDY2VKMWJRSkk/view?usp=drivesdk
REQUIREMENTS:
1. Unlocked Bootloader
2. TWRP Recovery (preferably @squid2's current version, v3.1.1-r1)
SOURCE INFORMATION:
KERNEL: https://github.com/moto8916/android_kernel_motorola_msm8916
DEVICE TREE: https://github.com/MotoG3/android_device_motorola_osprey
INSTRUCTIONS:
1. Download the ROM zip from the below link and store it either on the internal storage of your device, or on an external micro SD card;
2. Boot your device into TWRP recovery. Perform a full wipe(/system, /data, /cache, /dalvik cache);
3. It is strongly advised that you flash the Bootloader/Partition Updater from the above link. Flashing the Baseband Updater is optional.
4. Select "INSTALL" from TWRP's main screen and navigate to the location in which you saved the ROM zip. Commence with installation. Flashing will complete in approximately 2 to 3 minutes. Reboot system. NOTE: first boot can take several minutes. Just be patient and don't interrupt the process.
You should now have the latest stock Android 6.0.1 installed on your TextNow Moto G3.
DOWNLOAD LINK:
TextNow Stock 6.0.1 ROM: https://drive.google.com/file/d/0B1Sfod4HWfk2WGZFR1VmRnFGdTQ/view?usp=sharing
Stock Recovery image: https://drive.google.com/file/d/0B1Sfod4HWfk2Nm42QUJ5NklDdHM/view?usp=sharing

Don't update the baseband with that zip
I love the ROM, it works really well, but after flashing the .zip that updates the baseband, the rom became unstable and would always reboot 30-60 seconds after being turned on. This happened in a constant loop. Upon reflashing and trying again, the problem persisted. I reflashed one last time without it, and it worked without the problem. once again, love the ROM, hate the baseband updater.
Anyone know what could cause this?
---------- Post added at 06:28 PM ---------- Previous post was at 05:53 PM ----------
I don't know if this is related but I just flashed the textnow stock .zip and now TWRP touchscreen capabilities are gone.

FlashnRom said:
I love the ROM, it works really well, but after flashing the .zip that updates the baseband, the rom became unstable and would always reboot 30-60 seconds after being turned on. This happened in a constant loop. Upon reflashing and trying again, the problem persisted. I reflashed one last time without it, and it worked without the problem. once again, love the ROM, hate the baseband updater.
Anyone know what could cause this?
---------- Post added at 06:28 PM ---------- Previous post was at 05:53 PM ----------
I don't know if this is related but I just flashed the textnow stock .zip and now TWRP touchscreen capabilities are gone.
Click to expand...
Click to collapse
Probably not related, but I may add this to the OP, a wipe of cache and dalvik/ART should probably be performed after flashing the ROM. On the baseband issue, I just determined the problem. I need to include in the baseband installer a command and files to update the bootloader and partition index. Because if you are coming from stock 5.1.1 on TextNow, your partitions and bootloader need to be updated to 6.0.1. Thank you for your user experience and input. I will write a script to correct the issue and update the thread accordingly.

How can I get permission of Google Drive to download for the baseband updater and bootloader?

New to device and the whole firmware thing

OK, long story short. Came for the nexus 6 and nexus 6p to oneplus 3t. The 6p had to flash vendor.IMG after every new ROM flash. But what is this whole firmware thing in this device? I have tried to find answers before asking but, what should I DO and NOT DO to have a brick? Like, wanting to go from a nougat ROM to an Oreo ROM, but not sure how. And then if I wanted to go from a n/o ROM to a beta, not sure how...then if I wanted to downgrade from an o or beta ROM.......please help

Treat the OP3T pretty much the same as you would the Nexus 6. The only difference is, like you've discovered, that OnePlus provides firmware files rather than factory images.
The installation instructions for the different firmwares (stable and beta) are found in the first few posts of the respective threads:
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240

It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)

Mizart said:
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Click to expand...
Click to collapse
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?

jamescable said:
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
Click to expand...
Click to collapse
I'm not entirely sure but in most cases the ROM would simply refuse to flash. Like for RR, if you don't flash a correct firmware then the flashing returns an "Error 7" and the installation stops. But even if it does flash through, it would either not connect to a network or get stuck in a bootloop, but nothing too serious which you can't rectify.

[STOCK] [H872] [11h] T-Mobile G6 Stock Collection

T-Mobile G6 H872 11H Stock Collection
Based on OEM 11h KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Stock 20a System Firmware will not work with 11g or 11h Bootloaders
11H Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
​
Bootloader: 11h Stock Bootloader ONLY
SysBoot: 11h Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11h Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS​
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
Boot to TWRP and do a Format Data
Reboot back to TWRP on Recovery to allow TWRP to mount System properly.
Do an Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you flash the SysBoot rom with Kernel patch and Root you are good to go, otherwise flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge​
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:1c168cff641f8609b3ee0d235d232028
SysBoot ROM - md5:f3bb40d933fdb11cdf3e7c18b91f0ec3
SysBoot Deodexed - md5:f45b6325326234a61ebcb012febdb1a8
SysBoot w/Patched Kernel + Magisk Root - md5:170ef77a503c4c3b36eb39150ca7a2d9
FullStock ROM - md5:667066e2eff9d1fd1c5b895c40950733
StockLAF - md5:4f2f2318005231f65a4ebdc36b6434c9
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!​
Other H872 Projects
H872 11G Stock Collection
H872 20A SysBoot ROMs (OEM and Rooted)
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom​
XDA:DevDB Information
[STOCK] h87211h, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-g6-firmware/files/h872/11h/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11h KDZ
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-10-05
Created 2018-10-05
Last Updated 2018-10-19

All 11h Files Up
UPDATE
All Files are done and available now for 11h
Added Today:
SysBoot ROM
SysBoot Deodexed
SysBoot w/Patched Kernel + Magisk Root
Enjoy!
​

Is full stoc.zip include recovery or laf ? I mean flashing full stock will not remove twrp or twrplaf ?
I was on 11g I made full backup from twrp... Then I flashed 20g for testing .. 20g flashed successefully but it was too laggy ... Then I restored my backup of 11g it restored succefully but fingerprint did not work ... After that I wiped everything and flashed 11g bootloder ,restored backup and flashed magisk and ended up with a bootloop....
Now I am on pixelexperience 9.0 ...
Now I want my 11g+data(apps) backup to restore ...
Plz help me
I hope you understood sorry for bad English

[GUIDE] [F.A.Q.] [chef] [TREBLE] Common Hurdles and Solutions for First Timers!

This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.​
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI. ​
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.​
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update. ​
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!​

Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!

Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/

DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.