Database Info

[Q] Need help flashing img via Fastboot - am I bricked?

Had just flashed the latest CM9 nightly (clean install, fresh wipe) yesterday and everything was running fine.
This morning, woke up, my phone was turned off. When powering it on it hung on the google screen. Fastboot still working, booted into recovery only to find that I would get error messages when trying to load my backs "E:unable to mount /sdcard". Apparently it also couldn't mount /data. So I was unable to flash any images or restore or boot up.
Seeing that fastboot was still working I assume I'm not bricked yet. I tried flashing a new boot and cwm recovery via fastboot - no dice. Same errors.
I don't have a recent backup of anything in sdcard, but at this point I'm willing to sacrifice it.
Found this thread http://forum.xda-developers.com/showthread.php?t=1078213
and I'm trying to follow the steps to flash back to stock GB. using the GRJ22 images
It flashed the boot and recovery without issue but seems to hang while flashing the system.img. I know it's a big file, but it was up to ~2hrs with it still transferring. I pulled the plug on it and tried again, lost patience after an hour.
Now I had the idea of maybe locking and unlocking the boot loader would help things.....not sure why I thought this. Anyway, now it seems to hang on the unlock bootloader screen.
So my question now - am I screwed?
- anything else to try?
- is it really "hanging" or do I need to give it more time?
- have I screwed myself even more by now locking my bootloader and flashing the stock recovery?
Any help would be very much appreciated....

Some new additions and new insights from the reddit android community:
- this probably has nothing to do with CM9. My phone has been wonky for about two weeks - random reboots, sometimes rebooting into recovery. That's why I thought I'd throw on the latest nightly and do a fresh wipe yesterday.
- There's definitely something up with /data. Anytime I tried wiping all/factory reset in cwm recovery I got errors about not being able to mount /data or being able to find files in /data
- basically anything I do involving /data partition causes the phone to lock-up -- flashing the boot.img and recovery img worked, but not system. Also, I think the reason I can't re-unlock the bootloader is because during the unlock process it tries to do a factory reset/data wipe
Basically I think there are two things I need to know if I can do - 1) unlock the bootloader again, via some way that won't try to reset the /data partition and thus won't freeze the phone. 2) try repartitioning /data
I really hope I didn't screw myself by locking the bootloader. I'd actually feel a lot better if it was something in my phone that just failed hardware-wise rather than something I could've fixed if I wasn't too quick to try poorly thought out ideas.....
Any help at all would be appreciated!

Possibly (and likely) a corrupted nand flash. Fairly common problem sadly. I'd say it's a good thing your bootloaders locked, no dramas sending it back to samsung. It might've been possible to reset the partitions and flash fastboot images but i don't think i've seen anyone who has done this to sort any similar problem. Hopefully your phones still under warranty

Well thank God that it turns out that I'm still on warranty.....sending the phone back to Samsung tomorrow.
Like you said, it's actually a good thing the bootloader is now locked and the stock boot img and recovery img are now back on! Hopefully this makes it more likely that they weren't turn away my phone.

I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.

Harbb said:
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Click to expand...
Click to collapse
I bricked my nexus s 4 days before Christmas last year... and i was using a custom rom obviously with an unlocked bootloader and custom recovery image, and i handed it to vodafone, and guess what? they repaired without asking any questions, and the day before Christmas! sooo happy maybe because i was thirteen then, they didn't suspect a thing

Samsung Tab 2 10.1 (CM11) unable to wipe/factory reset/install CM update

I have been routinely flashing CM 11 ROMs on nightly basis since the past year without any problems. However, the last Nightly I installed started giving me errors like xyz.process.com stopped etc etc. So, I decided to wipe everything through my TWRP recovery by wiping cache, data, internal storage (I have done this before for a clean install many times), but this time even when I wipe EVERYTHING and flash the latest nightly and the Gapps, the tablet boots into the same old version. I have done this repeatedly but with no success.
The strange thing was that when I even tried uninstalling individual apps, like I installed Whtsapp, Viber, Twitter, a few games, they did get uninstalled but on the next reboot, all the apps were back?! How is it even possible?!
Steps I have done to resolve this issue:
1-Flashed the newer ROM, nothing changed.
2-Tried wiping everything to no avail.
3-Tried flashing stock ROM like 20 times via Odin but it always fail midway.
4-Tried flashing Philz recovery via Odin, it succeeds but when I reboot in recovery, the same old TWRP recovery is there.
5-Tried flashing newer TWRP recovery via img file by booting into recovery,finding the img file and flashing it, it also succeeds but when I reboot into recovery, it still boots into the older TWRP recovery.
6-Tried flashing newer TWRP via Odin, it too succeeds but when I reboot into recovery, the old version is still there.
I mean, anything I do, the system wont change/wipe. Please help!

16gb Tab2?
Sounds like a emmc issue,maybe a emmc firmware update is needed to get back right access to your tab, in bad case the emmc needs a replacement. If you are from europe: i know someone from austria who can fix it for you. Added some notes about that issue on the faq on my github userpage.

Can you install https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check and post a screenshot of it?
~ All my work, news etc. on http://andi34.github.io ~

I tried install the app but was unable to as the gapp.google.com stop working thing wont let me. So I tried installing it through the web, it didnt install but the tab rebooted and is now stuck at boot. Wont shut down either

How to fix the emmc issue? Update? I m far away from Europe

Rag888 said:
How to fix the emmc issue? Update? I m far away from Europe
Click to expand...
Click to collapse
Update the emmc firmware (only via ISP possible) or replace the emmc. Maybe you can find someone who's able to do it...

Android-Andi said:
Update the emmc firmware (only via ISP possible) or replace the emmc. Maybe you can find someone who's able to do it...
Click to expand...
Click to collapse
Via ISP? Pleas explain. And are we sure that this is am emmc problem? Because I can boot and use the tab to some extent, it's not totally bricked I guess. What about the procedure here: http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862

Rag888 said:
Via ISP? Pleas explain. And are we sure that this is am emmc problem? Because I can boot and use the tab to some extent, it's not totally bricked I guess. What about the procedure here: http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
Click to expand...
Click to collapse
I am not an expert on this, someone else would have to explain it if you have further questions about ISP etc.
I am quite sure it's the problem, if wipe / format does nothing and flash via odin also doesn't change anything... Your emmc is read only...
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
Click to expand...
Click to collapse
On a faulty EMMC firmware it happens a lot faster.
There's no way to boot from microSD, you would need to flash a modified boot.img at least which is imposible if the emmc is read only.
~ All my work, news etc. on http://andi34.github.io ~

Thanks for your input. Well, Odin is able to write the recoveries to the Tab, and shows that they are pass, doesnt that mean it is still writing? Also, Odin attempts to write the stock firmware but fails half way, I also also suspect a faulty cable. And should I try the procedure given in the link I quoted?
I am also downloading the Jtag suite like here: http://forum.gsmhosting.com/vbb/f672/p5100-how-repair-2118618/

Ok, I just saw your website https://andi34.github.io/faq_de.html I think I am screwed.

SMG386T1 Partition Recovery

Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...

shmusername said:
Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...

shmusername said:
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...
Click to expand...
Click to collapse
Oh, you mean you want to recover your lost data. All I can say is try some data recovery software on PC, there isn't any guarantee that it will work though. Data recovery on android is not very reliable.
Sent from my LGL84VL using Tapatalk

Bricked my OP7P - Can't decrypt data partition anymore

Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.

the.cybertronic said:
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
Click to expand...
Click to collapse
The bad news is once twrp loses access to data. The only fix is to format data and everything will be fixed.

So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
The reason that format is the only answer is because when twrp does not ask for password. It believes you are unencrypted. What has happened is the file that store your password and encryption key is corrupted so any answer you give is wrong.

There's nothing you can do but format data. I've encountered this issue already.

You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?

Joker123## said:
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
Click to expand...
Click to collapse
vegetaleb said:
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Click to expand...
Click to collapse
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
Zhuang zhuang said:
There's nothing you can do but format data. I've encountered this issue already.
Click to expand...
Click to collapse
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.

the.cybertronic said:
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
For future reference, brick means a brick. Like, can't boot to fastboot/twrp/or use msmtool

the.cybertronic said:
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue

Zhuang zhuang said:
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Click to expand...
Click to collapse
damn, good to know if I ever install OOS again - I now switched to Havoc... even though I had to skip rooting it all together after I couldn't get Magisk running with the latest safety net changes (thanks Google -.-)

Flashing Kernel Patch for RMM on unsupported Note 9 caused it to stop booting

Hello,
I've been trying to root my Note 9 using the "N960F_DS_N_Oreo_Root_for_OEM_issue_devices_V5" which I've found online and i believe it is based on what was developed by Dr. Ketan.
While flashing this setup, I selected "Proceed with ROM Flash and Multi tool", "Patch for OEM issue", "Flash Kernel Patch for RMM" and then "Root with Magisk". Once the installation is done and the device is rebooted, the phone no longer boots. It shows the logo Galaxy Note 9 powered by Android then black screen then loop again to Galaxy Note 9 logo and it stays in this loop. I can only break the loop by entering to the Download Mode and loading TWRP and staying there.
I'm suspecting that the "Flash Kernel Patch for RMM" that I've selected is not supported on my Note 9 Model.
Is there a way to revert back this change? or may be install back the default kernel?
Appreciate your help!
Regards,
Elias

As I can see you are proud owner of a softbricked phone.
My recommendation: re-flash phone's Stock ROM to get rid off of all mods you applied to the phone.

jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
My recommendation: re-flash phone's Stock ROM to get rid off of all mods you applied to the phone.
Click to expand...
Click to collapse
Thanks for your help.
I've downloaded this: https://androidfilehost.com/?fid=4349826312261705548
It's around 4.8GB. Is this what you're referring to?
Just to give some background, the phone got an accidental factory reset (which I still don't understand how) and i'm trying to retrieve at least some of the deleted data (mainly pictures/videos). All the recovery tools requested to have the phone rooted in order to do a deep scan. So I started this learning journey myself since no phone repair store was off help.
Would reflashing the phone stock ROM affect my chances of retrieving my data?
Thanks!

The Factory Reset performed erased all your user data: though they are still physically present on device, their entry in Android's MTF got removed. IMO it requires a forensic tool to recover them.
As soon as you re-flash the phone with Stock ROM the disk space utilised by user data again gets wiped ( means a new MFT gets created), so the chance to recover user data previously stored there is NULL.

jwoegerbauer said:
The Factory Reset performed erased all your user data: though they are still physically present on device, their entry in Android's MTF got removed. IMO it requires a forensic tool to recover them.
As soon as you re-flash the phone with Stock ROM the disk space utilised by user data again gets wiped ( means a new MFT gets created), so the chance to recover user data previously stored there is NULL.
Click to expand...
Click to collapse
I was checking this thread on this form: https://4pda.to/forum/index.php?showtopic=915992&st=520
it seems that it's the same problem as mine and he was able to resolve it by flashing the original kernel. Not sure how i can do the same.

EN90 said:
I was checking this thread on this form: https://4pda.to/forum/index.php?showtopic=915992&st=520
it seems that it's the same problem as mine and he was able to resolve it by flashing the original kernel. Not sure how i can do the same.
Click to expand...
Click to collapse
With regards to recovering wiped user data: As I can see you didn't get it.

jwoegerbauer said:
With regards to recovering wiped user data: As I can see you didn't get it.
Click to expand...
Click to collapse
hmmm, what i understood is that if I go and flash the phone with Stock ROM (to make it boot again) I'll lose any chance of getting my data back even with a forensic tool. Is that what you meant?
So I was trying to say that what if I just flash back the original kernel to solve my booting issue, would it also affect the possibility of retrieving the lost data?
Unless I'm confused with the terminologies and flashing kernel is the same as flashing the Stock ROM. I'm quite new to this .
I appreciate your help!

@EN90
As with Android
Kernel is the core part of Android OS and is based on Linux. It is the system which initializes, configures and sets all hardware components for use. It prepares the complete system for functioning. It consits of several sub-systems and services.
Stock ROM is a read only memory chip on the phone's motherboard that contains the Android OS image that boots every time you turn on your phone. A ROM contains full Android OS system and a few system apps that comes pre installed with the device.