[Q] Custom ROM, kernel and recovery - Galaxy S 4 Q&A, Help & Troubleshooting

Hey everyone!
I would like to flash P.A.C.-MAN ROM on my phone, and also a new kernel, and I need some help with that.
As of right now, I am rooted with DjEmbey's root-method, and have BusyBox and SuperSU installed. I have a regular i9505, XXUAME2, 4.2.2, official device status and all Know related items removed. Do I need to do some kind of updating of my device, before doing any flashing, or do I only have to wipe /data, cache etc.?
I've read some in the P.A.C. Q&A thread on how to flash a custom recovery. But before I flash a new recovery, should I format /data, cache and Dalvik cache? I've heard people recommend TWRP over CWM, is it more stable or have better functionality, is TWRP compatible with P.A.C.?
For a new kernel, I've thought about this one. Is it compatible with P.A.C. ROM?
After I've flashed a custom recovery, should I always format /data, cache, Dalvik cache and fix permissions, before and after every kind of flashing?
Is BusyBox and (or) SuperSU reserved when flashing a new ROM and kernel, will it be included in P.A.C. or do I have to install it manually?
Thanks in advance for all answers

There are plenty of guides and Google is your friend.
Flash recovery via Odin. I use CWM never had a problem. If your nervous about flashing get the SGS4 flasher and flash recovery through the app. Then reboot and jump into recovery volume up + home button + power ( let go of the power button once you see the screen turn on). Do a full wipe cache davlik. I also go to mounts and format /system. Then install your ROM from the SD card. Good luck.
Echoe ROM. Rock Solid. Stable. Blazingly Fast with Adam Kernel.

Related

[Q] Flashing ROM and Kernel question

So when I root my phone using this method: http://forum.xda-developers.com/showthread.php?t=858996 (TRUE PermaRoot and the ULTIMATE S=Off) and then comes time to install the ROM and with that the Kernel... in this case: "MIUI 1.6.24 demonSPEED v1.1" it is recommended that I also update the kernel to "demonSPEED INSANITY v2.0"
So I wiped everything and then flashed the ROM and then shutdown the phone and then booted into recovery and then wiped everything and then flashed the kernel.
My question is: Did I do this correctly or should I have done something different.
Here is my hboot info after I rooted my phone:
GLACIER PVT SHIP S-OFF
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Your results posted only show that your phone has root and s=off. When flashing a rom wipe everything (wipe data/factory reset, wipe cache partition, advanced then wipe dalvike cache, then flash rom. After flashing the rom wipe cache partition and dalvik cache again then install custom kernel. Eveything can be done in recovery.
Sent from my Acer Iconia Tab A500 using XDA Premium App
I do understand that everything can be done in recovery.
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Or can I do both (ROM and Kernel) like this:
1) Boot into recovery.
2) Wipe Everything
3) Flash ROM
4) While still in recovery wipe everything
6) Flash Kernel
7) Reboot.
aybe said:
I do understand that everything can be done in recovery.
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Or can I do both (ROM and Kernel) like this:
1) Boot into recovery.
2) Wipe Everything
3) Flash ROM
4) While still in recovery wipe cache partition and dalvik cache (in advanced)
6) Flash Kernel
7) Reboot.
Click to expand...
Click to collapse
See minor change in step 4...After reboot I would open ROM manager and select fix permissions and reboot then u will be set....other than that you got it
Sent from my Acer Iconia Tab A500 using XDA Premium App
aybe said:
I guess my question is that after I flashed the ROM (after wiping everything of course)... should I shutdown the phone and then start back into the recovery right away and then wipe everything and then flash the kernel or should I let the phone start up normally after the ROM wipe and then shutdown and reboot into recovery followed by wiping everything and then flashing the kernel?
Click to expand...
Click to collapse
It sounds to me that the problem is you're wiping "everything" before flashing the kernel. If you do a full data wipe, you're wiping the phone clean including the freshly flashed ROM. Try following this procedure: wipe everything, flash ROM, let it boot/reboot, wipe only cache and Dalvik-Cache, flash kernel, boot again, fix permissions, reboot. That's the standard procedure for flashing a custom kernel other than the kernel that comes with the ROM.
TeeJay3800 said:
It sounds to me that the problem is you're wiping "everything" before flashing the kernel. If you do a full data wipe, you're wiping the phone clean including the freshly flashed ROM. Try following this procedure: wipe everything, flash ROM, let it boot/reboot, wipe only cache and Dalvik-Cache, flash kernel, boot again, fix permissions, reboot. That's the standard procedure for flashing a custom kernel other than the kernel that comes with the ROM.
Click to expand...
Click to collapse
I actually haven't had a problem yet. Just wanted to make sure if what I did was the correct way to do things or not. Since there haven't been any problems and everything is working correctly so far, would you recommend that I reflash both the ROM and the kernel using the method you provided or should I just leave it be?
Thanks.
aybe said:
I actually haven't had a problem yet. Just wanted to make sure if what I did was the correct way to do things or not. Since there haven't been any problems and everything is working correctly so far, would you recommend that I reflash both the ROM and the kernel using the method you provided or should I just leave it be?
Click to expand...
Click to collapse
If you have the ROM and kernel you want loaded, and it's running smooth and stable, I would say leave it as is. Just refer to the steps I detailed the next time you flash a ROM followed by a third-party kernel.

cant flash new rom

Hi
I have a acer iconia a500 and i was trying to flash a rom using the acer recovery installer, i have dont this about 10 times but this time when i booted into the recovery kernal then wiped the chache and the dalvick cache and the battery stats then installed minimalist 3.1 it installed then i rebooted and it did not have the launcher and all my apps where still there. How can i fix this i have tried other roms same thing i need help fixing this
Not only wipe cache user data.i format partitions as well. Reboot back into car.and wipe cache again after flashing rom before booting into it first time.there is a thread about this
+1 to erica
You need to do a *full* wipe before flashing a new ROM.
if i do a full wipe will i loose all my data ie music etc also where is the thread about it?
If running it fro Acer recovery installer, just check the 'wipe data' checkbox. It won't erase your /data/media files. This is all I do when flashing a new rom. Have never had any issues.
Sent from my A500 using Tapatalk

Cache partitions erase error.

Guys, I need some help with my Galaxy S4 - 9505.
I'm running Omera rom with TWRP recovery.
I had one random restart and decided to wipe cache and dalvik. But I can't. , recovery report that cache could not be mounted.
I changed recovery with PhilZ but its the same. Also the partition size is shown 0MB.
This is the second time i got this issue.
Could anyone of you help me to understand why this happen?
re: cache issues
samo_ said:
Guys, I need some help with my Galaxy S4 - 9505.
I'm running Omera rom with TWRP recovery.
I had one random restart and decided to wipe cache and dalvik. But I can't. , recovery report that cache could not be mounted.
I changed recovery with PhilZ but its the same. Also the partition size is shown 0MB.
This is the second time i got this issue.
Could anyone of you help me to understand why this happen?
Click to expand...
Click to collapse
First you should do a nandroid backup.
Your best bet is to do a system reset (under settings in the phone) and then download the stock odin
flash pre-rooted i9505 rom from here: http://forum.xda-developers.com/showthread.php?t=2409867
Odin flash it and then check out the phone make sure all is well.
After that get the Odin flashable Philz, CWM or TWRP recovery and flash it, (or simply use goomanager to get twrp)
then get the latest update of SuperSU and flash that in recovery. (both goomanager & superSU are free apps at the playstore)
Then after checking everything out making sure everything is working properly make another nandroid backup.
After that flash any of the i9505 compatible custom rom you like.
@Misterjunky, thanks for the reply.
I actually have done this first time i got this issue, so did same and now.
More or less I try to understand why cache got corrupted? And could this be some kind of hardware issue with the internal memory.

[Q] Flashing various TW Lollipop fw over existing CM12 fails

Hello,
actually I'm using a SGS4 I9505 with cm-12-20150304-NIGHTLY-jfltexx and CWM 6.0.5.1.
I've tried to flash several TW Lollipop firmware wich i found in the I9505 forum:
1. Kushan+Touchwiz+Lollipop+Lite+Rom+v.1.2
2. S4_Echoev42_EchoePop2_020315
3. OA7-2.1F
4. XXUHA07-v2.01
Before flashing any oft this firmwares i made a factory reset, wiped both caches and installed the modem Firmware via Odin.
After flashing firmware # 1 and 2 my phone was stuc in a bootloop (only Samsung Galaxy S4 Logo appears).
Flashing firmware #3 and 4 fails and cwm reports error 7.
Flashing cm12 afterwards isn't a problem and runs fine.
I think the wipe fails or doesn't work properly. Is it enougth to select factory reset in cwm and wipe the dalvik cache manualy?
What can I do?
With besteht regard
Mirko (NemesisMF)
What if it is a recovery problem?
Thought about that too.
Should i try twrp or philz?
I switched to Philz Recovery and flashed S4 Echoe Rom v42 without any Problems.
CWM seems to have a problem to falsh TW Lollipop images ower an existing CM12 an the I9505.
You need to do full wipe not just cache.
ranger4740 said:
You need to do full wipe not just cache.
Click to expand...
Click to collapse
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Factory wipe is not full wipe, you need to do a full wipe as in format to install new rom, phillz recovery has this feature can't remember exactly where, I think its under advanced.
Just have a look in the sub menus.
Just to explain it better when you do a full wipe it deletes every part of the existing
Rom including the system, data and cache and some other stuff completely removing the android operating system, so unless the rom you install does a wipe before install parts of the existing system will remain and can cause boot issues. For example as you've already discovered you are trying to install a tw rom over an existing cyanogenmod 12 installation which Will cause it to hang on boot.
NemesisMF said:
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Click to expand...
Click to collapse
Do you mean a factory reset from within Android itself? If so, then that's a complete obsolete step. When before flashing a rom you should perform a factory reset, then they always mean a full wipe from the recovery. You need to do a full wipe from the recovery. That means the /system partition is being wiped. You will see it in the screen during the wipe if it wipes /system.
But it also could have been a problem of CWM. I don't think it is being updated anymore, so better use TWRP or Philz.

Will flashing a stock firmware with odin reset a custom rom?

I have the batman rom installed on my g95ff now since my stock rom got boot looped when i tried to flash a boot logo that was a size too big.When that happened i flashed the stock firmware with odin aswell as stock recovery and it let me clear my cache/factory reset my phone to fix it.Sadly i lost my bootlogo and boot animation collection i had stored but i had most of my important apps backed up with titanium,so to make up for the lost data i rerooted with twrp,installed the batman rom and restored my apps back.The rom is really neat since i can customize more ui things such as the status bar aswell as my nav bar color which couldnt be done on the stock rom.So now that im familiar with installing roms,would i be able to try other ones simply by reflashing the stock firmware over the batman rom and reinstalling twrp?
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
the_scotsman said:
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
Click to expand...
Click to collapse
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
iostoandroidconvert said:
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
Click to expand...
Click to collapse
Yep, the "System" partition is where the ROM is installed. When you wipe that, you're essentially wiping the ROM from your phone.

Categories

Resources