Database Info

Calling all mini owners

Calling all mini owners, donate to tdm, found a mini for $100 and sent him the info for it.
He has been working very hard to bring us root, now let's bring him a Dev phone!
Unlocking, root and custom ROM will come a lot faster if we get a device permanently in his hands.
https://forum.xda-developers.com/member.php?u=4126377

It is so nice to see that the community cares more about serving the consumer than the actual company does. ?

Well, i'd like to donate, but how?
fallen00sniper said:
Calling all mini owners, donate to tdm, found a mini for $100 and sent him the info for it.
He has been working very hard to bring us root, now let's bring him a Dev phone!
Unlocking, root and custom ROM will come a lot faster if we get a device permanently in his hands.
https://forum.xda-developers.com/member.php?u=4126377
Click to expand...
Click to collapse
Sent from my ZTE B2017G using XDA-Developers Legacy app

JoeGatto said:
It is so nice to see that the community cares more about serving the consumer than the actual company does.
Click to expand...
Click to collapse
I know right
Muggx said:
Well, i'd like to donate, but how?
Click to expand...
Click to collapse
I guess you would have to pm him to ask how you can donate to him, I thought he had a link up for donations.
I'd take the donations and buy the phone for him since I live closer to the seller, but I don't know if he got the PM I sent him about it and bought it or not yet.

He's gotten the device, use the link in the op to ask how you can donate to tdm and offset the cost, he plans on releasing custom roms soon.
Very exciting time to be a mini owner.

I'm excited and can't wait! I'm coming from a Nexus 5 and Nexus 5x those have very good development support, I can't wait to start flashing ROMs and kernels on this mini!

Hey @fallen00sniper hope you don't mind me hijacking this thread, but I wanted a place to update everyone on progress and I didn't want to start a new thread.
Current status as of Oct 3 2017
Unlock
Unofficial unlock tool has been released.
Waiting for official ZTE unlock.
TWRP
Alpha version posted in unlock thread. This uses the binary kernel and init from stock (including enforcing selinux) and does not have decrypt support, so it is not optimal.
Working on a full source build and eventual official TWRP builds.
Custom ROMs
I have just now successfully booted the device with a source built kernel based on the ZTE provided sources. I'm starting on Lineage 14.1 support. This will probably take at least a week or two.
Once Lineage 14.1 is working reasonably well, I will also do an AOKP build since that is my preferred ROM. I can help community members with other ROMs, but I won't maintain them myself.
Other
Collecting information on regional variants.
@saymonek has a single-SIM UK/Europe version that is reportedly stuck on 6.0. Are there any more variants?

@tdm, completely fine by me.
while you are in the rom getting them up and running, check into why the touch screen sucks at positional tapping, mine isn't 100% accurate lol

Did a bit of research on variants by trolling through ZTE support. So far I've found:
* USA version.
* UK Carphone Warehouse version.
* International "open market" version (eg. Austria).
* Hong Kong version.

First build done:
Package Complete: /home/tdm/out/laos-14.1/target/product/tulip/lineage-14.1-20171003-UNOFFICIAL-tulip.zip
This is going to need a fair amount of work before it boots and runs, but ... progress!

Oh also FYI... I've been cribbing from the HTC One A9 (hiae) device for Lineage builds. haie is maintained by intervigil, who I had the pleasure to work with at cyngn. I'd say he is one of the top four or five device people in the custom ROM world. And it looks like he has been actively working on Lineage 15.0 so we should get that soon after nightly builds start.

It's so exciting to see device development take off!

Just a quick update...
I had a ... uh ... "server malfunction" yesterday so didn't get a chance to do much. However, I'm back in business today.
So far today I've got linage to start the boot animation. Should be able to get all the way to the home screen tomorrow.

tdm said:
First build done:
Package Complete: /home/tdm/out/laos-14.1/target/product/tulip/lineage-14.1-20171003-UNOFFICIAL-tulip.zip
This is going to need a fair amount of work before it boots and runs, but ... progress!
Click to expand...
Click to collapse
Hello, can I change my axon 7 mini back to the US variant? It was originally US variant, I mistakenly switched US band in the engineering menu and Iost network services. I managed to get it working with the European firmware from ZTE Russia. Would like to revert to the US variant. I noticed in the bootloader version, the US version is P852A12 whilst the European variant is P852A11. Any luck on reverting to US variant?

Can you not access the engineering menu and switch back?
If not, my suggestion would be to use QPST and/or QXDM. These are proprietary tools but you can find them for download. They will allow you to program the frequency bands that your phone uses.
Good luck.
djeniuss said:
Hello, can I change my axon 7 mini back to the US variant? It was originally US variant, I mistakenly switched US band in the engineering menu and Iost network services. I managed to get it working with the European firmware from ZTE Russia. Would like to revert to the US variant. I noticed in the bootloader version, the US version is P852A12 whilst the European variant is P852A11. Any luck on reverting to US variant?
Click to expand...
Click to collapse

tdm said:
Can you not access the engineering menu and switch back?
If not, my suggestion would be to use QPST and/or QXDM. These are proprietary tools but you can find them for download. They will allow you to program the frequency bands that your phone uses.
Good luck.
Click to expand...
Click to collapse
I can access the engineering menu. The device is working but would have loved to switched back to US variant because it's a US variant initially but I am unable to install the US firmware I downloaded from ZTE US Support site

I'm sure we can get you back on US firmware.
What is the error when you try to flash the ZTE package?
djeniuss said:
I can access the engineering menu. The device is working but would have loved to switched back to US variant because it's a US variant initially but I am unable to install the US firmware I downloaded from ZTE US Support site
Click to expand...
Click to collapse

tdm said:
I'm sure we can get you back on US firmware.
What is the error when you try to flash the ZTE package?
Click to expand...
Click to collapse
Error Target machine P852A12 not found. I noticed my device bootloader has changed to P852A11 - Tulip. I checked my friend's Device which we bought at the same time from best buy in US, his own is still P852A12

Ain't it beautiful?
It's alive
Edit: can't get inline images to work, so you gotta click. Oh well.

tdm said:
Ain't it beautiful?
It's alive
Edit: can't get inline images to work, so you gotta click. Oh well.
Click to expand...
Click to collapse
:victory:
I am considering not even worrying about the warranty lol
Big questions are, everything working?, can you return to stock?, and how does the performance of the rom feel?

Help unrooting and flashing a new rom

Hello, it's been some time since I've last rooted and flashed kernels on my devices. My device is having problems with certain apps and I feel it's time to update my root or change my rom or flash a stock rom etc. Here is what I am using now:
Build: MOAR v6.1 OA6
Software: G900PVPU1BOA6
Hardware: G900P.04
Android: 5.0
Kernel: 3.4.0-3859396
Would you recommend I unroot then flash a stock kernel? What is a new root I can use with this phone? Thanks

I would recommend Odin a fresh stock MM rom. Then boot to the desktop, by pass set up. Go to dialer ##72786# it will do a reactivate and update prl and profile.. Then Odin TWRP, and flash a new rom or your choice.. If you like MOAR then Odin a LP stock rom, and do as mentioned and flash MOAR 7.0 it works best. Right now, I'm running crdroid 3.8.5 baset off of Nouget with 7.1 gapps and it works very well You need the latest MM firmware to run it, and at least TWRP 3.2.1-0-ktle.img If you do flash crdroid download ktledv
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894

First off, thanks for the reply. I really appreciate the help. What's the battery life like on MM compared to Lollipop?
I would prefer to use something like a stock rom but just extremely debloated. I also want to be able to play pokemom go without problems and super su keeps giving me problems when trying to play. Do you know of any setups that would allow for pokemon go and are fast, battery effecient, and debloated?

doubledragon5 said:
I would recommend Odin a fresh stock MM rom. Then boot to the desktop, by pass set up. Go to dialer ##72786# it will do a reactivate and update prl and profile.. Then Odin TWRP, and flash a new rom or your choice.. If you like MOAR then Odin a LP stock rom, and do as mentioned and flash MOAR 7.0 it works best. Right now, I'm running crdroid 3.8.5 baset off of Nouget with 7.1 gapps and it works very well You need the latest MM firmware to run it, and at least TWRP 3.2.1-0-ktle.img If you do flash crdroid download ktledv
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-crdroid-t2860894
Click to expand...
Click to collapse
How's the mm baseband? I know the obvious response is updated is better but I experienced better LTE on the firmware I currently have, no idea honestly other than it's lolipop, maybe ok4? I want to upgrade phones but having trouble finding one with sprint newer that can be customized how I like so I'm also looking at playing with this one prior to and after getting maybe a pixel unlocked

andrew2432 said:
How's the mm baseband? I know the obvious response is updated is better but I experienced better LTE on the firmware I currently have, no idea honestly other than it's lolipop, maybe ok4? I want to upgrade phones but having trouble finding one with sprint newer that can be customized how I like so I'm also looking at playing with this one prior to and after getting maybe a pixel unlocked
Click to expand...
Click to collapse
I would stick with Lollipop OK4 and flash MOAR 7.0. I to find better LTE and all around connectivity on Lollipop than MM.. I once again, went back to MOAR 7.0 from crdroid.. Crdroid is a great rom, but battery life, sucks, as well as connectivity on calls and data. When in aroma and you get to the point about the kernel, choose don't touch kernel, and finish from there. I never like MM and those are the reasons why.. Crdroid I flashed was 7.0 but naturally on the MM base band, but it was still the same.

Thanks sir nobody could really answer that for me. I found the ok4 of all lollipop got the best LTE where I live, plus I'm on sprint so I'm a bit restricted on ROMs, unified dev leave some bugs with sprints network but not too badly!!

andrew2432 said:
Thanks sir nobody could really answer that for me. I found the ok4 of all lollipop got the best LTE where I live, plus I'm on sprint so I'm a bit restricted on ROMs, unified dev leave some bugs with sprints network but not too badly!!
Click to expand...
Click to collapse
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.

Fear_The_Fluff said:
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.
Click to expand...
Click to collapse
Thanks! I'll make sure to read which I should use. My daily is still on MM while my old one that's kinda beat up is now on N as it us now the practice phone. Playing with it before Oreo, may stay for a while. And I installed kltespr on both devices as there were still options available for specifically this device with the spr tag. My CM 13 network is fine, no worse than just regular sprint...
Haven't tried the move to either N or O on my daily, worried about the signal discussion. I'll use an old kltespr to test before the newer maintained kltedv if its there probably to see how it goes.

Fear_The_Fluff said:
You probably already know, but I will ask anyways. Are you using the KLTEDV version of the unified ROM? KLTE roms does not work very well with sprint.
Click to expand...
Click to collapse
Delete

andrew2432 said:
Thanks! I'll make sure to read which I should use. My daily is still on MM while my old one that's kinda beat up is now on N as it us now the practice phone. Playing with it before Oreo, may stay for a while. And I installed kltespr on both devices as there were still options available for specifically this device with the spr tag. My CM 13 network is fine, no worse than just regular sprint...
Haven't tried the move to either N or O on my daily, worried about the signal discussion. I'll use an old kltespr to test before the newer maintained kltedv if its there probably to see how it goes.
Click to expand...
Click to collapse
Unfortunately my sprint s5 is one of the phone with that signal issue. I was in the process of changing carrier so to try and fix that issue wasn't worth it for me. My new S5 did not have that issue, when i went to verizon, its a really weird bug.

Fear_The_Fluff said:
Unfortunately my sprint s5 is one of the phone with that signal issue. I was in the process of changing carrier so to try and fix that issue wasn't worth it for me. My new S5 did not have that issue, when i went to verizon, its a really weird bug.
Click to expand...
Click to collapse
I think it took a bit to stat with the sprint APN, changed some settings, messed with some stuff, and it seems fine now, I'll have to remember to check back at that before upgrading. I'm on the ok4 baseband

OpenKirin site now launched

So it looks like the OpenKirin site is finally here and they have their Lineage based ROMs available for download.
Now it does say the 970 is a supported chipset, but it doesn't list the P20/Pro as a device.
From what I can see it looks like EMUI camera and gallery are fully supported.
I'm not rooted etc. but does anyone know who's working on this project or if it can be tested on our device at all?
Would be keen to see a nice working Lineage ROM with full support of the EMUI camera.
Here's the site: OpenKirin.net

MrDanMak said:
So it looks like the OpenKirin site is finally here and they have their Lineage based ROMs available for download.
Now it does say the 970 is a supported chipset, but it doesn't list the P20/Pro as a device.
From what I can see it looks like EMUI camera and gallery are fully supported.
I'm not rooted etc. but does anyone know who's working on this project or if it can be tested on our device at all?
Would be keen to see a nice working Lineage ROM with full support of the EMUI camera.
Here's the site: OpenKirin.net
Click to expand...
Click to collapse
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it

dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
It seems that it's treble via fastboot only. We have to w8 and see for confirmation, I guess.

dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
1 - YNWA
2 - what would be the advantage of the Treble releases? My dream would be that its more like stock but ..

YNWA
Treble is just a system image, probably won't completely work for every device, probably won't ever be fixed for every device.
Whereas a full ROM, usually only has to be fixed / tweaked once.[
When you install a ROM you flash most of the device and it's generally in a zip format, whereas a treble ROM is an IMG and you flash it only to the system partition leaving everything else intact.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
@MrDanMak
You do know that we have lineage in the ROM section right? And that the camera had been ported and its working?
P20 camera.

dladz said:
YNWA
Treble is just a system image, probably won't completely work for every device, probably won't ever be fixed for every device.
Whereas a full ROM, usually only has to be fixed / tweaked once.[
When you install a ROM you flash most of the device and it's generally in a zip format, whereas a treble ROM is an IMG and you flash it only to the system partition leaving everything else intact.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
@MrDanMak
You do know that we have lineage in the ROM section right? And that the camera had been ported and its working?
P20 camera.
Click to expand...
Click to collapse
YNWA indeed! Nice to see fellow redmen in here.
Yeah I know there is a Lineage ROM, but I was under the impression the camera isn't fully working right? It still has the gallery issue doesn't it?

If you read the FAQs you will see that they mention you shouldn't flash the current downloads on the P20/Pro. They will provide builds for this phone at a later date.

MrDanMak said:
YNWA indeed! Nice to see fellow redmen in here.
Yeah I know there is a Lineage ROM, but I was under the impression the camera isn't fully working right? It still has the gallery issue doesn't it?
Click to expand...
Click to collapse
Yea that's true but at the same time, the fact that the p20 camera app actually starts is great news.
I'm sure the gallery app can be used, haven't looked into it myself but it should be fixable.

dladz said:
Is this a full ROM or treble?
More ROMs can only be good, thanks for the share.
This phone definitely had something special about it
Click to expand...
Click to collapse
Hi mate I am using a UK c782 any custom rom you would recommend?

Sttrory said:
Hi mate I am using a UK c782 any custom rom you would recommend?
Click to expand...
Click to collapse
So there's very few custom ROM's here for the Pro, there's one called Romaur and a Lineage ROM, haven't flashed either.
All i did was unlock bootloader, install TWRP and Root, then i've tweaked the OS so that it's faster and more stable.
Themed it and for me that's enough.
I did debrand though so you may want to look at that first, the c432 device is the EU one i think or whats predominantly used in EU countries, mine was the c782 L09 which is the single sim variant from EE.
Changing over to c432 has allowed me to get the latest updates like 120 - 128 and i think at some point b131 will drop.
The c782 afaik is still on 110 which is a bit crap.
Check the guide here to debrand: https://forum.xda-developers.com/showpost.php?p=76785704&postcount=152 if it's something you want to do.
Guide to install OTA updates when you have TWRP installed and are rooted etc: https://forum.xda-developers.com/showpost.php?p=76844754&postcount=254
Hopefully there will be more ROM's but at the moment it's extremely quiet.
Treble is a bit of an issue for us i think because the installation method requires the use of TWRP to wipe and i've read somewhere that it can't wipe correctly so it fails when you flash a treble IMG.
There's a few great guides to install treble in one of the threads over in the project treble section, take a look.
I'll get around to installing treble img's at some point but can't today.

dladz said:
So there's very few custom ROM's here for the Pro, there's one called Romaur and a Lineage ROM, haven't flashed either.
All i did was unlock bootloader, install TWRP and Root, then i've tweaked the OS so that it's faster and more stable.
Themed it and for me that's enough.
I did debrand though so you may want to look at that first, the c432 device is the EU one i think or whats predominantly used in EU countries, mine was the c782 L09 which is the single sim variant from EE.
Changing over to c432 has allowed me to get the latest updates like 120 - 128 and i think at some point b131 will drop.
The c782 afaik is still on 110 which is a bit crap.
Check the guide here to debrand: https://forum.xda-developers.com/showpost.php?p=76785704&postcount=152 if it's something you want to do.
Guide to install OTA updates when you have TWRP installed and are rooted etc: https://forum.xda-developers.com/showpost.php?p=76844754&postcount=254
Hopefully there will be more ROM's but at the moment it's extremely quiet.
Treble is a bit of an issue for us i think because the installation method requires the use of TWRP to wipe and i've read somewhere that it can't wipe correctly so it fails when you flash a treble IMG.
There's a few great guides to install treble in one of the threads over in the project treble section, take a look.
I'll get around to installing treble img's at some point but can't today.
Click to expand...
Click to collapse
Many thanks mate

Sttrory said:
Many thanks mate
Click to expand...
Click to collapse
no worries man, but id say read up before committing, this phone is so different to any device i've ever had.

Sttrory said:
Many thanks mate
Click to expand...
Click to collapse
May I know what does debrand means ?

olygopoly said:
May I know what does debrand means ?
Click to expand...
Click to collapse
If you bought you're device in the UK it's highly likely it's branded (even if there's no visual indications that it is) to a mobile network. Mine was bought via Mobiles.co.uk on 02 network and I assumed it was completely unbranded as there was no bloatware or 02 branding but apparently any updates from Huawei need to go though 02's checks before being pushed out and so updates are slooooowwww. debranding is essentially removing any ties to a network thus you get the Huawei updates as soon as they push them out.

Deano1889 said:
If you bought you're device in the UK it's highly likely it's branded (even if there's no visual indications that it is) to a mobile network. Mine was bought via Mobiles.co.uk on 02 network and I assumed it was completely unbranded as there was no bloatware or 02 branding but apparently any updates from Huawei need to go though 02's checks before being pushed out and so updates are slooooowwww. debranding is essentially removing any ties to a network thus you get the Huawei updates as soon as they push them out.
Click to expand...
Click to collapse
Thanks for the explaination

[GUIDE][xt1952-4] Cellular Data on Sprint Compatible Moto G7 Play with GSI ROMs

Moto G7 Play
CHANNEL (XT1952-4)
Sprint, Boost Mobile, Virgin Mobile
RIL/Cellular Data on GSI Based ROMs
DISCUSSION:
As most Moto G7 Play owners are already aware, our devices are fully Project Treble compatible. As such, there are several GSI builds of custom Android 9 and Android 10 ROMs that can be installed on the Moto G7 Play and booted using the stock boot image. As is typical on Sprint compatible Moto devices, users are experiencing telephony issues and broken cellular data connections after installing GSI based ROMs. After much trial and error, I have been able to establish RIL and a fully stable 4G/LTE cellular data connection on an AOSP Android 10 GSI ROM. Because the fix involves some rather unorthodox steps, system-level mods and sequential reboots, I am actively working on a simplified fix that can simply be installed via TWRP. In theory, the fix should work on any GSI based or custom ROM for the CHANNEL; however, this theory will need to be tested. The sole purpose of this thread is for such discussions and such testing.
I would urge any owners of the Boost Mobile/Virgin Mobile/Sprint Moto G7 Play to share their individual experiences regarding RIL and cellular data while using GSI based ROMs. My tentative fix is for Boost Mobile only; however, based on past Moto history and theory, a single universal fix should suffice for all Sprint dependent providers. The only key difference should be individualized APN configurations for cellular data.
NOTE: Please do not make ETA type requests on this project. I work long hours and travel regularly. I commit to XDA projects when free time permits. Also, if there are any Sprint of Virgin Mobile users of the xt1952-4, please share your experiences with cellular data on GSI based ROMs.

Viva La Android said:
Moto G7 Play
CHANNEL (XT1952-4)
Sprint, Boost Mobile, Virgin Mobile
RIL/Cellular Data on GSI Based ROMs
DISCUSSION:
As most Moto G7 Play owners are already aware, our devices are fully Project Treble compatible. As such, there are several GSI builds of custom Android 9 and Android 10 ROMs that can be installed on the Moto G7 Play and booted using the stock boot image. As is typical on Sprint compatible Moto devices, users are experiencing telephony issues and broken cellular data connections after installing GSI based ROMs. After much trial and error, I have been able to establish RIL and a fully stable 4G/LTE cellular data connection on an AOSP Android 10 GSI ROM. Because the fix involves some rather unorthodox steps, system-level mods and sequential reboots, I am actively working on a simplified fix that can simply be installed via TWRP. In theory, the fix should work on any GSI based or custom ROM for the CHANNEL; however, this theory will need to be tested. The sole purpose of this thread is for such discussions and such testing.
I would urge any owners of the Boost Mobile/Virgin Mobile/Sprint Moto G7 Play to share their individual experiences regarding RIL and cellular data while using GSI based ROMs. My tentative fix is for Boost Mobile only; however, based on past Moto history and theory, a single universal fix should suffice for all Sprint dependent providers. The only key difference should be individualized APN configurations for cellular data.
Click to expand...
Click to collapse
My signal bar keeps on going in and out on the android 10 GSIs and after I configure the data via apn settings I get Lte but the signal bar goes in and Out so it's pointless ( signal with the x no signal then lte signal for a few seconds) on the android 9 GSIs my signal is solid however no matter what apn configurations I use I'm not able to obtain LTE (same configs give me data on Android 10 GSIs minus the signal bar issue on Android 10 GSIs) can you share the steps in how you was able to fix the GSi boost mobile data and signal and the twrp zip so it can be tested (I need that tentative fix)
([emoji3590]09-09-18[emoji3590])

PoochyX said:
My signal bar keeps on going in and out on the android 10 GSIs and after I configure the data via apn settings I get Lte but the signal bar goes in and Out so it's pointless ( signal with the x no signal then lte signal for a few seconds) on the android 9 GSIs my signal is solid however no matter what apn configurations I use I'm not able to obtain LTE (same configs give me data on Android 10 GSIs minus the signal bar issue on Android 10 GSIs) can you share the steps in how you was able to fix the GSi boost mobile data and signal and the twrp zip so it can be tested (I need that tentative fix)
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Yes. That's what this thread is for. I'm actively working on a simplified fix that can be installed with TWRP, so that data is enabled and stable on reboot. I'm in hopes that this will work on Sprint and its subsidiary networks.

Viva La Android said:
Yes. That's what this thread is for. I'm actively working on a simplified fix that can be installed with TWRP, so that data is enabled and stable on reboot. I'm in hopes that this will work on Sprint and its subsidiary networks.
Click to expand...
Click to collapse
Can you post the manual method for us boost users that would like to have functionality with GSIs now since the twrrp zip is still in works and there isn't a eta on it
([emoji3590]09-09-18[emoji3590])

PoochyX said:
Can you post the manual method for us boost users that would like to have functionality with GSIs now since the twrrp zip is still in works and there isn't a eta on it r
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
The "manual" method is unorthodox, rather sloppy, and overall unreliable (it does not always survive a reboot). This is the very reason I'm devising a simplified method. Simply put, this is a work in progress. I now know why the fix doesn't always survive a reboot, and I am implementing that fix into the simplified method. My goal is to post a fix that is both stable and universal for all owners of the Sprint compatible CHANNEL. I do not have an ETA. I work long hours and travel frequently, so I commit time to this and other Android projects when I have extra time. The unofficial TWRP for the CHANNEL, created by @Spaceminer, is fully stable and functional for all intents and purposes. It performs a full backup of all pertinent partitions, wipes relevant partitions, and installs zip files written with the Edify updater-script/update-binary.

Anyone can bring me FIRMWARE FOR XT1952-4 US RETAIL

Fdraco10 said:
Anyone can bring me FIRMWARE FOR XT1952-4 US RETAIL
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/channel/official/RETUS/

On an update I am making progress on my data fix mod for the Sprint compatible Moto G7 Play. I'm working out edits to the apns-config.xml file now for my Aroma installer.

Viva La Android said:
On an update I am making progress on my data fix mod for the Sprint compatible Moto G7 Play. I'm working out edits to the apns-config.xml file now for my Aroma installer.
Click to expand...
Click to collapse
That's fantastic
/09/[emoji645]/[emoji725]/
---------- Post added at 10:10 AM ---------- Previous post was at 09:38 AM ----------
Viva La Android said:
https://mirrors.lolinet.com/firmware/moto/channel/official/RETUS/
Click to expand...
Click to collapse
I was using retail firmware on my boost mobile G7 play and I was getting locked sim is it because my device isn't unlocked, so I had to switch back to the sprint firmware and then the locked sim went away
/09/[emoji645]/[emoji725]/

PoochyX said:
That's fantastic
/09/[emoji645]/[emoji725]/
---------- Post added at 10:10 AM ---------- Previous post was at 09:38 AM ----------
I was using retail firmware on my boost mobile G7 play and I was getting locked sim is it because my device isn't unlocked, so I had to switch back to the sprint firmware and then the locked sim went away
/09/[emoji645]/[emoji725]/
Click to expand...
Click to collapse
The Boost Mobile xt1952-4 is locked to the Boost Mobile network. There may be a user-end mod or workaround to enable GSM SIM support for other carriers but I've honestly not researched that topic. I do know the Boost xt1952-4 has quad-band GSM capabilities, so the network lock was undoubtedly put in place by Sprint.
Are you saying that you were using GSM providers while on the retail firmware?

Viva La Android said:
The Boost Mobile xt1952-4 is locked to the Boost Mobile network. There may be a user-end mod or workaround to enable GSM SIM support for other carriers but I've honestly not researched that topic. I do know the Boost xt1952-4 has quad-band GSM capabilities, so the network lock was undoubtedly put in place by Sprint.
Are you saying that you were using GSM providers while on the retail firmware?
Click to expand...
Click to collapse
Na I was using my boost sim card (just tried retail since it doesnt have carrier bloat until your fix was ready so I can transfer to a android 9 GSI for daily driver) it was working for a bit calls and Lte and then I got sim card locked please do a reboot cycle and if issue still persist call your service provider so I reflashed boost firmware and the sim lock was removed (My G7 play is not networked unlocked I think if it was I could of used retail firmware with no issues)
/09/[emoji645]/[emoji725]/

PoochyX said:
Na I was using my boost sim card (just tried retail since it doesnt have carrier bloat until your fix was ready so I can transfer to a android 9 GSI for daily driver) it was working for a bit calls and Lte and then I got sim card locked please do a reboot cycle and if issue still persist call your service provider so I reflashed boost firmware and the sim lock was removed (My G7 play is not networked unlocked I think if it was I could of used retail firmware with no issues)
/09/[emoji645]/[emoji725]/
Click to expand...
Click to collapse
Have you tried using the retail firmware but keeping the Boost (Sprint) radio firmware? In other words, install all files of the retail firmware except NON-HLOS.bin and fsg.mbn. This will allow you to run retail firmware with the Boost baseband radio.

Viva La Android said:
Have you tried using the retail firmware but keeping the Boost (Sprint) radio firmware? In other words, install all files of the retail firmware except NON-HLOS.bin and fsg.mbn. This will allow you to run retail firmware with the Boost baseband radio.
Click to expand...
Click to collapse
I didnt try that..... I'm going to apply it
/09/[emoji645]/[emoji725]/

PoochyX said:
I didnt try that..... I'm going to apply it
/09/[emoji645]/[emoji725]/
Click to expand...
Click to collapse
Somebody in one of the other threads tried it sometime back and had good results with it. And, as you know already, no real danger in trying it. Not going to hard brick your device. At worst, you may have to reinstall a full firmware package to restore your device.

Viva La Android said:
Somebody in one of the other threads tried it sometime back and had good results with it. And, as you know already, no real danger in trying it. Not going to hard brick your device. At worst, you may have to reinstall a full firmware package to restore your device.
Click to expand...
Click to collapse
You said you was putting the fix in a aroma installer does that mean the fix is going to have multiple options in the way it can be applied?
/09/[emoji645]/[emoji725]/

PoochyX said:
You said you was putting the fix in a aroma installer does that mean the fix is going to have multiple options in the way it can be applied?
/09/[emoji645]/[emoji725]/
Click to expand...
Click to collapse
Yes. For Sprint, Boost Mobile, FreedomPop and TextNow.

Viva La Android said:
Yes. For Sprint, Boost Mobile, FreedomPop and TextNow.
Click to expand...
Click to collapse
Omgggg when is it going to be ready this is so exciting I so want to use a GSI as a daily driver
/09/[emoji645]/[emoji725]/

Viva La Android said:
Somebody in one of the other threads tried it sometime back and had good results with it. And, as you know already, no real danger in trying it. Not going to hard brick your device. At worst, you may have to reinstall a full firmware package to restore your device.
Click to expand...
Click to collapse
Back on retail followed your suggestion so far no sim lock, waiting patiently for your GSI service fix for us boost users
([emoji3590]09-09-18[emoji3590])

PoochyX said:
Back on retail followed your suggestion so far no sim lock, waiting patiently for your GSI service fix for us boost users
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Glad it worked for you. @PoochyX, I am fully aware you need this fix. You've sent PM,s and made several comments stating your needs. Please don't ask for ETAs or make repeated posts regarding your need for this fix. Again I'm fully aware. I work 50 plus hours a week and do my best to dedicate time to my XDA projects. When it's ready you'll be the first to know. No worries.

Viva La Android said:
Glad it worked for you. @PoochyX, I am fully aware you need this fix. You've sent PM,s and made several comments stating your needs. Please don't ask for ETAs or make repeated posts regarding your need for this fix. Again I'm fully aware. I work 50 plus hours a week and do my best to dedicate time to my XDA projects. When it's ready you'll be the first to know. No worries.
Click to expand...
Click to collapse
Alright thanks , I just want to get off stock [emoji23][emoji1787][emoji16][emoji1787][emoji16] I will just patiently wait
Sent from my moto g(7) play using Tapatalk

Has anyone gotten OOS 12 on the IN2019 (Verizon OnePlus 8)?

Been looking for a solution to convert this device to the global variant successfully with the modem working or to get Verizon to release the update. It's been one year since Android 12 has been released and it doesn't seem like OOS 12 is coming anytime soon, so if anyone knows how to get the modem working on the global variant, I'd be glad.

The hardware and kernel source are fundamentally different on the Verizon model. Even if you somehow got global firmware installed with working data, you'd have a lot of other bugs and glitches because the hardware isn't compatible with the Global OS.

FoxyDrew said:
The hardware and kernel source are fundamentally different on the Verizon model. Even if you somehow got global firmware installed with working data, you'd have a lot of other bugs and glitches because the hardware isn't compatible with the Global OS.
Click to expand...
Click to collapse
It works quite well. on the V model (that's what I have). but you need to back up your modem for data. It's best to reset to 11 factory. Then you can run ROMs that are OS 12.

Thorin_Stone said:
It works quite well. on the V model (that's what I have). but you need to back up your modem for data. It's best to reset to 11 factory. Then you can run ROMs that are OS 12.
Click to expand...
Click to collapse
It works? That's awesome! Can you please share the link to the guide you followed to do it, pretty please?

Sнаđошƒаӽ said:
It works? That's awesome! Can you please share the link to the guide you followed to do it, pretty please?
Click to expand...
Click to collapse
I believe he means that you can run Android 12 ROMs, not custom ROMs, unless I misread?

Sнаđошƒаӽ said:
It works? That's awesome! Can you please share the link to the guide you followed to do it, pretty please?
Click to expand...
Click to collapse
I did not use a specific guide. I have been rooting the phone for some time and found that I could flash os global using a fastboot flash ROM. If you root your phone and save the stock os the 11 modems you can replace it in the global rom.
I will correct myself and say that I don't remember for sure if global will work (for modem replacement) but you can get custom ROMs to work well with that method.
I would have to go back and sort through for the links or try again to be sure. But if you know what you're doing, it is pretty hard to brick the phone. So play around with other guides. (with your own risk and discretion involved).
You can even run android 13 on the V model( not good IMO. buggy).

Thorin_Stone said:
It works quite well. on the V model (that's what I have). but you need to back up your modem for data. It's best to reset to 11 factory. Then you can run ROMs that are OS 12.
Click to expand...
Click to collapse
Which rom u used?

Mr Hassan said:
Which rom u used?
Click to expand...
Click to collapse
Deerpfest works for sure

Thorin_Stone said:
Deerpfest works for sure
Click to expand...
Click to collapse
I think stock rom u talk about

Thorin_Stone said:
I did not use a specific guide. I have been rooting the phone for some time and found that I could flash os global using a fastboot flash ROM. If you root your phone and save the stock os the 11 modems you can replace it in the global rom.
I will correct myself and say that I don't remember for sure if global will work (for modem replacement) but you can get custom ROMs to work well with that method.
I would have to go back and sort through for the links or try again to be sure. But if you know what you're doing, it is pretty hard to brick the phone. So play around with other guides. (with your own risk and discretion involved).
You can even run android 13 on the V model( not good IMO. buggy).
Click to expand...
Click to collapse
I don't think the stock Verizon modem works on the global ROM? Or did it work for you?

Xryphon said:
I don't think the stock Verizon modem works on the global ROM? Or did it work for you?
Click to expand...
Click to collapse
Stock modem does not work. That is for sure. I've moved to the pixel 7 Pro so I won't be messing with the one plus anymore.