Related
Hi guys!
Recently i buy this Photon Q 4G LTE Sprint to my wife's birthday.
It's a wonderfull device with a nice hardware, but the best is the external keyboard (She likes it, because his old device was Motorola dextr, and she was used to), but we're from brazil and my first difficulty was to find a rom that support drivers without bugs.
So here i was: My first try was MIUI. I unlocked my bootloader, rooted and installed TRWP. Didi Backup, formated and installed MIUI, :good:
First i tryed with Kernell the UFO developed for it, and the device don't boot. After i tryed just the rom, but it has no modem or wifi. So i flashed up the stock rom modem img and worked fine.
But apks like "retrica" doesn't work with it, bringing black photos and others apks made for instragram. I love this rom and i have installed in my Xperia Play. It works perfect, but in this device have a lot of bugs, so i give up.
I know how to use it with bugs, but not my wife. Then i had to try another one.
I downloaded Cyanogenmod CM10.1, CM10.2, CM11 nightly, snapshot. Then after try all "Xt897" roms, i tryed all "moto_msm8960".
I can't get in any of this roms make my wifi or 3G work. I believe that modem is not compatible. Even if i tryed to flashed stock modem after, i still had no signal at all. No IMEI, no MAC Address, nothing. :crying:
This device have few alternative roms, so i decided try to translate the rom with less bugs at all. I picked up the stock rom JellyBeans 4.1.2, but this was my second failure. A language patch is something that you don't find in market, and to disassembly entire rom and work in a translate is something beyond my knowledges.
So i have an answer to someone that know how to do a fix patch to wifi in cyanogenmod(Specific "cm-11-20140518-NIGHTLY-moto_msm8960.zip" ), or someone good in translate rom, or input a language in stocked rom, like The Solutor did in " [Full ICS ROM] Multilanguage/Toggle2g /STK/Tethering" (but the rom he used was 4.0.4 and it have bugs).
I will be grateful for any help. :fingers-crossed:
Hmm, what's the language you want (CM11 already have lots of them - not in the list?), and what WiFi/3G problem are you having? And you also failed to RSD the phone back to stock?
My recommendation is you first sort the RSD thing out and get the phone back to stock 4.1.2, and flash everything from that onwards. Assuming that you don't do anything wrong in the process, you should have no quirks with WiFi/3G.
Sent from Google Nexus 4 @ CM11
Try MoreLocale2 for the stock ROM language issues.
As for the CM issues... I agree with Andy, if it works in stock form, it "should" work on CM - at least that has been my experience.
You are clean wiping / factory resetting before or after flashing CM yes? I see you have done this step for MIUI, so I am thinking that you have already done this step...
If you have, can you provide logs from CM if the wiping/RSD'ing doesn't work?
Thx for help guys...
AndyYan - The language i need is Portuguese(Brasil) and it has on CM 11 and MIUI.
I did it as you said. I downloaded stock from here:
http://sbf.droid-developers.org/phone.php?device=3
Rom version: Android 4.1.2 - Blur_Version.98.10.5.XT897.Sprint.en.US)
And flashed by RSD.
Everything ok till here. No errors, nothing wrong. Wifi working as well, and the network.
My MIUI was taken from here: http://forum.xda-developers.com/showthread.php?t=2444449 (GSM one).
Cool rom, it has wifi and network, but camera bugs with some apks. For me ok, but not for my wife. So this rom was discarded.
CM i dwonloaded from here: http://download.cyanogenmod.org/?device=moto_msm8960
The last one was: cm-11-20140521-NIGHTLY-moto_msm8960.zip (i tryed all of then "XT897" and "moto_msm8960", but none of them could get my network working. No wifi, no IMEI, no MAC, no wifi).
CM was my hope, because it has my language, but in all tries i did the wipe in cache, dalvik, system, factory, even internal memory, before installing, and cache or dalvik after flash. I tried this in all (tried not wiping too) and still has no modem.
After this, just for try, i flashed stock modem "NON-HLOS.bin". Still got no modem in any CM roms.
arrrghhh - i did try "MoreLocale2" for the stock rom, and "Set Locale and Language" (and more). This softwares did a nice job for keyboards and apks, but system stays intact in english. It need to be a real translation for my wife.
My guess is that this issue can be easily solved.
If all JB roms have the same system(at least for "moto_msm8960" processor kind ).
This ROM is generic for Motorola Atrix HD, Electrify M, Photon Q, RAZR HD, and RAZR M right?
Razr HD is a type of phone that came to my country.
Is it possible compile a system from Brasil career stock, for this phone with modem and anything else from my stock rom? Does it will crash my phone?
Please provide logs from the latest build of CM after booting and attempting to engage/connect to wifi.
Logs??
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Skymidt said:
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Click to expand...
Click to collapse
CM does create logs. If you're not familiar with them, the easiest way is to use an app from the Play Store... which I'm not sure how you will manage without wifi or mobile data, and I assume you are not familiar with adb.
I can go thru the detail, but it's a bit involved. Perhaps this thread will help you?
Once you know how adb works, there's actually an easier method than using adb logcat to output to a file - there are logs stored in '/data/logger'. So:
Code:
adb root
So you can have the permissions to pull the files, then pull them:
Code:
adb pull /data/logger
Will pull all of the log files to wherever your command prompt is. If you 'cd' (change directory) to your desktop, doing the adb pull will send all the log files to your desktop.
Let me know if you have any questions, good luck.
Logs from Adb
Yeap! I'm familiar with ADB!!
(i'm not expert in it, but i already did something with that...)
I don't know exactly what are you lookin for, so i did two logs.
First a complete boot:
Code:
adb reboot system
adb logcat -v long > boot_log.txt
And one for especific modem log from boot
Code:
adb reboot system
adb logcat WifiStateMachine:E *:S -v long > just_wifi_error.txt
(I believe this this won't help u a lot?!)
The first one is the most complete solution for this and have all the boot infos, errors and other things.
If am i wrong please say the correct command to use.
I forgot something...
In filemanager i can't access internal storage.
It shows /storage/emulated/0, and points to nothing.
If i'm right, this was a well know bug on CM 10.2, which supposedly been fixed in CM 11 right?!
I think that information can help to solve this bug...
Please try the adb pull command I sent... Those logs are not very helpful, and quite difficult to read.
However, I have a feeling if you use RSD Lite to flash everything back stock, confirm it works, then start with the latest CM, I'd be curious if it works.
Also, someone mentioned they needed to install the CM10.2 snapshot before going to CM11 - or else BT and wifi did not work.
Eureca...
That is something that i didn't tried! I'd never flashed CM 10 in first!!!
I'm downloading "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip ".
Fisrt i'll flash stock "Blur_Version.98.10.5.XT897.Sprint.en.US" with RSD.
Then fastboot "logo.bin" (to avoid warning unlocked), and TRWP(my stock have a original recovery that can't install CM. I can edit XML, but to cleanse my conscience i'll let this way).
After i'll install "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip" with TRWP and boot with this one.
Then i'll flash "cm-11-20140526-NIGHTLY-moto_msm8960.zip ".
But i'll have to do this at night(it's 12pm here), because i'm working today.
If that don't work i'll pull the log that you said here, but I come back to thank.
Same problem
I confess I was hopeful in that case you said to flash first the CM 10.2.
But again failed. I tried two ways:
In both I tried to install the Snapshot CM 10.2, then the CM 11.
There is no way that cell boot with "CM 10.2" in any case. That saty on boot animation for several time(i waited 30 minutos each).
In the first I downgraded to version 4.0.4 stock to see if the modem worked.
After that i flashed CM 10.2 that stood in boot animation, then CM 11 booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.0.4.7z)
On the second attempt, I used the default stock 4.1.2.
After CM 10.2 which was stucked on boot animation again, then CM 11 again booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.1.2.7z)
Strange thing happened on both CM 11 boot. When the system's load, it shows a message "The clock stopped". This is strange thing for me.
Can you wait for CM10.2 to boot...? There is a fsck process which sometimes takes quite a long time to boot.
Also, for your FC issue - you are clean flashing the ROM everytime? You are doing a factory reset everytime you flash a new ROM?
Edit - looking at your logs, I don't think the fsck is the issue... something is causing the CM10.2 boot to die over and over. Please try clean flashing...
I clean everything before.
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Skymidt said:
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Click to expand...
Click to collapse
Yes, factory reset == clean flash.
As for the long boot, I'm not sure the fsck is your issue - basically there is a process which runs a disk check, and sometimes this will make the boot take quite longer than usual. I can't say how long, I've never personally experienced the issue.
However, the fact that CM10.2 isn't booting is a little disturbing. I've heard some people report 45-60 mins... can you do me a favor, charge up the phone, and try to let it boot for at least 90 minutes?
If at the 90min mark it still hasn't booted, pull logs and post them.
Thanks.
The logs contain references to apps that are present only in stock firmware.
That means the CM boot is actually not happening in a clean environment (the data wipe/factory reset in TWRP hasn't worked as it should?).
Please try to use OpenRecovery 2.09 instead of TWRP (as OR is the recovery I personally use and watch for possible bugs) to wipe the device and to install CM11 - http://forum.xda-developers.com/showthread.php?t=2211579&page=10
When installing CM in recovery, you will probably also want to install the gapps package - http://wiki.cyanogenmod.org/w/Google_Apps
Btw., CM11 expects the baseband (modem) and other partitions the be at the 4.1.2 stock level. Experiments with 4.0.4 are useless.
Please post the logs from CM11 boot.
You will need to enable the logger under CM11 by
Code:
su
setprop persist.log.aplogd.enable 1
in Terminal app or ADB shell, it's not enabled on CM11 by default.
Links are broken
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Skymidt said:
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
I'm on an older version of TWRP, and it has never failed me... that's a shame really. I'll try to update and see what's what. In the meantime, flash OpenRecovery I linked above ^^.
Skymidt said:
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
Click to expand...
Click to collapse
TWRP 2.6.3.x should also work properly.
@arrrghhh, so you see it's not just me having the "wiping /data reboots the recovery" problem... I've already sold my PQ (might buy a new one in the future), but please do help let this problem be known to whoever's developing TWRP for us
Sent from Google Nexus 4 @ CM11
I can't believe it works
Unbelievable! :laugh:
This very simple solution worked for me.
My TRWP did not work right.
He said he had done successfully in cleaning the cache and manufactures, but did not.
I downloaded the link you guys sent me and it worked on the first try.
Not needed before installing CM 10.2. Already installed in the first CM 11, has worked with modem and everything. Now I can configure the GSM network my country and language of the country for my wife (PR-BR).
I want to thank the efforts of user @ AndyYan to respond, the attention given by the user @ Arrrghhh teaching me with patience, and the solution given by the user @ kabaldan. :victory:
You are awesome for this forum. Thanks for everything.
If you still want the log I get, but I think with everything working, you guys should already know the outcome.
Q&A for [ROM][5.1.1] Candy 5 - Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] Candy 5 - Skyrocket. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Anaya Boom said:
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Click to expand...
Click to collapse
This is a problem with most 5.1 roms. Mostly after using another audio app like hangouts phone,whatsapp phone,music players and video players. Driver is not released back too phone.Reboot is needed . On a good note, Paranoid Android 5.1.1 has just come out with an update and an audio patch that fixed mine. Hope this helps.
I don't get any signal
My phone after updating it to candy 5(5.1 Lollipop) I can't get any signal?
Please Help!
New to this
This is the best rom I have installed ever since fixing my bricked Skyrocket a couple weeks ago.
Latest Version 5/15:
After installing the latest update the data drops far less frequently... however it is still a good five times every twenty minutes or when I send two or more text messages. I tried rebooting, messing with wifi/airplane mode, removing excess APN's, and using Signal Boosters which are junk. Folders seem to be a bit different and overall rom is a bit more laggy compared to previous version. My recents menu did not work, holding the home button with no response, fixed by turning on OmniSwitch.
Installing SlipLP fixed the data, so I am confident you will figure it out for Candy! If only I digged the look of SlimLP.
Will report back next update, still learning how to Logcat... I will post if I figure it out tonight.
I am not getting any charging or heat issues like the poster above. I did not change to noop prior to writing this.
Found a PERMANENT signal fix!
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
requiredhq said:
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
Click to expand...
Click to collapse
Thanks, yes the UCMC1 radio or newer is needed for this. It is one of the last versions available for the Skyrocket. My Slim threads have this but I didn't see that mentioned here, so I have updated the OP.
Cheers!
Preinstalled App
Does this ROM has Apollo music player installed?
Hunter661 said:
Does this ROM has Apollo music player installed?
Click to expand...
Click to collapse
It has CM's Eleven music player. You can install whatever you want, Google Music, XenoAmp, etc.
GAPPS
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Candy 5 v2.5.3 onto skyrocket I727 as well as I727R)
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Twisterboy669 said:
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Click to expand...
Click to collapse
Michel177 said:
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Click to expand...
Click to collapse
Make sure you are using an up-to-date version of GApps. Recommended is Slim's Zero GApps (~60MB), a link to which you can find in the OP.
Google Cards
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Minor Question
How would you update the 2.53 version to this one?
Twisterboy669 said:
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Click to expand...
Click to collapse
When you flash the ROM, either the GApps package you flash needs Google Now (might be Google Search, not sure), or you need to install it from the Play Store separately. Voice input on the AOSP/Google keyboards may be missing as well until you do.
I partitioned my Skyrocket to have a 6GB Data partition so the tiny GApps is fine and I can install pretty much all I want for apps. It's quite nice.
Twisterboy669 said:
How would you update the 2.53 version to this one?
Click to expand...
Click to collapse
Wipe Dalvik and Cache in recovery
Make a nandroid backup
Flash the ROM
Flash either Slim Zero GApps or a very small base GApps package
Reboot
Have fun!
Flashing Potential Issue
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Twisterboy669 said:
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Click to expand...
Click to collapse
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
NoSpamDan said:
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
Click to expand...
Click to collapse
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Twisterboy669 said:
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Click to expand...
Click to collapse
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
NoSpamDan said:
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
Click to expand...
Click to collapse
Nvm, Sorry I forgot about the dirty flashing and it worked. Thank you
CM 13.0 has gone official for kltevzw. I may post a test build here or there to this thread, but otherwise get your builds from download.cyanogenmod.org
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: Why does my phone reboot when I try to make a call?
A: Your default dialer got changed for some reason. Maybe you installed a gapps package that replaced the dialer with Google Dialer or your default dialer somehow else got changed. Stop that: Settings -> Apps -> (Gear Icon) -> Default Apps -> Phone App -> (Select Phone).
Click to expand...
Click to collapse
Recovery:
I recommend the test1 recovery here by @jcadduono. This is the only TWRP I've found that handles adopted storage, MTP, and encrypted userdata.
The only caveat is that if you encrypt userdata then adopted storage doesn't work correctly. You won't be able to see /sdcard, so to flash things you either need to copy what you need to a safe place (/cache or /data/media/0 are both good options) or use an app like Flashify which does that for you.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. You must fully poweroff your phone before booting into download mode for any modem flashes to take.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
CyanogenMod recommends Opengapps. I use Opengapps mini, but feel free to use whatever you would like, even non-Opengapps. Make sure to use an ARM 6.0 version.
http://opengapps.org/
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
Unless I post a test in-thread, everything you need will come from Cyanogenmod.
CM-13.0 kltevzw Official nightlies
Click to expand...
Click to collapse
Does/Doesn't Work:
Same as the other klte* devices. I'd suggest tracking the below thread and participating in it.
http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-13-0-android-6-0-t3237502
And yes, bluetooth is glitchy. It's less glitchy when you turn off WIFI and ensure there aren't apps (WeatherBug is apparently a culprit) using/polling BT. When I get a free moment I may try to dig in and see if I can find something.
And yes, WIFI can sometimes drop when the screen is off. That's a Google AOSP thing.
Click to expand...
Click to collapse
Thanks:
Everyone on the CM team. This is 99% CM with just a couple tweaks to make it build, boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r46
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
Unless otherwise noted (test or other), builds are all 100% CM source for filename dates (UTC build dates) of 20160409 or later.
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Works perfectly! Thank you, thank you, thank you! I have been waiting for marshmallow for so long...
Question
Works for any verizon S5?
RichyValents said:
Works for any verizon S5?
Click to expand...
Click to collapse
FAQ #1 - any that has a dev bootloader, whether that is because you bought the device with one or whether you used the tools (provided you had a Samsung emmc) in the linked thread to flash one.
Sent from my SM-G900V using Tapatalk
so how do i go about installing this on my device that is now with developer mode
Download the ROM, make a backup in twrp, and install in twrp
Voice and SMS are not working after flashing. LTE data works however.....
I found that waiting, toggling airplane mode and data worked. Glitch free ROM once you get it dialed in.
Curious, can you both confirm to me what baseband version is being reported in Settings -> About Phone?
I wonder if they're set to the wrong network mode. I remember that being an issue auto selecting wrong on past cm roms.
talktosamson said:
Voice and SMS are not working after flashing. LTE data works however.....
Click to expand...
Click to collapse
In the bootloader thread you mention flashing a 122715 version of CM13. Where did you get this? If you got any version from anywhere other than my AFH dropbox (https://www.androidfilehost.com/?w=files&flid=52843) then things may not work correctly.
The symptoms make it sound like you have a standard klte version, not one of my kltevzw versions -- klte is a GSM ROM and it's init.cpp doesn't initialize CDMA properties like is done here.
If I am on PB1 already and rooted and unlocked to developer, should I bother with the PB1 firmware? I verified again just for good measure and I am on PB1.
thewebsiteisdown said:
If I am on PB1 already and rooted and unlocked to developer, should I bother with the PB1 firmware? I verified again just for good measure and I am on PB1.
Click to expand...
Click to collapse
If you confirmed that your baseband is reporting PB1 then there really is no need. Install a version of TWRP, at a minimum format /system, format /cache, wipe /data, and start installing the ROM and gapps.
A full factory reset would be even better then just wiping /data as far as starting fresh, but that erases /data/media (internal storage) and you may not want to jump that far.
How do I install the pb1?
coopmaster said:
How do I install the pb1?
Click to expand...
Click to collapse
If your about phone says you have PB1 baseband then you don't have to.
If you don't have that baseband, boot your phone to download mode and flash the .tar.md5 (containing just the modem and non-hlos) in the AP (or PDA if older version) slot of ODIN.
haggertk said:
If your about phone says you have PB1 baseband then you don't have to.
If you don't have that baseband, boot your phone to download mode and flash the .tar.md5 (containing just the modem and non-hlos) in the AP (or PDA if older version) slot of ODIN.
Click to expand...
Click to collapse
Thank you
Factory reset and noticed that it stated it was skipping /data/media and I was like meh, I installed anyway and it booted after optimizing the apps and everything worked and works. Awesome sauce! Thank you everyone!
haggertk said:
Curious, can you both confirm to me what baseband version is being reported in Settings -> About Phone?
Click to expand...
Click to collapse
Just replying back, I've got it nailed down now. Wasn't sure what the issue was, but it's all good now.
So one question how do i go about updating for each nightly build? do i just flash over it and everything should be fine or ?
Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17
Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP
Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!
e6833
thank you.
is it working for z5p Dual?
faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?
e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?
faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?
e6683能用吗，或者说e6653
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz
WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1
OP Updated with rev7 for both e6853 & e6883
enjoy
Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse
I have the Google Fi Android One X4 XT1900-1, and I made the mistake of trying out Lineage OS, which was great on my last couple phones but a bit underwhelming here. So I wanted to go back to stock. I tried following the threads here and here (just the return-to-stock part, not the Pie update), using the Linux shell script. And everything worked great! EXCEPT! Neither the WiFi nor the SIM card are working. I tried using the firmware from Motorola-Firmware-Team on Android File Host that were marked as Fi, both the most recent and a few versions back. And everything works except the modems.
Any suggestions? I don't really want to be stuck with this meh version of Lineage.
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flash the latest release (XT1900-1_PAYTON_FI_9.0_PPW29.69-39-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with your shell script, I guess you flashed stock oreo instead of pie and going back to oreo with pie modem is not a good idea
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Code:
#!/bin/sh
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot --set-active=a
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem_a oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot
Maybe there's something missing, or something I should take out?
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
trixter42 said:
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Maybe there's something missing, or something I should take out?
Click to expand...
Click to collapse
ElijahUSA said:
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
Click to expand...
Click to collapse
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
SyberHexen said:
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
Click to expand...
Click to collapse
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
trixter42 said:
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
Click to expand...
Click to collapse
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
SyberHexen said:
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
Click to expand...
Click to collapse
Still having trouble...
I did format everything in TWRP before flashing it. I've tried this a bunch of times, in a bunch of different variations, but I've made sure not to carry Lineage data over into the stock ROM.
I tried flashing the Pie Fi stock from lolinet and then flashing your Pie Fi firmware, but then it just bootlooped. I tried it with the retail firmware too, just in case it was some weird rebranded old stock thing, but the same thing happened. It was a good thing to try, though!
Ultimately, the stock ROM just isn't reading my IMEI for some reason, even though Lineage sees it just fine. I do have my IMEI, is there a way to enter it into the stock ROM manually? I've also been playing around with the official Moto tools over in Windows, but no luck there either.
I really appreciate all the suggestions though!
I'm hitting the exact same problem. I have a Google Fi variant, went to Lineage to try it out, tried to revert to stock, and wireless and radio are not working. I followed the guide at https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265, but accidentally skipped the step to install "Copy Partitions Zip". I've been trying to figure out what that file does, but haven't made much progress. I don't know if it's related or not to stock not working.
I lost all data/wifi/cell service after doing a clean flash of the April update. During the setup phase of the initial flash, I had no 4G, device was failing to acknowledge that I even had a SIM card inserted. Wifi was so intermittent that I couldn't enter my password to restore my Google account to the device. After this I tried out numerous stock flashes of the earlier Pie factory firmwares, LineageOS, HavocOS, none of them having any success..
After getting in a bootloop trying to restore the full backup I made right after unlocking my bootloader, I decided to again do a factory firmware flash of the April update and only restore the backups I made of the EFS and Persist partitions, at the initial boot, that didn't seem to work. I decided to go ahead and proceeded with my normal routine of flashing TWRP and the latest Magisk. Thought maybe a Magisk module could kickstart service. Booting after that, I finally had both Wifi and 4G LTE w/ voLTE on Total Wireless again.
Definitely a pain, especially the full backup I had made turning out to be a waste of time.
Just backup your EFS/Persist partitions. Lenovorola's gross mishandling of the EFS partition on nearly every recent device makes this step nearly vital before doing anything to the phone.
Is there any progress towards a solution on this? I experienced this for the first time while trying to re-flash stock April ROM.
Can the same EFS and Persist partitions interchangeable, as in can I use yours? I've been using the re-flash stock, accept OTAs, re-root/twrp method for months now and this is the first time this has happened. Its only bluetooth capable right now. lol
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
Neffy27 said:
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
Click to expand...
Click to collapse
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
NeoandGeo said:
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
Click to expand...
Click to collapse
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
JustDJ_From_Da_Swamp said:
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
Click to expand...
Click to collapse
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Comby_sk said:
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Click to expand...
Click to collapse
Awesome, I'll try it now. I greatly appreciate that
---------- Post added at 02:16 PM ---------- Previous post was at 01:39 PM ----------
Hey.. umm.. where can I find that new ROM?.. lol I know, it's a shame
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ?...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
JustDJ_From_Da_Swamp said:
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
Click to expand...
Click to collapse
Glad you got your problem sorted out. Honestly the best ROM for this device has always been Plain Stock w/ Magisk for root. Everything just seems to work without issues, all of the custom ROMs have the odd issue here and there that really prevents the device from being able to be run trouble free.
same problem on 1900-7 version