1

Please, help me with the following questions:

Q1). Where is the original stock Rom of the Android device is usually stored?

Q2). Is it possible to delete the original stock Rom completely from the Android device? In case, we have already rooted the device with a different customized Rom.

Any resources, tips, guides, or short answers will be greatly appreciated.

Thanks in advance for your help!

Note: My device is Huawei Honor 7 - PLK-L01.

Improve this question
2
  • 2
    "Where is the original stock Rom of the Android device is usually stored?" -- literally, usually in a ZIP file somewhere on the internet. Anyhow, the device doesn't keep a copy of all the files, but the overall stuff after flashing is inside /system which is technically what Android OS contains. 2) Yes, boot into custom recovery and wipe /system. Whatever ROM you've had would be gone for good. 3) Please do a thorough search/research for an answer before asking your question.
    – Firelord ♦
    Commented Nov 9, 2015 at 10:53
  • 1
    Thank you for your comment. It would have been nice to see it as an answer though. I am aware that you down-voted my question and from your note, it seems that you were not happy while commenting on it. To answer your comment, i did research very well before asking this question. Using search engines to find specific technical questions is not as easy as many think it is. On any rate, thanks again for taking the time to answer that. I can't upvote your comment since my account here is new and pretty much restricted until i collect my first 15 points.
    – Ken
    Commented Nov 9, 2015 at 17:19

1 Answer 1

Reset to default
2

This is based entirely off @Firelord's comment, with some modifications, so all credits go to him.

First things first, the stock ROM is not as such stored anywhere on device in a form which the device can use to recover itself in case of some catastrophic software failure, such as a botched OTA.

Now, as to how stock ROMs are stored for distribution, that is an entirely different issue. The method of ROM distribution or loading onto devices vary from OEM to OEM, even carrier to carrier. We find 3 common types of ROM distributions:

  1. ROM image files (700-1400MB): These are like Windows System Images, as such being a logical bit-for-bit copy of an on-device partition, which can be written to the device's NAND storage by a flashtool such as fastboot, nvflash or SPFT, while the device is tethered to a PC/Mac. These are usually distributed as archives, but cannot be flashed as such, they need to be decompressed separately before flashing.

  2. ROM zip files (250-600MB): These are also system images in essence, but they are compressed and lack some model-specific or device-specific partition images to lower distribution size as these are installed, in compressed form, on-device via the device's recovery. Some manufacturers do this, but this is commonly the distribution format for custom ROMs.

  3. ROM OTA zip files (4-200MB): These are like ROM zip files, but instead of having all the system images in the zip, these contain image patch files. They are also installed via recovery. This method helps in reducing update file size to meagre amounts when major system changes are not involved in the update.

When we talk about custom ROMs, only methods 2 and 3 are important. Only some for some Cyanogen OS devices does CyanogenMod provide ROM images for fastboot flashing.

Well, now you could wipe your device's /system partition, but note that while installing the custom ROM you already did that, and so there isn't a stock ROM on device to speak of. Wiping /system now would remove your custom ROM which you had installed, and then you would have to flash either a stock or custom ROM to make the device usable again.

Note something here: Stock recoveries cannot flash custom ROMs as the custom ROMs do not have the digital signatures that the recovery verifies before flashing them.

Similarly, custom recoveries such as CWM or TWRP cannot flash stock ROM zips as the zip checks for the integrity or stock nature of the device, which has been compromised by the presence of the custom recovery itself.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .