Develop Bugs

Flashing Rom add-ons?

I just rooted my phone yesterday and flashed warm z 2.2 rom and i want to flash a few of the add-ons. Do i just go into recovery and install from zip? Do i need to clear anything before i do this? this topic has been discussed before but im still unclear on exactly what i do. thanks.

You don't always need to wipe, but yeah, most stuff you flash in recovery. I usually wipe Cache and Dalvik before flashing anything, no matter what it is just to be safe. You shouldn't have to wipe anything other than that.
If you let me know the specific mods, I can double check for you.
Edit: Welcome! Excellent 1st ROM selection.

Yea im just trying to get the "recent apps in notification bar" and the "Hulu" add ons. thanks again for the help.

Yeah, you flash those, although I can't find the recent apps mod, I'm sure it is a flashable zip.
Also, someone the other day had trouble with the hulu zip. If you do, let me know and I can direct you to how to manually install Hulu.

ok im waiting on my battery to charge so i can flash the "recent apps in dropdown menu" add-on to my rom. Just to be 100% clear, i can just go into recovery and hit install from zip and choose the file? Is it best to clear the cache & dalvik cache before hand or does it matter? and if i do clear them will it erase any of my apps/files? Sorry, im really new to this stuff and im trying to learn as i go.

jphipps187 said:
ok im waiting on my battery to charge so i can flash the "recent apps in dropdown menu" add-on to my rom. Just to be 100% clear, i can just go into recovery and hit install from zip and choose the file? Is it best to clear the cache & dalvik cache before hand or does it matter? and if i do clear them will it erase any of my apps/files? Sorry, im really new to this stuff and im trying to learn as i go.
Click to expand...
Click to collapse
Its best to wipe the cache and dalvik before flashing anything in recovery. And it won't delete you apps, ect. Think of it like cleaning your internet cache on your browser. And yes, after the wipe, click install zip, and then choose zip. If you flash multiple things, wipe then flash again.
Ex: wipe cach/dalvik, flash thing one, go back, wipe cache/dalvik. flash thing 2, ect. Then reboot when done.

ok thanks a lot for the help.

jphipps187 said:
ok thanks a lot for the help.
Click to expand...
Click to collapse
No problem.

jphipps187 said:
I just rooted my phone yesterday and flashed warm z 2.2 rom and i want to flash a few of the add-ons. Do i just go into recovery and install from zip? Do i need to clear anything before i do this? this topic has been discussed before but im still unclear on exactly what i do. thanks.
Click to expand...
Click to collapse
I know I wasn't a part of this conversation but I used it to educate myself all the same, I would hit the thanks button if I could find it. Sorry, I'm new to this...

Are you using CWM to flash? I'm new to this as well and I don't think I'll be able to wipe cache without doing a full wipe with it.

chocolate8175 said:
I know I wasn't a part of this conversation but I used it to educate myself all the same, I would hit the thanks button if I could find it. Sorry, I'm new to this...
Click to expand...
Click to collapse
If your on a PC it's to the Left if your using the latest version of XDA. If your on the App tap the screen, you'll see the option.
victorvjr said:
Are you using CWM to flash? I'm new to this as well and I don't think I'll be able to wipe cache without doing a full wipe with it.
Click to expand...
Click to collapse
You can use CWM Recovery to Flash. Or there are several other Recoveries out there. Amon_Ra v2.3 , or SmelkusMod.

Want to flash add ons after flashing revolution os
I flashed my Samsung galaxy smj700f 2016 with revolution os and I wanted to flash bixby which is provided on a zip file of add one but it contains several other files which I don't want
How do I flash bixby only

[Q] Samsung Galaxy s3 i747 stuck in Cyanogenmod boot screen

Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!

dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.

ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...

Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.

shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?

dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.

ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?

dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).

ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?

dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)

ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?

If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.

audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it

dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)

Optimus G E975 (Kit Kat 4.4.2 ) Sling Rom 2.1 -- Install Instructions UPDATED

Just to be sure, before doing any of these steps BACKUP your current rom, connect your phone to a pc, open your phone`s internal storage, create a new folder and name it "0", without qoutes ( that`s a zero, not a letter 0 ), put all your files to that folder.
I am not responsible if anything goes wrong. You`re doing this at your own risk.
So, to get to the point, many users have reported a soft/hard brick. I recommend you trying this method, even thought the previous method worked for me every single time. That same method is quoted in the first comment, so if you want you can still try it. Install Jelly Bean E97510h from this link ( using KDZ updater )https://mega.co.nz/#!0gtWRABR!WSbEST...Y3UKMh3m4i7i14 Make sure you have an unlocked bootloader ( download app called "freegee" from the play store and unlock your bootloader using "mako" method ) and a recovery ( I recommend using CWM ):
After that install Paulicat, just to be safe https://drive.google.com/folderview?id=0B7AgxW28IQTwR2ZoZnpwNTZMekk&usp=sharing
( install it the same way as any other rom - wipe data/factory reset, wipe cache, dalvik cache, format system, install zip. wipe data/factory reset)
1. download Sling Rom 2.1
https://docs.google.com/file/d/0B6XkUfz_jC9aNXo1TXd6SF9WdlE/preview?pli=1
http://pan.baidu.com/s/1ntsiloX
https://storage.rcs-rds.ro/links/6bee2cd4-78b9-424a-9b0b-a2c492a63cdc
2. Download patch https://www.dropbox.com/s/7a3urpzvw48hrc0/Sling2.1_Patch_F180K_lgviet.com.zip
3. Super su http://download.chainfire.eu/420/SuperSU/UPDATE-SuperSU-v1.99.zip
4. Put all three files on your sd card
5. Enter recovery >> Wipe data/factory reset >> Wipe cache >> Wipe dalvik cache >> go to mounts and storage and click "format system"
6. Install Sling Rom, then Patch and finally Super Su
7. Go back, once more wipe data/factory reset >> wipe cache >> and wipe dalvik cache
Reboot your phone and enjoy kit kat.. you dont need to flash 10H modem because I`ve already included it in the patch, and you dont need to unlock your bootloader. I`ve tested this method and it works 100%, if you cant get it to work than you`re doing something wrong.
If u have installed kit kat rom and have a weak signal then go to recovery, wipe cache and dalvik cache, install 10h modem >>>>https://www.dropbox.com/s/rzpnlwu1lofpq2f/cwm-lgog_e975-europe-10h_modem.zip
Thanks @sunyakram for the rom links.

Brontok said:
Hi guys.. I just want to write down a few things about the install process.. As u may have already seen many users have installed kit kat and ended up with a soft brick..
All the credit for the kit kat rom goes to @hoangnova...
1.So, first thing`s first, I would recommend downloading this exact version of Jelly Bean (due to the fact that many users have reported loss of network after flashing kit kat over other jelly bean versions)
E97510H_00 (https://mega.co.nz/#!0gtWRABR!WSbESTvFJPJTVvOO6hmnPxIDhq0eNY3UKMh3m4i7i14) and installing it through KDZ Updater (http://forum.xda-developers.com/showthread.php?t=2010624)
2. After that install freegee (https://play.google.com/store/apps/details?id=edu.shell.freegee) and unlock your phone`s bootloader by tapping CWM or TWRP and choosing "mako unlock method" >> "classic" can also do the job, but in my opinion "mako" is the safer option
3. After installing and unlocking JB download kit kat rom from this link http://www.filedropper.com/vdt-v20superlitelgg, put it on your sd card aka internal storage
--- also download UPDATE-SuperSU-v1.99.zip (http://download.chainfire.eu/420/SuperSU/UPDATE-SuperSU-v1.99.zip) and put it on your internal storage
4. Once more go to freegee app, wait for it to download supported device list, click on the "settings" button on your phone and select "reboot recovery"
5. From the recovery make sure to wipe cache and dalvik cache.. DO NOT format anything else.. after that click on "install zip", "chose zip from sd card" > navigate to your rom file and install it.. DO NOT go anywhere.. once more click on install zip and make sure to install UPDATE-SuperSU-v1.99.zip
6. Now once again wipe cache and dalvik cache, but this time you also must do a factory reset.. click on "wipe data/factory reset". this will not delete your pictures, songs etc
7. You can click on "reboot system now". Upon reboot setup your phone, once again download freegee, install it, unlock your bootloader using the same option as before..
If you follow these steps carefully you will not have any problems. If u already have a "secure boot error" just download the KDZ file from the first post and flash it through KDZ updater. At the end of flashing phone will try to reboot, if it gets stuck at LG logo press and hold the power button until it shuts down completely.. now press and hold the volume down button + the power button.. a warning should pop up saying that you will lose all your data if you continue, press the power button to confirm.. you should be good to go.
If you have any other question feel free to ask here or send me a pm.
And lastly, if I`ve missed something do let me know
Sorry for bad english
Click to expand...
Click to collapse
Thanks alot @Brontok for these useful instructions i ve followed all these instructions and kit kat is working like a charm :good:.

I can't restore from kdz...I already restored from kdz a couple months ago cause I bricked my phone and now when i power on the phone the Google logo comes up..not LG and I can't kdz anymore:/ would it work coming from a stock based Rom such as savvyrom? Or epsilon v3?
Sent from my LG-E975 using XDA Premium 4 mobile app

Ahmed Xperia p said:
Thanks alot @Brontok for these useful instructions i ve followed all these instructions and kit kat is working like a charm :good:.
Click to expand...
Click to collapse
you`re most welcome ahmed.. I`m glad I could help you.

itsdacj said:
I can't restore from kdz...I already restored from kdz a couple months ago cause I bricked my phone and now when i power on the phone the Google logo comes up..not LG and I can't kdz anymore:/ would it work coming from a stock based Rom such as savvyrom? Or epsilon v3?
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have you tried turning off the phone and pressing volume up + the power button in order to enter recovery ?
I would recommend using the provided kdz file, simply because i dont know the base of those stock based roms. and mainly because stock doesnt have any removed files, unlike those two

Actually, my phone is very weird since I last kdzed...it's like a nexus 4, if I press both volume buttons and power, it comes up with a scroll choice screen
Sent from my LG-E975 using XDA Premium 4 mobile app

itsdacj said:
Actually, my phone is very weird since I last kdzed...it's like a nexus 4, if I press both volume buttons and power, it comes up with a scroll choice screen
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats good, simply scroll down until you see "reboot recovery"..its just two clicks down

Ya I know that and I do like it. I know how to enter download and restore from KDZ but it errors, well it did last time it tried, I really wanna kittykat yumminess
Sent from my iPad Mini (1st Gen) running iOS 7.1
HURRY UP JAILBREAK, STOCK IOS SUCKS

itsdacj said:
Ya I know that and I do like it. I know how to enter download and restore from KDZ but it errors, well it did last time it tried, I really wanna kittykat yumminess
Sent from my iPad Mini (1st Gen) running iOS 7.1
HURRY UP JAILBREAK, STOCK IOS SUCKS
Click to expand...
Click to collapse
check your pm

Okay
Sent from my iPad Mini (1st Gen) running iOS 7.1
HURRY UP JAILBREAK, STOCK IOS SUCKS

itsdacj said:
I can't restore from kdz...I already restored from kdz a couple months ago cause I bricked my phone and now when i power on the phone the Google logo comes up..not LG and I can't kdz anymore:/ would it work coming from a stock based Rom such as savvyrom? Or epsilon v3?
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i was on artmod and flashed this without flashing kdz . It should work in your case too

Ahmed Xperia p said:
i was on artmod and flashed this without flashing kdz . It should work in your case too
Click to expand...
Click to collapse
Just flashing the rom and wiping both the caches and then wiping data? If so..Imma cry xD
Sent from my iPad Mini (1st Gen) running iOS 7.1
HURRY UP JAILBREAK, STOCK IOS SUCKS

@Brontok if you want to intall this KK version over the first KK that was available what we should do?
Wipe data and dalvik only? Or a full wipe? Do we need to flash superuser too?
Thanks
Sent from my Sony Tablet S using Tapatalk

itsdacj said:
Just flashing the rom and wiping both the caches and then wiping data? If so..Imma cry xD
Sent from my iPad Mini (1st Gen) running iOS 7.1
HURRY UP JAILBREAK, STOCK IOS SUCKS
Click to expand...
Click to collapse
Well what i did
1. Factory reset
2.Wipe cache
3. Wipe dalvik
4. Wipe system/data and cache
5. Installed rom
6. Installed super su
7. Reboot
8. Freegee
9. Unlock Mako and cwm
Hurrray All fine

rimsilva said:
@Brontok if you want to intall this KK version over the first KK that was available what we should do?
Wipe data and dalvik only? Or a full wipe? Do we need to flash superuser too?
Thanks
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Go to recovery - wipe cache and dalvik cache - install rom - once more wipe cache , dalvik cache and do factory reset
and yes.. install super su once again..

Hey guys, can any of you tell me if you are able to charge your phone while off with kitkat?

furkandeger said:
Hey guys, can any of you tell me if you are able to charge your phone while off with kitkat?
Click to expand...
Click to collapse
Yes, I am: I`ll post screenshots in a few minutes.

Brontok said:
Yes, I am: I`ll post screenshots in a few minutes.
Click to expand...
Click to collapse
I am waiting for your screenshots. With Classic unlock there is no charging animation while the phone is off. With Mako, it shows the animation for a second then boots the phone up.

Not working for me, still stuck at LG Logo, it doesn't even show animation.. :/ I don't know what is wrong with my Optimus G, I have E975 btw

furkandeger said:
I am waiting for your screenshots. With Classic unlock there is no charging animation while the phone is off. With Mako, it shows the animation for a second then boots the phone up.
Click to expand...
Click to collapse
you`re right, i thought it didnt happen in my case, but it did.. it shows the battery icon but then it turns itself on..

TWRP installed; Do I need anything else to flash CM13?

Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)

IronRoo said:
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)
Click to expand...
Click to collapse
What I ment is before flashing it....Afterwards/during of couse Ill flash gapps

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^

syednawaz said:
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^
Click to expand...
Click to collapse
checked every file hash matches, did exactly as written, done all of above and it doesn't work
TWRP went on in less than 10 second does that sound normal ? and how do you know if its actually on there?

Nope. Installation take atleast 2 or 3 minutes.
and if its installed properly you would have seen different rom from the stock.
Here is what i use for s4 mini(i9192). Also used it on i9190 model as well.
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-aokp-rom-25-apr-2016-t3366314
and these steps mentioned in the website.
A. Initial install
1. Copy ROM and Gapps to your external SD Card or internal memory
2. Boot into recovery
3. Wipe
4. Install ROM and Gapps
5. Reboot
Its simple. Should have worked.
I hope you have installed your model rom.

A question the system format is required to install the rom ??

juanpabloml said:
A question the system format is required to install the rom ??
Click to expand...
Click to collapse
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.

syednawaz said:
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.
Click to expand...
Click to collapse
Ie that enough only to make WIPE FACTORY RESET AND WIPE DALVIK CACHE is not necessary to the FORMAT SYSTEM, DATA AND CACHE ??

sorry i do not understand.
to install a rom just do a factory reset. nothing else is necessary.
If you do not do factory reset, sometimes you will not be able to install a new version of rom(for example, from kitkat to lollipop).
if you do not do factory reset its called dirty flash.
for example
you are using custom rom cm13. and it has a new update released, you go in twrp recovery and install the updated rom without doing factory reset. this way you can keep all the application and data you have.
i hope i am making some sense. it is hard for me to explain.
well do some flashing and you will understand but always make a backup.

Custom ROMs crashing every couple of minutes...

Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!

SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0

madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible

SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?

J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?

SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.

J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?

SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)

JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...

JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.

SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.

ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!

SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.

J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!

ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!

Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.

ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!

Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.

ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes

Wow, that is poor. You aren't having this problem with stock OS?