I installed one latest firmwares to try it, and hate it. Anyway I went to install CM13 even blisspop and it won't install and gives error 7. I can odin stock rom but can't flash any asop is my sm-g900T dead lol.
enzodad said:
I installed one latest firmwares to try it, and hate it. Anyway I went to install CM13 even blisspop and it won't install and gives error 7. I can odin stock rom but can't flash any asop is my sm-g900T dead lol.
Click to expand...
Click to collapse
Are you doing a full wipe before installing any AOSP ROM? I.e. in TWRP, there is an option for Advanced Wipe. Before your first time installing any AOSP ROM, coming from stock ROM, you must wipe system, data, cache, and dalvik. Also when you say latest firmware, you mean FOL1, right? Because that's the latest. Finally, are you using the right ROM file. This phone's development codename is klte, as opposed to kltespr, kltedv, kltevzw, klteusc, etc.
thisisapoorusernamechoice said:
Are you doing a full wipe before installing any AOSP ROM? I.e. in TWRP, there is an option for Advanced Wipe. Before your first time installing any AOSP ROM, coming from stock ROM, you must wipe system, data, cache, and dalvik. Also when you say latest firmware, you mean FOL1, right? Because that's the latest. Finally, are you using the right ROM file. This phone's development codename is klte, as opposed to kltespr, kltedv, kltevzw, klteusc, etc.
Click to expand...
Click to collapse
Yes I've install hundreds of roms on this phone, I know it's klte I do a full advanced wipe in twrp
I believe it was FOL1- I've never had a problem before. Figured maybe new firmware made impossible flash asop or something.
enzodad said:
Yes I've install hundreds of roms on this phone, I know it's klte I do a full advanced wipe in twrp
I believe it was FOL1- I've never had a problem before. Figured maybe new firmware made impossible flash asop or something.
Click to expand...
Click to collapse
I googled it and error 7 is a problem with the assert. So double check you have the correct ROM file, then edit the first line or two out of the updater-script (located in META-INF/com/google/android/)
Related
Just curious about whether I am wiping and flashing correctly.
I currently have TWRP 2.2.2.0 installed.
I am presently on the Viper sense based rom for the HOX+. I assume I must be wiping and flashing correctly as the rom works!!
Wipe cache, wipe davlik cache, factory reset and system? Then flash rom?
Doing this, does it completely remove the previous rom, audio drivers etc so that I have a clean slate so to speak for flashing the new rom?
That's what I'm after, wiping the previous rom completely, drivers, everything so that I can flash an aosp based rom.
Thanks.
First off, I would advice you to flash the latest version of TWRP before doing anything. Now, having said that, yeah, essentially press all buttons in the wipe Menu (I frankly don't know if the "Format" button would be overkill). However, be aware that in doing so, you're going to wipe all the data in the partition, including any zip files you may want to flash afterwards. If you end up doing this, you're going to need to sideload the rom into your phone in order for you to be able to install it.
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
If he is wanting to use the Viper rom it is best to flash the version that is on the Viper thread. This has some minor changes in it to allow the install of OTA's and zip files from the hub.
If he uses the latest version it may cause issues trying to install OTA's.
Lloir said:
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Exactly, so long as he doesn't touch the data partition he should loose nothing. I did recommend the whole "Nuke it" approach because of the whole "Clean Slate" thing the OP wanted though...
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
Yeah, although it's not necessary most of the times, at least that's what I personally do when I want a 100% clean install (Short of re-locking the bootloader and running a RUU of course).
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
While installing Viper you can choose to wipe the phone for a clean installation. So basically it's not necessary to do anything than install recovery for Viper and then install Viper ROM and choose the correct option in AROMA installer...
I'm currently running CM10.1 nightlies, I quite fancy trying out a stock based ROM, can I just flash as usual using a ROM manager from the phone being turned on or will i need to flash back to stock first?
Thanks
batjon said:
I'm currently running CM10.1 nightlies, I quite fancy trying out a stock based ROM, can I just flash as usual using a ROM manager from the phone being turned on or will i need to flash back to stock first?
Thanks
Click to expand...
Click to collapse
the best stock based rom i have come across is this - http://forum.xda-developers.com/showthread.php?t=1998701&highlight=phenom
You don't need to flash a stock rom with Odin and your PC, just use CWM. Just follow the instructions on the page, i've pasted them below for your convenience.
***COMING FROM A DIFFERENT ROM A FULL WIPE IS RECOMMENDED***
***FULL WIPE***
MAKE A NANDROID BACKUP
Wipe data/factory reset in recovery
Wipe Cache & Davilk Cache
Flash Rom in CWM
Reboot
[EDIT] "can I just flash as usual using a ROM manager from the phone being turned on" - yes.
squ89r97 said:
the best stock based rom i have come across is this - http://forum.xda-developers.com/showthread.php?t=1998701&highlight=phenom
You don't need to flash a stock rom with Odin and your PC, just use CWM. Just follow the instructions on the page, i've pasted them below for your convenience.
***COMING FROM A DIFFERENT ROM A FULL WIPE IS RECOMMENDED***
***FULL WIPE***
MAKE A NANDROID BACKUP
Wipe data/factory reset in recovery
Wipe Cache & Davilk Cache
Flash Rom in CWM
Reboot
[EDIT] "can I just flash as usual using a ROM manager from the phone being turned on" - yes.
Click to expand...
Click to collapse
Thanks man, appreciate it. Thanks for not saying "this has been asked before, moderator close this NOW!"
safe
batjon said:
Thanks man, appreciate it. Thanks for not saying "this has been asked before, moderator close this NOW!"
safe
Click to expand...
Click to collapse
You're welcome, you could hit the thanks button seeing as I was so kind
batjon said:
I'm currently running CM10.1 nightlies, I quite fancy trying out a stock based ROM, can I just flash as usual using a ROM manager from the phone being turned on or will i need to flash back to stock first?
Thanks
Click to expand...
Click to collapse
You have to do a megawipe if coming back from 4.2 roms, as these roms change the folder structure of internal storage. Dont forget to backup everything in your internal storage or you will lose them.
Many others have faced problems later by not doing a megawipe.
lefttobleed - pardon my ignorance, can this be done within the ROM manager or is it worth going into recovery to do this? I don't have my phone for a couple of days so I can't currently check settings.
Thanks
batjon said:
lefttobleed - pardon my ignorance, can this be done within the ROM manager or is it worth going into recovery to do this? I don't have my phone for a couple of days so I can't currently check settings.
Thanks
Click to expand...
Click to collapse
you have to go into recovery and flash the megawipe aroma file. sorry i dont remember the link for the file. Search for it.
Please note that i am not familiar with rom manager so i dont know whether this can be done with rom manager. I always flash through recovery.
Edit: Please dont try this through rom manager... i feel something might go really wrong.
Hi!
I need some help with understanding of flashing custom roms e.t.c.
If I have 4.3 ( latest official update ), is it possible that I upgrade to CM11 4.4? Or I just can flash roms wich are based on 4.3?
Dont get it!
Thank you for responding!
If you have custom recovery installed, then you can install Compatible ROMs for your device (such as CM 4.4). If you are running stock or another ROM, then by entering custom recovery and making Nandroid backup first, you can install the ROM. To install, read the post for ROM you want to make sure compatible/whats needed (like GApps, etc), download, backup current ROM if isssue happens (to save yourself), WIPE data/factory reset, WIPE cache/dalvik cache, install ROM/etc as directed via the ROM post page. As long as you can meet these, you can flash what you'd like.
RevelationOmega said:
If you have custom recovery installed, then you can install Compatible ROMs for your device (such as CM 4.4). If you are running stock or another ROM, then by entering custom recovery and making Nandroid backup first, you can install the ROM. To install, read the post for ROM you want to make sure compatible/whats needed (like GApps, etc), download, backup current ROM if isssue happens (to save yourself), WIPE data/factory reset, WIPE cache/dalvik cache, install ROM/etc as directed via the ROM post page. As long as you can meet these, you can flash what you'd like.
Click to expand...
Click to collapse
I have cwm on my phone and made a backup yesterday so i think im ready to roll!
Thank you!!!
damarsdun said:
I have cwm on my phone and made a backup yesterday so i think im ready to roll!
Thank you!!!
Click to expand...
Click to collapse
Welcome, make sure you do your research though on flashing and the ROM in case there are issues with the ROM specifically (ex. Bluetooth not working, or something). Any one thing missing (didn't flash GApps, ROM problem, etc) can cause issue. If no issues or you can live around them if they exist, then good luck.
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
nht48823 said:
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
Click to expand...
Click to collapse
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
jt1998 said:
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
Click to expand...
Click to collapse
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Dorsant said:
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Click to expand...
Click to collapse
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
jt1998 said:
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Dorsant said:
And what is clean vs dirty flash?
Click to expand...
Click to collapse
Make a backup, then wipe system, data, cache, and dalvik before flashing the ROM. It helps prevent bugs
Dorsant said:
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Click to expand...
Click to collapse
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
jt1998 said:
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
Click to expand...
Click to collapse
Perfect! Great explanation, worked perfectly!
Dorsant said:
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Click to expand...
Click to collapse
there's little reason to use an old & insecure version at this point, i've ONLY used a few nightlies, the bugs were usually minor & you can get the fixes pretty much as soon as they come out rather than waiting months
deep sleep battery use & the camera app are greatly improved in CM13
http://www.cmxlog.com/13/klte/ changelogs