Odin fails at cm.bin while flashing Galaxy J710FN - General Questions and Answers

I was trying to flash Glaxy J710FN with stock ROM using Odin. But it fails at cm.bin and shows 'Complete write operation failed'. Please do help me with this.

I am facing the same issue, I've googled the problem and Its something to do with the wrong baseband version which cannot be downgraded.
I am on supernova ROM and want to switch to complete stock, unroot for warranty.
DId you find any solution?

jumbobombo said:
I am facing the same issue, I've googled the problem and Its something to do with the wrong baseband version which cannot be downgraded.
I am on supernova ROM and want to switch to complete stock, unroot for warranty.
DId you find any solution?
Click to expand...
Click to collapse
It has something to do with the USB cable, USB port and the installed driver versions. Update your driver to the latest version. Try using a different USB port, never use a USB hub. And that's it.

Jezwn said:
It has something to do with the USB cable, USB port and the installed driver versions. Update your driver to the latest version. Try using a different USB port, never use a USB hub. And that's it.
Click to expand...
Click to collapse
Also check whether you're trying to downgrade to a former version of Android which can't be done using Odin. Try getting the latest version of your stock ROM which you can Google yourself.

Thanks for your reply
I tried with different USB port but receiving same error.
Supernova custom ROM is on Android 6 and the firmware that I downloaded are also Android 6
I am completely clueless on how to solve this issue. I've been sitting and researching about this since 2 days now with no luck

jumbobombo said:
Thanks for your reply
I tried with different USB port but receiving same error.
Supernova custom ROM is on Android 6 and the firmware that I downloaded are also Android 6
I am completely clueless on how to solve this issue. I've been sitting and researching about this since 2 days now with no luck
Click to expand...
Click to collapse
You do have a J710FN right. Even though the downloaded one is Android 6 it has got variants as Samsung provides updations frequently. J710FXXU2APK6 is my current basaeband version. If I try to flash an update below this version it shows the same error. So do check your current version and try flashing an update above that.

Jezwn said:
You do have a J710FN right. Even though the downloaded one is Android 6 it has got variants as Samsung provides updations frequently. J710FXXU2APK6 is my current basaeband version. If I try to flash an update below this version it shows the same error. So do check your current version and try flashing an update above that.
Click to expand...
Click to collapse
Hey,
I tried a firmware of SM-J710F instead of SM-J710FN and odin worked.
I got official full stock ROM.
But issue is the boot screen when you first switch on the phone. It is still of the previous custom ROM Supernova. So it appears as "Samsung S8" Because of the custom ROM
Even though I flashed complete firmware through Odin the S8 did not return to stock
I am on complete stock with no root now
How to change the first boot image back to J7?
Thanks in advance

jumbobombo said:
Hey,
I tried a firmware of SM-J710F instead of SM-J710FN and odin worked.
I got official full stock ROM.
But issue is the boot screen when you first switch on the phone. It is still of the previous custom ROM Supernova. So it appears as "Samsung S8" Because of the custom ROM
Even though I flashed complete firmware through Odin the S8 did not return to stock
I am on complete stock with no root now
How to change the first boot image back to J7?
Thanks in advance
Click to expand...
Click to collapse
Are you sure you're on J710FN? The problem with the boot image would be that the ROM you're saying stock is a custom one with the S8 boot image. Try wiping all your data including David cache and flash the ROM again. If it's still the same root your phone and change the boot image.

Related

Kies not showing latest firmware...

Kies in my pc is just showing current firmware version for my tab(as well as for my phone).
It is not showing latest version as it shows conventionally.
So anyone knows fix for it???
I have tried uninstalling and then re installing latest version but still no luck...
Looking for some help asap
I am on stock,non rooted.
Any chance of showing a screenshot of what Kies shows you when your tablet is connected ?
uberNoobZA said:
Any chance of showing a screenshot of what Kies shows you when your tablet is connected ?
Click to expand...
Click to collapse
here is screen....
*i have internet connected.
Don't know why it's not working, sorry. if you have a custom ROM on the tablet, it might be that, or if the CSC on the tablet is not the original CSC (often caused by flashing ROMS, even 'stock' ROMs)
uberNoobZA said:
Don't know why it's not working, sorry. if you have a custom ROM on the tablet, it might be that, or if the CSC on the tablet is not the original CSC (often caused by flashing ROMS, even 'stock' ROMs)
Click to expand...
Click to collapse
No custom Rom.i am on stock and not rooted.
Problem is with latest version of kies.
I tried installing an previous version its displaying latest version without any issue...
Pls somebody help.
I tried installing older version of kies and its working fine.

Deleted my OS

Help i accidentally deleted my operating system on my Samsung Galaxy S6 SM-G920F
I have tried flashing the original firmware with odin but it always seems to fail the same way and says
NAND Write
FAIL!!
i have also tried flashing roms like Cyanogen 12 and a unofficial 13 version with TWRP which is installed but this always fails as well
I would really appreciate if someone could help i am quite desperate
luka1745 said:
Help i accidentally deleted my operating system on my Samsung Galaxy S6 SM-G920F
I have tried flashing the original firmware with odin but it always seems to fail the same way and says
NAND Write
FAIL!!
i have also tried flashing roms like Cyanogen 12 and a unofficial 13 version with TWRP which is installed but this always fails as well
I would really appreciate if someone could help i am quite desperate
Click to expand...
Click to collapse
Use latest Odin (v3.11.1)
try another USB port
Check the model number again
Always flash the latest firmware.
or you can try smart switch -> emergency recovery.
Just calm down, reboot PC, start everything from fresh and do not hurry!

S6 SM-G920f stuck on samsung logo after trying to install xposed framework

hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install

Galaxy s 7 flat no signal after root and custom room installation

i just rooted my phone and installed superstock rom with no problems in rooting or installing twrp and custom rom . but now i have no signal .simple solutions will not help i have no roaming in the setting . looks like the radio.img file is missing . any ideas how to fix it ????
Flash stock to make sure it's working first and it's not a phone issue
*Detection* said:
Flash stock to make sure it's working first and it's not a phone issue
Click to expand...
Click to collapse
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
jiries said:
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
Click to expand...
Click to collapse
Maybe IMEI blocked if stolen or contract not paid off, is it 2nd hand?
Did you try using different USB cables and USB ports?
The phone may have to be force flashed using different hardware such as an octopusbox.
audit13 said:
Did you try using different USB cables and USB ports?
The phone may have to be force flashed using different hardware such as an octopusbox.
Click to expand...
Click to collapse
is there any other solution other than the box ??
in older versions of android we had the possibility to put the radio.img and other simpler solutions .
Usually, flashing a complete stock ROM with Odin will flash everything together including the bootloader, baseband/modem, recovery, and system.
Post the Odin log as there may be something in there that can help resolve the issue.
jiries said:
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
Click to expand...
Click to collapse
Go to daveloper settings and enable OEM unlock
Now flash stock and latest firmware with odin
And use latest odin version
Sent from my [device_name] using XDA-Developers Legacy app
Try installing dev 5.6 roms from alexander...oem hould
*Detection* said:
Maybe IMEI blocked if stolen or contract not paid off, is it 2nd hand?
Click to expand...
Click to collapse
yes it is , but am pretty sure its not stolen , bought from mobile store was almost new when i got it .
i just managed to fix my phone (in phone store lab , probably they used the box).
last time i rooted the phone and then installed "noutfan " custom rom there was no problem with IMEI , signal or software issues , exept for many bugs in firmware and gear VR made the firmware collapse .
after this i installed superstock rom (without flashing bootloader or modem) i installed kernel and everything which was in the aroma installer ( its not the first time that i flash this rom . worked fine before last time) after installation last timei lost the imei and phone signal (before fixing the phone) .
i dont know what went wrong this time ,usually i install custom roms with no problem . now i have 7.0 stock rom (after fixing the phone) and i want to install custom rom but afraid of facing the same ptoblem .
Any ideas ?? what have i done wrong when i have installed superstock last time?? why i lost imei ?? how to avoid this problem when rooting and installing the custom rom ???

Help noob in trouble

Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
SABN said:
Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
Click to expand...
Click to collapse
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
LlamaQ said:
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
Click to expand...
Click to collapse
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
SABN said:
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
Click to expand...
Click to collapse
i have tried different versions of odin, different basebands but i keep getting the same results
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
jwoegerbauer said:
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
Click to expand...
Click to collapse
been there done that, originally it comes with a rom released in 2014 and the other one that is newer released in 2015 try with both just in case but I'm still stuck , reading about it I'm starting to believe it's a hardware problem

Categories

Resources