yashsingh1/xdaforums huggingface dataset:
[OPPO Find X3 Pro] ChakraRocks:
Hi - I am in the same boat as you. I just bought a Oppo Find x3 Pro for my girlfriend and was amazed to see its IMEI fail the T-mobile checker. My Vivo x60 pro plus is allowed. That is odd since Oppo's parent company also makes the OnePlus which is offered by T-mobile so it can't be anything hardware related. It even has a few more Bands than my Vivo has.

I was worried about my Vivo since VoLTE wasn't provisioned but got lucky when I updated to the new Origin2.0 OS (Ocean)

So the hope is that once the Oppo Find x3 Pro is allowed to update to the new ColorsOS 12 that maybe it will be able to provision?

When I updated my Vivo, I got a prompt that said 'You aren't enabled for VoLTE yet, you want to enable it?' So once I hit yet, it set it up and it works great.

One worry is that the code I was using to check my Vivo was *#*#4636#*#* didn't do anything on the Find x3 Pro. Are there other codes for the Oppo?
[P3600 General] danielp:
Hi,

Yesterday, I had to do one of those ubiquitous soft resets we always have to do with Windows Mobile... but instead of getting a soft reset, my trinity totally hard reset itself! (and no, I didn't touch any buttons while pressing the stick in there)

I profited from the occasion of losing some of my data (backup was a couple of weeks ago) to upgrade the ROM. That all went fine until yesterday evening, when I did a soft reset with the stick and got a hard reset AGAIN!

Does anyone know where this can come from? How to fix this annoying problem?!

Thanks!

Daniel
[P3600 General] pjvieira:
Hi Daniel,

I had the same exact problem with certain Roms...

Just don't know if it can be hardware problem, but try using the original HTC rom for a while to make sure everything's OK.

Best regards
[P3600 General] boma23:
Hi

My trinityis sufferng from the same problem, and it's getting progressively worse. From it originally happening once every few weeks, I can now re-flash and it will hard reset as soon as a day later (usually once i've re-installed everything...)

I've tried lots of different and reportedly stable ROMs, the latest being FlixNOver and an excellent German WWE Manilla 2D one floating around whos name i forget.

I am now assuming my trinity is dying, with a hardware related issue.

What is puzzling is that information previously written to the phone often remains and is acessible after then hard-reset. If this was Windows XP I'd suggest the Hard Drive was was corrupting and Windows was losing it's profile.

Anyone any ideas?
[Nokia 4.2 Guides, News, & Discussion] pm-cz:
Hello,

I had this phone as a backup one laying around, and when my present phone died two weeks ago, I have updated the system and unfortunately found out the hard way that I lost all payment cards in Google Pay. The 00EEA variant is not "Google Play Certified" at least from 3.150 (and its variants) and the CTS profile match fails. Adding the ID did not help, nor reporting the issue. I hoped that the new firmware 3.240 will fix the issue, but it did not. The bootloader has been locked and everything seemed OK:

Device info
Device tampered: false
Device unlocked: false
Device critical unlocked: false
Charger screen enabled: false

I think this problem happened to me in past on Android 9 or 10 as well, and then it has been fixed then, but not this time.

Over last 4 days, I have tried everything including the factory reset, going back to previous slot, even flashing the original 3.150 in EDL mode in one of the slots, to check the problem always persists. During that time I started to be suspicious, as the device fingperprint for newest firmware is Nokia/Panther_00EEA/PAN_sprout:11/RKQ1.200928.002/00EEA_3_240:user/release-keys, but the vbmeta fingerprint is Nokia/Panther_00WW/PAN_sprout:11/RKQ1.200928.002/00WW_3_240:user/release-keys and similar for 3.150 firmware variants.

The WW/EEA variant is stored in oem partition. In the end I found a solution how to fix it on my phone, but it may be dangerous if something goes wrong and it WILL erase user data:

You have to enable developer mode and permit OEM unlocking. Then you have to unlock the phone in fastboot, change the skuid and then you may relock the phone again. The command to check the present skuid:

fastboot oem repair skuid get

This will display something like skuid=600EEA (please note the leading 6 which is not displayed)

fastboot oem repair skuid set 600WW

will change the skuid to match the one in vmbeta. After new setup/restore of the Backups where posible the device is Google Play certified again.

I am intentionally not giving other commands here needed to reboot to fastboot or to unlock/relock the phone to limit the risks for those not used to such things, but they can be found in other threads here.
[E 2015 Original Android Development] althafvly:
​

LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

GPL compliance:

Device tree source code: LineageOS/android_device_motorola_surnia

Kernel source code: LineageOS/android_kernel_motorola_msm8916

Working:

Camera (and flashlight)

WiFi

Battery LED

Bluetooth

Telephony (Calls) & Data

Audio (Record and Playback)

Video Playback

Sensors

GPS

VoLTE

Bugs:

Encryption

Selinux enforcing

Ui is laggy

Nothing (?)

Downloads:

Download

Notice:

No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

Installation:

Reboot to recovery

Format /system, /data and /cache

Install LineageOS zip package

Important notes:

* Required * firmware version must be based on Marshmallow/Lollipop

GApps can only be flashed on clean installs.

Formatting data (all user data is wiped, including internal storage) is a must if Stockrom was previously installed and device was encrypted.

Credits & collaborations:

All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

DONATIONS : Paypal

Contributors

althafvly, chil360, squid2, jeferson1979, Alberto97

Source Code: https://github.com/MOTO-M8916
[E 2015 Original Android Development] ThePiGuy3141:
It's amazing to see such an old device get the latest Android version. Thank you so much for keeping the device alive! I will try the ROM tommorow.
[E 2015 Original Android Development] jonta0:
Surnia with Android 12... I dont believe it ! OMG...

Any plans to become official?
[E 2015 Original Android Development] tales59:
Unlocked a bootloader for the first time and installed 19.0 to my XT1527 (US) with stock Lollipop 5.1 which had been upgraded from 5.02 OTA. Wasn't able to use ADB to sideload with the 19.0 recovery but the 17.1 recovery was able to sideload this 19.0 ROM.

As part of the 3g shutdown, US carriers are restricting LTE access to VoLTE-capable phones. I was curious to see if my XT1527 could survive these restrictions with a fresh VoLTE-capable OS. AT&T has a whitelist and surnia didn't make the cut. Not sure how AT&T determines if a phone is VoLTE-capable but it might not permit XT1527 access regardless of the OS or VoLTE capabilities.

Quick answer: Not yet and perhaps not ever. Since early March 2022, I've not been able to access LTE on Stock Android 5.1, official Lineage 17.1 or unofficial 19.0. I have 2g/3g only without MMS. But other Lineage features work as advertised. It's pretty fast without Gapps. Both the unofficial 17.1 and the unofficial 19.0 builds are impressive development efforts.

There is no stock Marshmallow 6.0 for the US XT 1527 and the upgrade from 5.02 to 5.1 disabled band 12 from US phones. Evidently, Moto didn't want the hassle of certifying the XT 1527 for VoLTE and instead chose to disable band 12 at the request of one major carrier that wanted to use 12 for VoLTE traffic. I'm wondering if that could cause LTE-access problems when flashing 19.0 on top of 5.1. The official 17.0 instructions were clear that we should start with stock Marshmallow but I wasn't sure about trying non-US ROMs.

Perhaps reinstalling Lineage 17.1 starting with a non-US 6.0 (or US 5.02) stock ROM would restore LTE. Another possibility is to switch within my MVNO to a T-mobile SIM (another major US carrier.) Anyone know if any US carrier will permit surnia access to LTE on any OS after the 3g shutdown is complete?

Also wondering if VoLTE is implemented in a proprietary way by US carriers that hinders open source OS development work.

Thanks again for a nice effort. The XT1527 is the only smartphone I've ever used...will hate to give it up if/when both LTE and 3g access are removed.
[E 2015 Original Android Development] @irtime:
I have tried this rom today and most stuff works fine. i have encountered one issue with the "3 button" controls setting turned on, the trebuchet launcher crashes if you try to see all the open apps. This doesn't occur if i use the " nova launcher". Keep up the good work.
[E 2015 Original Android Development] althafvly:
Updated to 12L (check OP for link)

- Fixed mobiledata
[E 2015 Original Android Development] tales59:
The "laggy UI" seemed to get worse over time in the week or so that I tried the first cut at 19.0 for Moto E 2015. Even though I didn't load extra software, by the end of the week it struggled to bring up a PIN-number screen unlock without displaying it on the Lineage logo simultaneously. I don't remember it doing that after 19.0 was first installed. Perhaps freeing up memory or other resources when unneeded would improve UI performance.
[E 2015 Original Android Development] goosnarrggh:
Not just US carriers. As far as I know, there does not exist any fully open-source VoLTE implementation on any phone, for any carrier, anywhere in the world.
[E 2015 Original Android Development] nabav:
My phone has a low battery

I think I need to change it or maybe I should buy a used E2.

What do you recommend?

I hope it will be supported for years to come. I don't want to leave it. For a basic use, it is the top. It is comfortable in the hands. I am lost with recent smartphones. Too big for my taste.

We need more E2

Thanks for the support!
[E 2015 Original Android Development] Viva La Android R.I.P.:
There are new E2 batteries available on both eBay and Amazon for around $6, and that typically includes a small toolkit for the job. Here is a listing for a brand name FT-40 battery for the E2 for $5.42 w/free shipping.

Battery FT-40 SNN5955A For Motorola XT1526 XT1528 Moto E XT1527 2nd Original | eBay

Compatible Models: Motorola XT1526 XT1528 Moto E XT1527 2nd Cricket. Battery Capacity: 2240mAh. Quality : Original.

www.ebay.com
[E 2015 Original Android Development] nabav:
For sure, but I need an hot air gun to detach the screen before replacing the battery. I don't know if I can do without it.
[E 2015 Original Android Development] Viva La Android R.I.P.:
The only tools I used were thin plastic edging tools (resemble guitar picks), a pry tool, and a T4 Torx security screwdriver. When reassembling, some 3M adhesive strips work nicely for getting the display back nice and snug. A regular hair dryer can, of course, be used to warm the edges of the display first, in order to loosen the underlying adhesive and make prying.a bit easier. On the three Moto E 2nd Gens to which I've done repairs, I haven't needed to resort to heating the screen first.
[E 2015 Original Android Development] Viva La Android R.I.P.:
Also, I should mention that when you are able to run the plastic edging tool all the way around the screen -- essentially breaking the seal -- use a playing card to assist you in prying the display from the phone body. The E2, as you probably know, has a LCD + touch screen digitizer display assembly. A playing card helps greatly with getting under the digitizer versus the edge of the LCD, which can be ripped from the digitizer if you're not careful.

OP, I do apologize for posting off topic in your thread.
[E 2015 Original Android Development] skpao:
I'm currently running LineageOS 17.1 with A10 and doing great. I would like to try 19.1 with A12. But I have a doubt because the opengapps.org site only shows gaspps up to A11 and this ROM is A12. Could you help me and tell me if they exist and where I can download the gapps for A12
[E 2015 Original Android Development] skpao:
God wants. Since we stayed in the official 17.1 with android 10
[E 2015 Original Android Development] nabav:
I have some tools but they are very cheap, including a torx and a plastic triangle, so pretty useless. I think I can use an old phone card. Let's say that the most difficult task is to detach the screen, then I hope to be able to remove it with the tools I have. I have to buy 3M double-sided tape or glue. as well. I will keep you informed as soon as I have the spare parts.

Thank you for your suggestion
[E 2015 Original Android Development] Viva La Android R.I.P.:
No problem. Yeah once you get the screen detached from the midframe, the T4 Torx will remove all screws holding the logic board in place, allowing you to then access the battery Take care when detaching.the display not to rip the flex cable connecting the display to the board. Pry tools won't get anywhere near it, but when prying it loose use caution .
[E 2015 Original Android Development] skpao:
I put ROM 19.1 to test and had to restore the save again and continue with the official version 17.1. This 19.1 everything worked for me but when I open the PHONE application, MESSAGES and CONTACTS close automatically. Turn back because without these applications it is impossible to have a mobile.
[E 2015 Original Android Development] nabav:
Is unlocking the bootloader always to be done? I have lollypop in this other phone, not Marshmallow.
[E 2015 Original Android Development] ThePiGuy3141:
Yes, bootloader must be unlocked in order to flash non-OEM software
[E 2015 Original Android Development] Cortom77:
Hello. I think I made a mistake. My phone was running lineage 17 (and recovery) and I saw this new version and I tried to install it. As it was required to have marshwallow/lollipop preinstall, I format the data, the cache and also system and partition. But now I'm not able to install and old version

So the state of my phone right now is : start on bootloader. I am able to go in recovery mode (twrp-3.6.1_9-0-surnia.img), but when i try to follow the guide https://www.phonandroid.com/forum/t...mware-stock-xt1524-surnia-oraeu-5-1-1.142431/

at the first line "fastboot flash partition gpt.bin" I got the error

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:partition: not found

target reported max download size of 268435456 bytes

sending 'partition' (32 KB)...

OKAY [ 0.409s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

What's wrong ? If somebody could help...

my phone is a Moto E LTE (surnia XT1524 8GB P3 read from the bootloader=
[E 2015 Original Android Development] kurtn:
Official return to factory image

Unlocking the Bootloader | Motorola Support US

Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.

motorola-global-portal.custhelp.com

I doubt your surnia was on an incompatible factory image before you started with custom ROM. So just flash anything you want.
[E 2015 Original Android Development] Cortom77:
Hy. Sorry but I don't understand your answer. Could you be more specific ?

Your link points to how to unlock a motorola phone, but the bootloader is already unlocked (I did it 6 months ago when I flashed lineage 17).

Right now the phone loops on the bootloader and it is displayed : "Device is UNLOCKED. Status Code: 3"

I tried, today after your answer, to unlock again but the answer was :

(bootloader) Not supported command in current status!

FAILED (remote failure)
[E 2015 Original Android Development] kurtn:
Scroll down in the linked website. "Return to factory image"

What happens when you try to flash lineageOS 17.1 ?
[E 2015 Original Android Development] Cortom77:
No : I can only boot on fastboot : I formatted all on the phone even system and partition (yes I know it was a big mistake).

So I ran lineage 17 and recovery lineage 17 and I wanted to install lineage 19. But to do this I need to have lollipop on the phone. So I tried to flash a stock ROM, but before i formatted all.

and know the phone loop on fastboot and I only be able to flash TWRP not lineage recovery?

when I try to flash the stock rom I get (enter in recovery mode (twrp), then adb sideload XT1524_SURNIA_RETGB_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml.zip

the operation failed : Invalid zip file format
[E 2015 Original Android Development] Cortom77:
Update : I am able to flash lineage recovery 19. But when I tried adb sideload (on linux) I get this

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

I have already used this command on the same computer with this phone before I make the mistake...
[E 2015 Original Android Development] Cortom77:
And when I tried to update from sdcard1

with XT1524_SURNIA_RETGB_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml.zip

after passing through signature verification failed I Got this error

E:Failed to find update binary META-INF/com/google/android/update-binary
[E 2015 Original Android Development] mnd123:
If I understand it correctly - you are trying to install the stock ROM 6.0 for the surnia, and after that you want to install Lineage?

Why don't you try to skip the stock ROM and just flash Lineage right away? If you already have working TWRP.
[E 2015 Original Android Development] kurtn:
Original Motorola firmware is no recovery flashable zip.
[E 2015 Original Android Development] Cortom77:
Well, it's that and not, I tried also to (re)flash lineage 17 and 19 but as the phone is completly formatted the lineage rom flash doesn't work

from adb sideload see the failure in my previous post

from the sdcard1, i tried to flash previous version of lineag that has worked on this phone (lineage--17.1-20211112-nightly-surnia-signed.zip). the process seems to work fine

Installing update...

Target: .../...

Patching system image unconditionally

script succeeded: result was [1.000000]

But when I try to reboot - It goes directly to fastboot

It was written in the guide for flashing lineage 17

Required * firmware version must be based on Marshmallow
[E 2015 Original Android Development] Cortom77:
ok. So what can I do ?
[E 2015 Original Android Development] Cortom77:
and when I tried to flash lineage-19.1-20220402-UNOFFICIAL-surnia.zip (after formatting data/factory reset, cache partition, system partition) I got these errors

E: failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file

update 15h00 : By chance I scrolled down the fastboot menu and I selected BP tools and there miracle : the phone launch lineage 17 :oops:.

But when I restart it It is always the fastboot menu that appears... (so I have to select BP tools) An idea ?
[E 2015 Original Android Development] kurtn:
Is a volume button jammed?
[E 2015 Original Android Development] Cortom77:
No button are jammed.

Well right now it is ok : I just have to push the power button at the beginning (after restarting the mobile) because it stays on the fasboot screen. but it's not a problem

And here is my experience return with trying to install lineage 19:

- installing lineage 19 recovery (20020402): ok

- entering recovery mode and format cache and data (1st option)

- apply update from adb

- trying to sideload lineage 19 or 17

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

- reinstalling lineage recovery 17 : ok

- format data/factory reset

- try to sideload lineage 19 :

adb sideload lineage-19.1-20220402-UNOFFICIAL-surnia.zip

serving: 'lineage-19.1-20220402-UNOFFICIAL-surnia.zip' (~0%) adb: failed to read command: Success

The phone stays blocked :

Finding update package

Opening update package

Verifying update package

- power off the phone and restart -> back to lineage 17 reinit

I read that the phone needs to be under marshmallow/Lollipop but as I can't downgrade from lineage 17...

my phone is an XT1524
[E 2015 Original Android Development] nabav:
Will there be new releases soon? I hope I can try it and that it becomes official and stable. Thanks for supporting this little smartphone

Good job
[E 2015 Original Android Development] kurtn:
19.1 will probability not gain official status. The kernel is too old.
[E 2015 Original Android Development] nabav:
And this will concerne other OS like CrDroid, Arrows etc... if will be developed; at the same time, we wait for a new kernel... :)
[E 2015 Original Android Development] kurtn:
Other OS are not so picky with official status. Best chance for lineageOS is: someone has to build iptables into android 12.
[E 2015 Original Android Development] O Tet:
Google play services does not work, why?
[E 2015 Original Android Development] kurtn:
Because you didn't install GApps?
[E 2015 Original Android Development] O Tet:
i already have the GApps installed

maybe android 12L only supporting SDK 32
[E 2015 Original Android Development] tcecyk:
can you hook me up with the device kernel requirements for 19.1 ?

as with harpia/osprey, MSM8916 is well supported in mainline, I wonder if one can ever swap the vendor kernel for an aosp install on the SoC line.
[E 2015 Original Android Development] kurtn:
Changelog 26 - Tailored Twelve, Audacious Automotive, Neat Networking, Devoted Developers

XIX

lineageos.org
[E 2015 Original Android Development] coolshesh40@gmail.com:
Hello Guys,

I have Moto E 2015 3G (Otus) can i flash this ROM , i want to try android 12 ,Please reply
[E 2015 Original Android Development] kurtn:
No, you can't.
[E 2015 Original Android Development] crazix:
Does anyone have link to Marshmallow update? My Volte is not working
[E 2015 Original Android Development] ThePiGuy3141:
https://xdaforums.com/t/stocks-firmwares-moto-e-2015-surnia-otus.3113235/
[E 2015 Original Android Development] wryunj:
These patches might help some of the performance issues:

https://android-review.googlesource.com/q/topic:%22slow_gpu%22

(just noticed them as part of Glodroid)
[E 2015 Original Android Development] nabav:
Has development been abandoned? Hopefully we can get a new update for Moto E2. Lineage OS 17.1 is good but no longer updated. Perhaps 19.1 is a bit heavy to still be supported
[E 2015 Original Android Development] kurtn:
There are unofficial builds.

Index of /ubs/android/LineageOS
[E 2015 Original Android Development] nabav:
Thank you but the last is updated on the 2022-07-07. Have you tried if these are good and stable rom?
[E 2015 Original Android Development] kurtn:
I can't remember.
[E 2015 Original Android Development] ThePiGuy3141:
From 18.1 onwards, the performance isn't the best, the phone often lags and freezes. 17.1 was the last version that didn't lag much.
[E 2015 Original Android Development] TimpaXxX:
Hello everyone! I could use microg?
[E 2015 Original Android Development] kurtn:
Yes. /e/ just built one with integrated microG
[E 2015 Original Android Development] TimpaXxX:
What version of Google apps you used for this ROM?
[E 2015 Original Android Development] SurniaJoseph:
Use Lite Gapps API 32 (Recovery versión)
[E 2015 Original Android Development] SurniaJoseph:
Somebody can update this rom to LineageOS 20 with Android 13?