[Galaxy Y GT-S5360 Android Development] CarlDeanCatabay:
Installation Troubleshooting Guide

​

INSTALLATION TROUBLESHOOTING GUIDE

​

In the past days, as we have observed, there had been installation issues for new and existing users. We know how annoying it is to get a bootloop, installation aborted and many installation related problem, so here you go, I will put every single scenario that had been reported and the best solution to install the best (according to users) rom when it comes to performance and style :victory:

Whenever I flash a new build, I have this "one-shot-install" method I am keeping. This one works whether you are jumping from one kernel to another. The one-shot-install step is:

Flash stock via Odin (Recommended)

Format SD Card to remove any unwanted files, orphaned data from previous ROM and of course, junk files.

Copy Hyperion zip package to sd card

Reboot to CWM using TempCWM if you are on stock ROM, or the built in CWM from savie's kernel if you are a previous Hyperion user and skipped flashing stock via Odin

Go to Mounts and Storage and mount /system, /data, /cache and sdcard

After mounting, Go back to main menu using the power button

Navigate to Advance (Advanced and Debugging)

Select Wipe dalvik-cache -this helps you avoid bootloops

Select Wipe batterystats -this ensures your battery gauge gets re-calibrated on first boot

After doing wiping dalvik and battstats, Go back to main menu using the power button

Select Wipe data/reset

Select Wipe cache

After doing data and cache wipe, select install update from sdcard

Select zip from sd card

Select Hyperion zip pacakage and install

Wait for the system to complete installation, it will take 2-5 minutes (maximum) to complete installation

Reboot your device

BELOW ARE THE REPORTED SCENARIOS AND POSSIBLE CAUSES WHY INSTALLATION FAILS
​

COMMON FAILED INSTALLATION SCENARIO(S)

SCENARIO 1:

"I flashed Hyperion after flashing stock rom via Odin but every time I use Temp CWM and try to flash Hyperion, it goes back to stock recovery. No error is shown on recovery"

CAUSE OF ISSUE:

Incomplete download.

HOW TO AVOID:

Use a MD5 Sum checker. You can ask our dear friend Google for any md5 sum checker, it's free and it is usually less than 1 MB to download. Always make sure your zip package is intact and complete.

QUICK GUIDE TO CHECKING MD5 SUM:

Open your MD5 checker

Select the Hyperion package you downloaded

Paste the MD5 sum value from the download page in DevHost (MD5 Sum: c8a0b092b53165db700943ba72b885d3)

If it matches, then that means the zip package you have is intact and complete
​

SCENARIO 2:

"I can't flash Hyperion via stock or CWM, it shows installation aborted"

CAUSE OF ISSUE:

Bad or damaged zip package

HOW TO AVOID:

Check the md5 sum and make sure your zip package is not damaged. If it is damaged, md5 checker will show you MD5 Hash Sum mismatch.
​

SCENARIO 3:

I flashed Hyperion but nothing happened, I still have stock rom or previous custom rom

CAUSE OF ISSUE:

/system, /data, /cache partitions were not mounted in CWM prior to installation

HOW TO AVOID:

Super duper hyper mega easy; Go to Mounts and Storage and make sure they are all mounted
​

BOOT LOOP SCENARIO(S)

SCENARIO 1:

"I am using a custom rom and I flashed Hyperion on top of it without flashing stock via Odin. After flashing, my device goes to endless boot loop. My previous custom rom includes a custom kernel"

CAUSE OF ISSUE:

Custom kernel (boot.img) from previous ROM

HOW TO AVOID:

The safest way to install a custom rom (in this scenario, Hyperion) on a device running a different custom rom with custom kernel is to revert back to stock rom first because jumpring from one kernel to another will surely cause boot loops. That is why we always recommend flashing stock rom first before flashing Hyperion.
​

STUCK AT BOOT LOGO SCENARIO(S)

SCENARIO 1:

"I am using a custom rom with repencis kernel or merruk kernel prior to flashing Hyperion. After flashing Hyperion, I am stuck on boot logo (the samsung galaxy y blah blah screen)."

+

Same scenario above but; "I flashed stock rom via odin, but every time I do wipe data/factory reset and wipe cache, it shows me error mounting rfs blah blah"

CAUSE OF ISSUE:

Both repencis and merruk are known to convert your device's File System (FS) to EXT4. If your device's file system is EXT4 and not RFS (Robust File System), flashing Hyperion will fail, but boot.img (kernel) will be flashed.

SYMPTOMS OF EMMC FORMATTED TO EXT4:

CWM cannot mount /system but all partitions can be mounted

Stock recovery cannot do data and cache wipe

HOW TO AVOID/FIX:

Given your phone is already formatted to EXT4, there is nothing you can do but to repartition your device's EMMC (the chip where we install the device's OS) using Odin.

But remember I have written "but boot.img (kernel) will be flashed"? This will help you in solving this kind of issue.

Please keep in mind that this issue is not a problem with Hyperion rom, if CWM and Stock recovery cannot mount your /system partition, no custom rom can be successfully installed on your device.

Now this is the work around . . .

Since boot.img will always be flashed, that means if the kernel on the rom you are installing have CWM installed, then you will have CWM as recovery.

Now that's a good news because your default recovery now is CWM, and you can use it to format partitions back to its default file system. Follow the steps below:

Remove the battery of your device

Press the recovery key combination to boot into recovery

If you are lucky, you will be able to reboot to CWM (given you flashed Hyperion)

Once you are in recovery, Go to mounts and storage and format /system, /data and /cache

Once format is successful, reboot recovery using the "Reboot recovery" option

After rebooting recovery, mount the partitions and try flashing Hyperion again.