Site icon Yaabot

4 Problems When Flashing Custom ROMs And Their Fixes

Android origin

Being an Android operating system is a tough job. But our little green guy knows his job well and adjusts himself to suit our needs. We can groom him and change the way he works too. You just need to know what you want and how to get it.

Right from the theme, the UI, the kernel, the recovery, anything and everything of your Android smartphone can be tweaked to suit your needs. The OS is truly like the desert it is named after. This work is fairly easy, but sometimes flashing a Custom ROM can be a headache, it might lead to unexpected and unwanted errors and our little green guy may become sick or go into a coma. For those of you who are having problems with this process, here’s our little list of errors you could face while flashing ROMs and a tutorial on how to fix these common errors.

From Earlier: 7 Reasons You Should Switch to an MIUI ROM

#1 – Your handset is stuck in a Bootloop


Android BootScreen

Well, this is the most common issue when talking about Android devices. Also, the problem can be easily fixed as you only have to wipe the system of your device. Usually, the boot loop problem occurs when you forget to wipe the data from the phone after flashing a ROM as there are residuals in the ROM from the developers which don’t allow the phone to boot up completely.

ClockWork Mod Recovery

Now, in this method we assumed that you have installed a custom recovery image on your handset: like CWM recovery, AmonRA, TWRP recovery and so on. Use the recovery for wiping the system of your handset thus resolving the boot loop issue. Be aware though as each device can be entered into the recovery mode differently; usually you need to press a combination of buttons (for example on Samsung you need to press Volume Up and Home buttons) while Powering up your tablet/smartphone. Once the recovery mode entered you need to follow the following instructions:

So, there you have it; now the boot loop problem should be resolved and you should be able to safely use your custom ROM firmware.


#2 – Your handset doesn’t allow the flashing of a ROM showing ‘Status 7 error’

Status 7 error

When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter ‘Status 7’ error issues once in a while with ClockWorkMod (CWM) Recovery.

Status 7 error is caused when the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called ‘asserts’

‘Asserts’ is a safety mechanism which prevents you from accidentally installing another phone model ROM on your phone.

Now, this safety mechanism is great but there are times where even if you have the correct ROM for your phone, you will get the Status 7 error. This is due to an error by the developer of the ROM in the updater script, causing havoc, making people install another custom recovery like TWRP recovery for no reason. You can fix the issue by installing TWRP recovery but if you need to restore your CWM backups later down the line, you will have to re-install CWM recovery, causing a big hassle.

Also, if you update to the latest CWM Recovery using ROM Manager, usually this problem is fixed.

But what if you did update to the latest CWM Recovery and still happens? And yes, it does happen even when you update your CWM recovery.

If you simply don’t want to change your recovery (because if it isn’t broken, don’t fix it) or you still get Status 7 error after changing the recovery, you can simply edit the updater script yourself to get rid of the asserts.

All you need is a computer and a compressing program! You might even be able to do it on your Android device with AndroZip and a text editor.

ROM zip file
Location of updater-script
The Text to be Deleted

#3 – Your device is booting straight to bootloader mode

In this case, the only way in which you can resolve the problem is the stock Android OS. Yes, unfortunately you will have to flash the official Android firmware on your device. In this way you will be able to restore the stock restrictions and default settings and your smartphone/tablet will be restored to its initial state.

Of course, if your handset is rooted, after flashing the stock ROM, the root access will be revoked and the bootloader relocked. The best though is that you will be able to restore the lost warranty and the default Android system with stock features, apps and capabilities.

Now let’s see how you can update or downgrade different devices to stock/official Android firmware:

For Samsung:


For HTC:

The HTC stock ROMs are dubbed as RUU and the same can be flashed straight from bootloader mode.

For Motorola:

RSD lite

For Sony:


#4 – Your handset boots straight to recovery mode

In case, after flashing a custom ROM, your handset enters right to the recovery mode, then you can try to wipe the system and see the results. But, most likely the wiping solution will not work here. You see, if your device is stock in recovery mode, then it means that you have flashed an inadequate ROM, or there is something wrong with the ROM you choose.

Therefore, you will have to re-install the firmware on your phone. You could follow the same steps as with the previous issue or you could just flash another ROM from you SD card.



These were few of the most common problems faced by newbie developers while flashing ROMs. We hope this was helpful. If you have any other problems or suggestions, feel free to comment your queries, we will be happy to help.

Exit mobile version