Related
I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.
Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?
I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse
harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?
You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?
tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!
Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.
I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.
Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.
I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app
Hello, I have had a touchpad for some time and but CM9 and CWM on it some time ago, but it started having some issues recently. So I figured I should try and reinstall a newer version of CM and start from scratch.
I went to this post http://forum.xda-developers.com/showthread.php?t=2026692 and downloaded both the skz+tenderloin-1.10.zip and the gapps zip.
I then placed those into the Download folder on the touchpad.
This is where things took a turn. I rebooted to get into CWM, upon selecting it from the boot menu it kept restarting back to the boot menu. After a few tries it got into CWM. I then wiped the data and did a factory reset, wiped the cache, and then wiped the dalvik like the post said to do. I then went to install zip from sdcard. Found the skz+tenderloin zip and chose to install that. CWM says it starts to install but then before the progress bar fills up at all...it resets back to the bootloader.
At this point I am at a loss with what to do and I would really appreciate any help I can get with this.
UPDATE: I figured starting from scratch would be the best bet, so I have uninstalled CM9 and CWM using ACMEUninstall. Now I am wondering if it is worth using CM10 as my default Android or should I stick with the best CM9.
Either way, if I should use CM9 or 10 can someone either help me or point me in the right direction for the best tutorial on doing this properly?
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
sstar said:
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
Click to expand...
Click to collapse
The issue I am encountering is there is a ton of info out there, some outdated some not. I restored back to stock webOS with nothing else. I have ACMEInstaller 3 in the Palm directory, so I am ready to install the most stable/best CM9 currently out there, I just don't know which tutorial is the best one to follow. Could you perhaps just link me to one you recommend?
http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-232013/
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I installed CM9 based on the link above with the AIO package. It worked flawlessly, hopefully my freezing/restarting issues happen less often now. Thanks to all who offered help.
Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I can tell you that I use my Schizoid as my daily driver, and it's not a preview.
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Cannonball3804 said:
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Click to expand...
Click to collapse
1. I don't know anything about GooManager or if it is compatible with the D4 but safestrap is a really great piece of software that is easy to use. I highly recommend it. Just download and install the app on your phone. Then open the app and install recovery. From there, when you reboot, you will be given the option to boot into safestrap recovery where you can install your ROMs.
2. You will not need to re-root your phone.
3. I am running CM10.2 (Android 4.3) nightlies and have found them to be very stable. I've also heard the latest stable version of CM10.1 (Android 4.2.2) is very good as well.
Now I have a Wi-Fi problem
kwyrt said:
1. I don't know anything about GooManager or if it is compatible with the D4 but safestrap is a really great piece of software that is easy to use. I highly recommend it. Just download and install the app on your phone. Then open the app and install recovery. From there, when you reboot, you will be given the option to boot into safestrap recovery where you can install your ROMs.
2. You will not need to re-root your phone.
3. I am running CM10.2 (Android 4.3) nightlies and have found them to be very stable. I've also heard the latest stable version of CM10.1 (Android 4.2.2) is very good as well.
Click to expand...
Click to collapse
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
I researched online and found lots of people having problems. Some people re-flashed the ROM and it fixed it, others tried this, that or the other and weren't even sure what fixed the problem. Some never fixed it at all.
I did the Wipe/Factory Reset. I re-flashed the ROM. I went back and flashed the 9/27 nightly since 9/28 didn't work. I rebooted my router. I did a Forget on the network and re-added it. My password is correct. I'm at a loss. Not having WiFi with this ROM is like having a great new car that does everything you want except it doesn't do left turns.
Cannonball3804 said:
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
I researched online and found lots of people having problems. Some people re-flashed the ROM and it fixed it, others tried this, that or the other and weren't even sure what fixed the problem. Some never fixed it at all.
I did the Wipe/Factory Reset. I re-flashed the ROM. I went back and flashed the 9/27 nightly since 9/28 didn't work. I rebooted my router. I did a Forget on the network and re-added it. My password is correct. I'm at a loss. Not having WiFi with this ROM is like having a great new car that does everything you want except it doesn't do left turns.
Click to expand...
Click to collapse
Sounds like you have tried most of the things I would have tried to fix it. One other thing you can try: open the Terminal app. Type "SU" and press enter. Then type "wificall.sh" and press enter. That will recalibrate the wifi on the phone. One other thing that comes to mind is I remember some people mentioning when they flashed a new ROM the D4s MAC address got changed which screwed with the wifi connection to their router. I can't remember what the fix was for it, but might be something to google if wifical does not fix it.
kwyrt said:
Sounds like you have tried most of the things I would have tried to fix it. One other thing you can try: open the Terminal app. Type "SU" and press enter. Then type "wificall.sh" and press enter. That will recalibrate the wifi on the phone. One other thing that comes to mind is I remember some people mentioning when they flashed a new ROM the D4s MAC address got changed which screwed with the wifi connection to their router. I can't remember what the fix was for it, but might be something to google if wifical does not fix it.
Click to expand...
Click to collapse
Thanks for the wifical tip. Wi-Fi is now working at my office. When I get home, I'll see if it did the trick there.
Cannonball3804 said:
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
Click to expand...
Click to collapse
Wifi has been hit and miss lately. I had to go back to 9/26 nightly. Didn't have working wifi until 10/2 nightly.
Some of the guys in the development thread found some clues as to why. The must be working on the wifi drivers in the nightlies right now.
http://forum.xda-developers.com/showthread.php?t=2102723&page=83
I just flashed the latest CM (this is my first phone mod) and I working on getting gapps to instal. I have the latest downloaded and am looking for guidance as to how to install the package. This thread looks like a proper place to address that step as it appears to be exactly what you do after you get CM running.
Thanks!
Huli13 said:
I just flashed the latest CM (this is my first phone mod) and I working on getting gapps to instal. I have the latest downloaded and am looking for guidance as to how to install the package. This thread looks like a proper place to address that step as it appears to be exactly what you do after you get CM running.
Thanks!
Click to expand...
Click to collapse
Find the gapps for your version of cm and flash like you did the ROM. Usually you would flash the gapps when you do the ROM.
Sent from my XT894 using Tapatalk
Cannonball3804 said:
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Click to expand...
Click to collapse
1. I prefer safestrap, you can install up to 4 more ROMs in addition to stock ROM. And it's the safest method to try those ROMs
2. That depends on the ROM you are going to install. Most custom ROMs have been rooted already.
3. CM11 that is Android 4.4 KitKat, sweet eh? (correction : CM11 is not stable development yet, but it is latest and nicely working)
I'm currently on the official CM11 nightlies, and I just haven't had the time to go through the entire process required to switch to the 4.4.2 OTA-based CM11 ROM. However, the random reboots and SODs are getting to me so much these days that I'm willing to try something different to quickly flash over to it. I was wondering if anyone knew if the following process would work:
Reboot into recovery
Make a backup of course
Flash TWRP 2.7 and reboot recovery
Flash the 24A OTA bootstack from XDABBEB's VS98024A ROM and reboot recovery
Wipe system, cache, dalvik
Flash JackpotClavin's OTA-based CM11 over my current install and reboot
I realize a dirty flash in this way may introduce its own set of problems, but I'm willing to take the chance if it means I can go straight from my current CM11 install to JPC's without having to wipe everything and go back to stock first.
I'm very comfortable with the command line and I have a good knowledge of how most Android devices work (bootloader, radio, recovery, kernel, cache, system, and data, and how they all tie together, all that necessary info). I just don't really know much about all the extra stuff for the G2 and I haven't had time to research it, so I've got no clue if flashing the bootstack is all I need, or if I'll also have to go hunting for a 4.4.2 radio zip to get the baseband up to date or anything else.
_b_d_ said:
I'm currently on the official CM11 nightlies, and I just haven't had the time to go through the entire process required to switch to the 4.4.2 OTA-based CM11 ROM. However, the random reboots and SODs are getting to me so much these days that I'm willing to try something different to quickly flash over to it. I was wondering if anyone knew if the following process would work:
Make a backup of course
Flash TWRP 2.7
Flash the 24A OTA bootstack from XDABBEB's VS98024A ROM
Wipe system, cache, dalvik
Flash JackpotClavin's OTA-based CM11 over my current install
I realize a dirty flash in this way may introduce its own set of problems, but I'm willing to take the chance if it means I can go straight from my current CM11 install to JPC's without having to wipe everything and go back to stock first.
I'm very comfortable with the command line and I have a good knowledge of how most Android devices work (bootloader, radio, recovery, kernel, cache, system, and data, and how they all tie together, all that necessary info). I just don't really know much about all the extra stuff for the G2 and I haven't had time to research it, so I've got no clue if flashing the bootstack is all I need, or if I'll also have to go hunting for a 4.4.2 radio zip to get the baseband up to date or anything else.
Click to expand...
Click to collapse
Follow steps 3-5 in XDABBEB's thread you posted and you should be good to install the CM11 4.4.2 based release. No harm in trying a dirty flash, worse case you need to wipe and install clean anyway.
Replying to say it worked perfectly, for anyone else in the same situation. I updated from the official CM11 4/26 nightly to JPC's 4/30 CM11 build by following the steps in my first post (and without wiping data or internal storage) and it booted right up with no issues whatsoever like a normal nightly upgrade. Huzzah!
_b_d_ said:
Replying to say it worked perfectly, for anyone else in the same situation. I updated from the official CM11 4/26 nightly to JPC's 4/30 CM11 build by following the steps in my first post (and without wiping data or internal storage) and it booted right up with no issues whatsoever like a normal nightly upgrade. Huzzah!
Click to expand...
Click to collapse
I did this same thing although my previous CM 11 worked just fine except my GPS didnt work. So after this install and upgrading my bootstack and modem to 25A that my GPS would be fixed but its still broken under this as well. Any ideas guys?
xsirxx said:
I did this same thing although my previous CM 11 worked just fine except my GPS didnt work. So after this install and upgrading my bootstack and modem to 25A that my GPS would be fixed but its still broken under this as well. Any ideas guys?
Click to expand...
Click to collapse
Did you make sure to get a GPS lock on a stock based 25A ROM by opening maps and letting it locate you? That seems to calibrate the GPS sensors.
JRJ442 said:
Did you make sure to get a GPS lock on a stock based 25A ROM by opening maps and letting it locate you? That seems to calibrate the GPS sensors.
Click to expand...
Click to collapse
up
I found that I had to go to a stock-based 25A ROM to fix this as well. Not a big deal - first back up everything in TWRP, wipe everything except internal storage, flash xdabbeb's ROM, get the GPS lock, then reflash as above (not really necessary if you're restoring but I did it anyway), then restore from backup.
I'm now on a 25B bootstack (dirty flash) and so far, so good - it's much more stable than straight CM11.
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
I read everywhere that the safest way is to do a full wipe, and since you have nothing to lose it won't hurt, so i think you should.
nickos12 said:
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
Click to expand...
Click to collapse
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
so i sould install the nighlty without wiping?
TechnoSparks said:
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
Click to expand...
Click to collapse
so i sould install the nighlty without wiping?
nickos12 said:
so i sould install the nighlty without wiping?
Click to expand...
Click to collapse
Yes you may
Ok thanks
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
TechnoSparks said:
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
Click to expand...
Click to collapse
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
giannisv6 said:
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
Click to expand...
Click to collapse
Yes, nightly is a daily release where changes are huge in the back end.. Sometimes a simple change can make a build unbootable. Sometimes it introduces new bugs. Sometimes it is better and fixes everything. It is of course a good thing to update to the latest if possible, it is just that it is also vital to know what we're going to face when we flash a new update. So that we can make backups beforehand in case something really bad happens.
If you are installing an update to the same ROM there is no need to wipe anything. Wiping is optional.
↑ Note, if you are reverting to a previous build, you will need to wipe everything as there will be conflicts for the system data. This is why frequent/periodic app backups useful.
You can do either both of them without any problem
Thank you very much.
It's the first time i flashed a custom rom (the AICP 10 successfully :cyclops: ) and i got overwhelmed with all these endless customization options .