DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
CyanogenMod 13.0 : Download
Changelog : Changelog
Open GApps : Download ( arm, 6.0, nano )
TWRP : Download
CM13 Nightlies, ROM for the Sprint Galaxy S5
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly, now moved to 14.1
UPDATE 6/14: Looks like there's an issue that 5ghz network doesn't work on higher bands, but it works on 36-48 and bluetooth. Hopefully it will be fixed soon.
UPDATE 6/23: There's a fix attempt on boot image. Link. Thanks to @haggertk
UPDATE 6/27: Looks like Bluetooth and Wifi issue have been fixed since 6/25 nightly.
Thanks to @haggertk
Created 2016-05-12
Last Updated 2016-11-29
Reserved
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
alexclang said:
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
Click to expand...
Click to collapse
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
e-j said:
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
Click to expand...
Click to collapse
Excellent!! I'll just install the latest nightly for CM13 just like I was going for 12.1 and hopefully things will go smoothly!
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
UPDATE/PSA: USE THE NANO GAPPS AS STATED IN THE OP. NANOGAPPS INFINITY OPENS THE DOOR.
e-j said:
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
Click to expand...
Click to collapse
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
alexclang said:
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
Click to expand...
Click to collapse
Got it working after I realized the OP specifically mentioned the "nano" GApps variant; booted fine after a clean install of CM13 & the nano zip.
Issues w. CM13 flash
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
lentm said:
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
Click to expand...
Click to collapse
Yeah that was exactly the issue. Reflashed 5.0 then made the jump and it worked perfectly. So much wasted time...
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
e-j said:
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
Click to expand...
Click to collapse
Yeah reflashing lollipop then installing cm13 did the trick.
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
has anyone got themes to work ine keeps crashing
manolze said:
has anyone got themes to work ine keeps crashing
Click to expand...
Click to collapse
Mine works fine with Puzzled UI - CM Theme from Play Store on 5/20 build.
I have no working theme chooser on this releaese
xenokc said:
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
Click to expand...
Click to collapse
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
xpm69420 said:
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
Click to expand...
Click to collapse
Theme chooser works great for me, not having any issues with it. I am having an issue with the time being or of sync when set to automatic... How'd you fix it? Also, what's wrong with the dialer... can't say I'm having any issues there either.
unclejuju said:
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
I little late here, but CM 13.0 did NOT fix the S5 bluetooth issues. Still have the skipping and studdering.
Related
Q&A for [ROM][CM12.0] Official CM12.0 for E970
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][CM12.0] Official CM12.0 for E970. 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!
wkobaint said:
Could this versions working on e975?
Click to expand...
Click to collapse
Nope, but if you choose you model from device list below, it will works.
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Volstagg.The.Valiant said:
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Click to expand...
Click to collapse
Did you flash 5.0 gapps?
dandrumheller said:
Did you flash 5.0 gapps?
Click to expand...
Click to collapse
Nope. Could find only old gapps
terribly sorry about the brain fart. whole problem arose because i didnt flash the correct gapps . got the gapps from xda and now its working well. but i am getting a pop up saying that google play services have not been installed on your computer etc...
will this problem go away if i just install the google play services apk?
edit : after flashing the proper gapps, an update from the play store solved everything. Now running smoothly.
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Volstagg.The.Valiant said:
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Click to expand...
Click to collapse
Has the app been updated to support LP? At times in the past, access for 3rd party apps to stuff like data connection, which requires root, sometimes changes functionality with version upgrades. Don't know if that's the case in this circumstance, but it's something to look into.
Performance drop
Flashed this rom with fulll wipe. Works well, but sometimes performance *drops* happens. It becomes VERY slow, like CPU speed drops down to 128mhz. I had the same problem on cm 11.
Who knows how to fix it?
Looking great and functions great but I am getting terrible battery life due to "miscellaneous" or "Cellular Standby" according to battery stats.
E970
1/15/2015 nightly (problem persists from previous nightly)
Same problem on stock and Solid_GEEB Kernel
PA 5.0 GAPPS
Lucky to get 12 hours of battery under normal use. Any suggestions?
Thanks,
-Nick
Any ideas how to fix my issue with the BT mac address being changed to "00:00:00:00:5A:AD"? I had the wrong address on CM11 also but it was a different incorrect address and I was able to fix it. I've posted details in my thread for fixing the issue on CM11. http://forum.xda-developers.com/showthread.php?t=2759056#post58131969<br/>
Video call issue
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
azatheadfi said:
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
Click to expand...
Click to collapse
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
CM Updates
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
alliance1975 said:
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
Click to expand...
Click to collapse
The 1/27 update was detected and installed. I do not know what if anything i did to make it work.
Shelnutt2 said:
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for late answer. I was too busy to post logcats earlier. I hope issues will get fixed.
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
thunder2132 said:
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
Click to expand...
Click to collapse
I'm using TWRP 2.8.4.0 recovery. I initially installed the CM12 unofficial rom along with this gapps:
https://s.basketbuild.com/gapps
and had no problem. I switched to official CM12 when announced by Shelnutt2 and have made no changes to gapps. Perhaps give that gapps a try.
Audio calls problem
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
arun.rama said:
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
Click to expand...
Click to collapse
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
azatheadfi said:
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
Click to expand...
Click to collapse
Hey, I just tried the steps you had mentioned and it worked like a gem. Thanks a lot for your solution. I really appreciate your help. Have a great weekend.
Arun
What's up people? Official LineageOS 14.1 nightly build has finally been released for the Verizon LG G3!
Downloads needed:
1) Download the ROM from download.lineageos.org/vs985
2) SU addon (optional) download.lineageos.org/extras. Download the ARM variant.
3) Gapps (optional): opengapps.org choose ARM, 7.1.1 and Stock or Super or Nano or whichever you want.
4) xdabbeb's 35B bootstack
Instructions for flashing:
1) Make backup of your current ROM(just in case).
2) Wipe System, Data, Dalvik and Cache.
3) Flash xdabbeb's 35B bootstack (if you haven't done it already)
4) Flash LineageOS, SU add-on (if you want root access) and Gapps (if you want Google apps)
5) Reboot.
Have a great day!
I am not the original creator nor contributor of this ROM. This is an all original work of LineageOS. Thanks to Google and LineageOS
required 35b bootstack
ngato35 said:
required 35b bootstack
Click to expand...
Click to collapse
Thanks
Anyone installed this yet and tried audiofx?
yes i'm using this rom.. nice rom audiofx working
ngato35 said:
yes i'm using this rom.. nice rom audiofx working
Click to expand...
Click to collapse
Which one of the firmwares did you use? Theres a 3.11 snd a 2.something where the bootstack files are. I tried just flashing the bootstack in TWRP but the ROM wouldn't flash then.
I have a nandroid so reverted am waiting to try again
35b bootstack.. flash 35b flash rom flash add on su flash gapps and flash agein 35b that all
Okk, I didn't know that I had to flash the bootstack twice. I was a bit confused, I've done bootstraps, FXZs, now tots and bootstack. All in the name of learning
ngato35 said:
35b bootstack.. flash 35b flash rom flash add on su flash gapps and flash agein 35b that all
Click to expand...
Click to collapse
Thanks, this worked like a charm. It all flashed beautifully except for the Gapps. I tried the one you choose your apps during install, I've never used that so I probably missed something. It flashed in seconds, well didn't flash. I''ll try again and if that doesn't work, I'll just download micro or another small one.
The rom runs great. I havent' noticed any issues yet. I'll play w' it for a bit longer, then probably shelve it. The challenge is over. I was half hoping/dreading I'd at least softbrick it. I learn more about devices that way than any other method.
as an off topic, I have a new Sammy Galaxy Sky SM-S320VL (Net 10 edition), no one's been able to root one yet to my knowledge. Anyone care to take up the challenge with me?
It's a nice rom, smooth and all that. Unfortunately, it only gives root through ADB. I've flashed the SuperSu twice, then went over to the rom site to learn that.
Gapps are a hassle too to install
I really like this rom but dont' want to have to mess around with sideloading, etc. I',,ll come back to it when, and if, it gets updated
equitube said:
It's a nice rom, smooth and all that. Unfortunately, it only gives root through ADB. I've flashed the SuperSu twice, then went over to the rom site to learn that.
Gapps are a hassle too to install
I really like this rom but dont' want to have to mess around with sideloading, etc. I',,ll come back to it when, and if, it gets updated
Click to expand...
Click to collapse
I'm also using the same rom on my Verizon lg g3 but I don't have any root issues. Use the su add-on which I provided in the link. Then go to developer options→root access→apps and adb.
Also, I installed Gapps without any issues (build- 08032017, variant - super). Wipe everything (excluding internal storage and sd card) and again wipe cache and dalvik after installing rom and gapps.
equitube said:
Which one of the firmwares did you use? Theres a 3.11 snd a 2.something where the bootstack files are. I tried just flashing the bootstack in TWRP but the ROM wouldn't flash then.
I have a nandroid so reverted am waiting to try again
Click to expand...
Click to collapse
I'm using the 35b bootstack and audiofx is working good, but the animation when you try to change between speakers in the app is kinda laggy. It seems to be an issue in every nougat rom. Also, a message pops up in the behind showing "com.qualcomm.shutdownlistener has stopped", but it doesn't affect the shutting down. This also seems a problem in nougat roms. Other than that, everything is working. Network, 4g, Bluetooth, etc is working.
farhanshaikh671 said:
I'm using the 35b bootstack and audiofx is working good, but the animation when you try to change between speakers in the app is kinda laggy. It seems to be an issue in every nougat rom. Also, a message pops up in the behind showing "com.qualcomm.shutdownlistener has stopped", but it doesn't affect the shutting down. This also seems a problem in nougat roms. Other than that, everything is working. Network, 4g, Bluetooth, etc is working.
Click to expand...
Click to collapse
I got the ROM installed fine. But it doesn't have root (except through ADB) so I am now running Dirty Unicorns 10.6. Android 6.01, I'll try the Linage again when they get a few more bugs worked out. Or I may write my own for this, not sure yet
equitube said:
I got the ROM installed fine. But it doesn't have root (except through ADB) so I am now running Dirty Unicorns 10.6. Android 6.01, I'll try the Linage again when they get a few more bugs worked out. Or I may write my own for this, not sure yet
Click to expand...
Click to collapse
use the su add-on which I provided in the link. Then enable it in developer options in settings. That's what I did.
farhanshaikh671 said:
use the su add-on which I provided in the link. Then enable it in developer options in settings. That's what I did.
Click to expand...
Click to collapse
that's what I Flashed unfortunately, developer options weren't able to be turned on. There's a workaround published either here or on the RR site.
Steven Peterson (Equitube)
"Aspiring Android Developer
"Recovering Windows Expert"
equitube said:
that's what I Flashed unfortunately, developer options weren't able to be turned on. There's a workaround published either here or on the RR site.
Steven Peterson (Equitube)
"Aspiring Android Developer
"Recovering Windows Expert"
Click to expand...
Click to collapse
Try factory resetting and flashing the add-on *with* the rom
farhanshaikh671 said:
Try factory resetting and flashing the add-on *with* the rom
Click to expand...
Click to collapse
Do you mean flashing both in the same zip queue? I had flashed the rom successfully, then immediately flashed the superSU add on. It also indicated success, but didn't seem to install superSu. I'll go back and try your suggestion.
equitube said:
Do you mean flashing both in the same zip queue? I had flashed the rom successfully, then immediately flashed the superSU add on. It also indicated success, but didn't seem to install superSu. I'll go back and try your suggestion.
Click to expand...
Click to collapse
Sure
farhanshaikh671 said:
Try factory resetting and flashing the add-on *with* the rom
Click to expand...
Click to collapse
That worked great, thanks. Rolling with this ROM now with development options enabled. (I do have to say though that I was using a dirty Unicorns ROM (10.2) and I may go back to it. This ROM doesn't have near the customizations. It's good though
equitube said:
That worked great, thanks. Rolling with this ROM now with development options enabled. (I do have to say though that I was using a dirty Unicorns ROM (10.2) and I may go back to it. This ROM doesn't have near the customizations. It's good though
Click to expand...
Click to collapse
Glad it worked And yeah, since it is an initial build, many features are missing. I hope that they will add them in future updates.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.