Related
Mysterious AOKP 4.2.2 rom, Feb 22 build, faux 123 kernel, .33 radio, twrp. Took a pic, decided to take another one, hit the shutter, the phone froze, and then rebooted. downloaded some apps from the play store, rebooted on its own.
I haven't had any problems with stock 4.2.1 before, but then I wasn't really using the phone before and tinkering with it. Don't know if it was related to a wrong version of gapps or a dirty rom install or worst case scenario-hardware problems?
I followed the guide here. under TWRP there was an option to Format everything which i haven't tried.
http://www.android.gs/install-paranoid-android-4-2-1-custom-rom-for-google-nexus-4-e960/
gapps 4.2.2
http://donandroid.com/gapps
I also noticed it came with some apps called Android tweaker free and Battery Guru. Could that be cause of it? Compatiblity issues? Should I go back to stock 4.2.1 or try a different rom?
Hello,
On the last few days I've been facing a problem that I couldn't solve alone. As I understand, there are two different android 4.3 versions, JSS15J and JWR66V, if I understood right. I don't know what is the actual difference between them. I had the google factory image of 4.3 on my nexus 4 (that eventually I learned it's JWR66V) e flashed (through TWRP) the franco kernel (also JWR66V), but my data got almost completely lost. Then I flashed (through TWRP) the stock kernel (JWR66V), which I found here, and the problem continued. Than I flashed (also through TWRP) the AOSP kernel, which I found on that same thread, and the data problem was solved but the screen transition effect had little hickups.
After all that I didn't understand what happened and what I did wrong, could someone explain to me that diffence and what I should've done instead? It would be very apreciatted.
Thank you
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Q&A for [ROM][OFFICIAL] CyanogenMod Nightly Builds for jfltespr
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][OFFICIAL] CyanogenMod Nightly Builds for jfltespr. 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!
Struggling with CyanogenMod 11
I installed last night with Philz recovery (most recent version), factory reset, wiped cache and dalvic cache first. Things appeared to be running smoothly initially but I realize I don't have any sound (DSP manager crashes when I open it or when I open Apollo). I'm not able to answer or make phone calls. I'm pretty new at this - do I need to update my modem? I know Knox got installed (0x1) and the baseband version says mk2. Is there a ROM that would work better for my phone?Can I install rom that say NAE and NG2? I'm just looking for something that's stable and has great battery life. Or is there something I'm doing wrong with Cyanogenmod?
Here's info in the about phone page:
SPH-L720
11-20141008-SNAPSHOT-M11-jflte
4.4.4
L720VPUEMK2 (baseband)
Kernel 3.4.104-cyanogenmod-gc55a5d6 etc
CPU ARMv7
Memory 1809 MB
Please help.
A second thorough wipe may be worthwhile. Otherwise download a fresh cm copy as the other may have gotten corrupted. Reload and reflash.
garbage914 said:
I installed last night with Philz recovery (most recent version), factory reset, wiped cache and dalvic cache first. Things appeared to be running smoothly initially but I realize I don't have any sound (DSP manager crashes when I open it or when I open Apollo). I'm not able to answer or make phone calls. I'm pretty new at this - do I need to update my modem? I know Knox got installed (0x1) and the baseband version says mk2. Is there a ROM that would work better for my phone?Can I install rom that say NAE and NG2? I'm just looking for something that's stable and has great battery life. Or is there something I'm doing wrong with Cyanogenmod?
Here's info in the about phone page:
SPH-L720
11-20141008-SNAPSHOT-M11-jflte
4.4.4
L720VPUEMK2 (baseband)
Kernel 3.4.104-cyanogenmod-gc55a5d6 etc
CPU ARMv7
Memory 1809 MB
Please help.
Click to expand...
Click to collapse
Hey garbage914, granted it's been several days, just wondering if you got your ROM issues sorted? I don't know much but glad to help in any way possible.
Cant connect to camera
Sent from my SPH-L720 using XDA Premium 4 mobile app
passlogin said:
Cant connect to camera
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got the same thing when I was using the front facing camera today. Took one picture then FC. Had to reboot to connect again.
Probably the fastest rom iv tried. But WiFi signal comes and go. Some applications close by then self. And the voice recording is terrible.
SIM problems
Is there any way to use CM12 without having a SIM card inserted because it won't allow the phone to connect to any network even though I've ben using my phone on Boost Mobile for almost a year now.
I'm running TWRP and the 2/8 nightly, I've been unable to access my developer options since the flash, even with factory reset before and after flash. Also having issues with the camera, seems to only want to take a few photos before it just stops capturing and force closing, leading to "unable to connect to camera". Any thoughts on the dev options issue?
babyshrimps said:
I'm running TWRP and the 2/8 nightly, I've been unable to access my developer options since the flash, even with factory reset before and after flash. Also having issues with the camera, seems to only want to take a few photos before it just stops capturing and force closing, leading to "unable to connect to camera". Any thoughts on the dev options issue?
Click to expand...
Click to collapse
same thing here I got the rom today and it was working perfectly but then I tried switching to record video and it froze and closed. Now when I try to open it, it say "can't connect to camera" any solution?
Camera Won't Work
Everything was running smooth but then I decided to record a video so after taking a few pictures I switched to video record. It frozee for a second and then closed the program. I clicled on camera again and a message popped up saying:
"Camera error
Can't connect to the camera."
I have CyanogenMod Version:
12-20150226-NIGHTLY-jfltespr
I tried closing disabling the camera app but no luck.
Move from CM12 nightly to Lollipop Stock Rooted
Greetings!
I've been running the Cyanogenmod 12 nightly build 12-20150224-NIGHTLY-jfltespr on my S4 (baseband L720PUFNG2) with ClockworkMod 6.0.4.7 installed. I've been experiencing some battery issues and miss features included in the stock Samsung ROMs, such as a working IR blaster and multiwindow support, and would like to move from CM12 to a stock AND ROOTED configuration. I have a few questions:
1) Where do I obtain the *correct* ROM to flash? I'd like Samsung's stock rooted Lollipop, *if possible*.
2) Do I run TriangleAway FIRST, and then flash, or flash, and THEN run TriangleAway?
3) After I flash the stock ROM, am I safe to recover user apps AND system data with Titanium Backup, or should I simply start fresh, being spring and all?
4) What about KNOX? Will it complain/cause issues/take off and nuke the entire site from orbit?
BTW, I *have* searched these forums, but there's almost an ocean of data to sift through even so, and most of my results date from 2013/2014. I don't want to get this wrong, as this is my only phone, and I've already softbricked for a day (no PIT found!), and want to avoid that happening again if possible.
I'll keep hunting for what I want on my own, but any help you geniuses here can provide would be.... well, helpful.
Thanks!
Did you make a nandroid backup of your stock ROM before you went down the custom ROM route?
meldryn said:
Did you make a nandroid backup of your stock ROM before you went down the custom ROM route?
Click to expand...
Click to collapse
No, and that answer probably means, apart from "do a nandroid backup next time, idiot", that I have to do a full wipe and can't restore my user data. I'm actually fine with that, as I don't really have any information on my phone that isn't already attached to my Google account or otherwise stored in the cloud.
What are the consequences beyond losing my data because I didn't do a Nandroid backup, if any?
And where do I get the stock ROM, etc.?
I see a bit of a green tint after latest updates (03/08 and 03/11).
I see a bit of a green tint after latest updates (03/08 and 03/11). This is not hardware issue. Is there anyone who noticed same problem?
occulus said:
No, and that answer probably means, apart from "do a nandroid backup next time, idiot", that I have to do a full wipe and can't restore my user data. I'm actually fine with that, as I don't really have any information on my phone that isn't already attached to my Google account or otherwise stored in the cloud.
What are the consequences beyond losing my data because I didn't do a Nandroid backup, if any?
And where do I get the stock ROM, etc.?
Click to expand...
Click to collapse
well not making a nandroid could be bad because you could have a bad flash and soft brick and all u have left is download and/or recovery mode and u can always go back to having a functioning phone with your backup. And plus running cm12 u could restore your back up and update your prl and profile then restore your cm12 or do the same for a gps lock. Always make a back up man. U can get the stock touch wiz by either searching the forum for it which I'm sure it's here or u can go to sammobile type in sph-l720 and download the current stock tar file then re root and make a back up of stock before u even delete any bloat that way u will always have a completely stock back up.
http://howto.highonandroid.com/samsung-tutorials/how-to-extract-stock-recovery-from-samsung-firmware
Sent from my SPH-L720 using XDA Free mobile app
Installed the 3/28 nightly last night and really digging it. I don't use it as a phone so I won't be able to test that aspect. About the only bug I've come across is that Falcon Pro 3 Twitter client can't play Youtube videos inside the app. Works on stock Lollipop. Not a biggie but thought you guys might want to know about it. NFC seemed to work great when I used it during initial setup. Camera pics and video looks great. Will try testing Bluetooth with file transfers to Nexus 7 (2013) tablet later. I'll try to report any other issues I encounter in this thread. Thanks for the really excellent work.
Edit: Well, I just played a YouTube video within Falcon Pro 3 (from The Verge Twitter account) and it played flawlessly. So that last attempt was either a borked link or who knows?
I am having the same issue with 13., moving back to 12 trying a new download.
junior92x said:
same thing here I got the rom today and it was working perfectly but then I tried switching to record video and it froze and closed. Now when I try to open it, it say "can't connect to camera" any solution?
Click to expand...
Click to collapse
Haven't found one other than buying a new phone haha! Still using the S4 but can't figure out the problems
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.