I have a Samsung S5. On the box, on the sticker inside the unit, checking the IMEI and using CPU-z they all said the unit is an SM-G900F and is using the Snapdragon core.

My biggest problem with it is I want to be able to back the entire unit up so that if I mess it up, I can put it back to its original state. There is no simple universal backup method, so I used ADB to do the following command:

dd if=/dev/block/mmcblk0 of=testsystem.img

I made changes to the programs and did this command:

dd if=testsystem.img of=/dev/block/mmcblk0

I thought this worked, so then I proceeded to try to install cyanogen rom. After many tries and other things to tedious to describe about what did not work, I finally got this version to work:


This version, and ones before it are for the SM-G9006V Chinese model, not my supposed international model. I tried to put in this version:


which should work for the SM-900F but it won't.

Now trying to put the phone back to its original state using

dd if=testsystem.img of=/dev/block/mmcblk0

does not work.

I think the phone was programmed somehow with two different ROMs, and I am hoping someone can tell me how to do this, or why I can't make dd command work?

Here is some more information before I did anything to the phone:

On Kies before changing to cyanogen rom it said it could not update the phone and reported the following:


Original answer to *#1234# before Cyanogen rom was:


Now this information cannot be gotten from KIES, and the *#1234# no longer works.

In addition, I wrote down all the following from the phone in its original state:

  • Device Name: Galaxy S5
  • Model Number: SM-G900F
  • Android Version 5.0
  • Broadband Version: G900FXXU1POEC
  • Kernel Version: 3-4.0-4884557 dpi@swdd5702 #1 Tue May 12 11:54:06 KST 2015
  • Build Number: LRX21t.G900FXXU1POEC
  • United Arab Emerates TRA ID:0016333/03 TP: 00000000/00
  • Security Software MDF V1.1 Release 4 VPN V1.4 Release 3
  • Knox Version Knox 2.3
    • Standard SDK 5.3.0
    • Premium SDK 2.3.0
    • Customization SDK 2.0.0
    • Container 2.3.0
    • IM 2.0.0
    • CEP 2.0.1
    • Enterprise Billing 1.0.0
    • SE for Android 2.2.1
    • SSO 2.1.1
    • TIMA 3.0
    • VPN 2.2.0

I want the phone to have a complete back up that is simple like using dd.

I want to use the phone in the US and Asia.

I would like to be able to put it back to its original ROM programming.

  • What does your IMG file contains? Where to mmcblk0 points? – Firelord Jan 19 '16 at 3:09
  • I don't understand the questions. Here is list of what I did: adb devices adb shell su cd.. ls cd storage ls cd extSdCard ls then the dd if=/dev/block/mmcblk0 of=testsystem.img – user146959 Jan 19 '16 at 4:26

Current Situation

  • I am afraid you have messed up things in a big way by flashing a ROM not meant for the device ,see this to get more understanding Can I install a ROM made for a different device?
  • Also surprised that you were actually able to successfully install CM meant for another device
  • I am not conversant with "dd" commands, but the probable reason it is not working now is that the partition information has been altered after flashing the wrong ROM
  • Samsung phones do not come with two ROMs as you are speculating based on Kies output. One remote possibility that strikes me is that this is a refurbished phone which had traces of earlier ROM (if that is possible ), leading to Kies reporting inability to upgrade. You can verify, if your phone is refurbished or not and also obtain more details about your phone, see my answer How can I tell if my phone is refurbished

Next Steps

  • At this juncture, trying to solve things on your own may cause more damage than help, so visit a service center to get it fixed. Leave it to the experts

  • If you still want to experiment, download correct stock ROM from Sammobile (requires registration) and flash stock using Odin as explained [Guide][Samsung] How to flash Stock ROM


  1. OP has confirmed that check by Phone Info Samsung shows it as refurbished. My guess is that the refurbishment was not properly done in terms of OS, leaving traces of earlier ROM as well. This could possibly disrupt attempt to restore to stock. This complicates situation further and strengthens my earlier recomendation to have the service center handle it. Of course, this does not stop OP from trying to flash stock ROM
  1. On Kies before changing to cyanogen rom it said it could not update the phone and reported the following:


factually reported by Kies, shows this, which is further confusing, either all the actions done by OP are not correctly reflected or there is an issue with refurbished phone

  • G900FXXU1POEC is UAE lollipop for your device

  • G9006VZNU1BOE3 is lollipop for SM-G9006V

  • G900FOJV1POF1 is lollipop UAE

  • Okay, what you're saying makes some sense, however it does not explain why it was already flashed with two different roms ...G900FXXU1POEC/G900FOJV1POF1/G9006VZNU1BOE3/G900FXXU1POEC (XSG) – user146959 Jan 19 '16 at 3:08
  • There is no refurbishment check on the Phone INFO Samsung I installed. – user146959 Jan 19 '16 at 3:20
  • I bought it from Amazon. Its being sold as an unlocked international phone model sm-G900f. – user146959 Jan 19 '16 at 3:38
  • figured out how to use phone INFO. it says refurbished, yet reports that the imei number is valid sm-g900f. which is believable? If its refurbished, why does it matter? Its the same hardware. at least thats what CPU-z says. – user146959 Jan 19 '16 at 3:56
  • I find it difficult to trust what apps are saying now, what am I to believe? Is the IMEi check online valid? I can understand why flashing roms might be done incorrectly, but why is ADB linux image not working to put it back into original state? Roms affect ADB? I do appreciate all the time you have spent trying to help me. – user146959 Jan 19 '16 at 4:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.