Database Info

Please help, gsr is bricked!

So yesterday i have flashed the pacman custom rom via CWM and it works fine.
However, I cant play a game that requires unroot, so I decided to flash it back to the ICS
From that, I tried to flash a OFFICIAL ICS ROM I9103ZCLPD via Odin, however, it stuck on flashing the file "Factoryfs.IMG"
so I decided to flash another OFFICIAL GB ROM I9103ZSLE5, but same problem.
Now, my phone can enter recovery mode and download mode
What should I do? Please help!

Maze=] said:
So yesterday i have flashed the pacman custom rom via CWM and it works fine.
However, I cant play a game that requires unroot, so I decided to flash it back to the ICS
From that, I tried to flash a OFFICIAL ICS ROM I9103ZCLPD via Odin, however, it stuck on flashing the file "Factoryfs.IMG"
so I decided to flash another OFFICIAL GB ROM I9103ZSLE5, but same problem.
Now, my phone can enter recovery mode and download mode
What should I do? Please help!
Click to expand...
Click to collapse
try this one -> http://forum.xda-developers.com/showthread.php?t=1706572

kataria.vikesh said:
try this one -> http://forum.xda-developers.com/showthread.php?t=1706572
Click to expand...
Click to collapse
OK, will try now and update afterwards

UPDATE : so I have tried to do a Re-Partition with the ICS ROM , bad news is it stucks on the same file again but it stucks on a further progress %.
What should I do now?
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> factoryfs.img
<ID:0/004> __XmitData_Read ..
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Maze=] said:
UPDATE : so I have tried to do a Re-Partition with the ICS ROM , bad news is it stucks on the same file again but it stucks on a further progress %.
What should I do now?
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> factoryfs.img
<ID:0/004> __XmitData_Read ..
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried this..??
NOTE FOR ICS USERS.
This unbricking tool is working on ICS also. but after this tool completes flashing u wont be able to flash stock ROM via odin directly to solve this u have to do a lil change in process.
after unbricking tool completes flashing, remove usb cable and reboot ur phone. phone will automatically boot in download mod as its not having OS.
now open odin, plug in ur device and flash ur desired stock ROM.
(thanks to UnknownzD for finding this solution.)
Click to expand...
Click to collapse

kataria.vikesh said:
Have you tried this..??
Click to expand...
Click to collapse
omg, maybe i am too nervous i forgot to read that, so should i restart my phone now and do the whole progress again?
odin has stopped already.

Use Odin v3.07
Sent from my CM10.1-powered GT-I9103

Maze=] said:
omg, maybe i am too nervous i forgot to read that, so should i restart my phone now and do the whole progress again?
odin has stopped already.
Click to expand...
Click to collapse
Its OK buddy. But dont panic. Let read process fully. Your Phone is not bricked fully but your nervousness can make it Paper weight.

kataria.vikesh said:
Its OK buddy. But dont panic. Let read process fully. Your Phone is not bricked fully but your nervousness can make it Paper weight.
Click to expand...
Click to collapse
Do I have to do the re-partition in odin if I want to flash ICS rom?

Maze=] said:
Do I have to do the re-partition in odin if I want to flash ICS rom?
Click to expand...
Click to collapse
now it time to read the most dangerous part of it, read this:
This method is dangerous as it will format the whole system and all the partitions on your phone. this will also format ur EFS partition so if ur using this tut for downgrading bootloader than its strongly warned that u backup ur EFS folder otherwise u will loose ur IMEI number.
this whole process will wipe ur internal sd card, there is no way to recover/backup it as in bricked phone u cant mount ur storage.
if u have 2.1 bootloader and want to downgrade it to v2.0 so that u can use usb jig to reset binary counter u can use this method but this method is risky so its recommended to backup all ur data and specially EFS folder to save ur IMEI number.
if u r on bootloader 2.0 and dont have usb jig and u want to reset ur download counter than u can use this method but as this method is risky so better buy usb jig and use it. use this as a last option. and dont forget to backup EFS and SD card otherwise u will loose ur IMEI and data stored on SD card.
Click to expand...
Click to collapse

kataria.vikesh said:
now it time to read the most dangerous part of it, read this:
Click to expand...
Click to collapse
Thanks for your help and encouragement, I have now able to turn on my device on GB ROM now, hurray!
Luckily, I dont know why my device has recognized my IMEI, but I didn't do any backup before.
But I wonder, should I update to ICS by kies or Odin now?
BIG THANKS!

UPDATE : It seems that my device can't be updated to the ICS, I have tried two different roms but it stucks in factoryfs.img but in different progress % again. What does this mean?

UPDATE: It seems that is the unzip program having the problem, my device is now alive on the ICS
Big thank you to everyone for assisting a beginner like me!

Maze=] said:
UPDATE: It seems that is the unzip program having the problem, my device is now alive on the ICS
Big thank you to everyone for assisting a beginner like me!
Click to expand...
Click to collapse
Glad to see that your phone finally having ICS. :cyclops:
BTW, there is Thanks button which can be pressed if you like anybody work in XDA..

[Q] I9103r doesnt want Rooted in Odin?Please Help

I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all

I9103-junior said:
I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all
Click to expand...
Click to collapse
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™

Could you post Odin screen shot with all details how you are flashing...
Sent from my Nexus 4 using Tapatalk 2

screen shot from Odin
Hi
I attach an image from Odin. Any other suggestions welcomed.
Thanks
Peter

Disturbed™ said:
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™
Click to expand...
Click to collapse
Hi
I removed the Kies from Windows, because it seemed to me that it can cause conflict when I''m starting flash my phone.But unfortunately, problem is the same.
Where I can find "follow soft brick tutorial". and what is it used for.
Thanks at all

If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.

Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
what a catch. we must have reading habits.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using XDA Premium 4
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™

Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?. Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:

I9103-junior said:
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?.
Click to expand...
Click to collapse
No you can flash different versions also. Since you installed CWM v4.0.0.2, now onwards download flashable zip file of other recoveries and flash them.
Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:
Click to expand...
Click to collapse
Visit [INDEX] Custom ROM/Kernel/MOD/Guide/Tool
links to various Roms are given there and instructions are given in respective Rom's OP.
Happy Flashing..

Galaxy SM-J700P - wont' boot after loading Superuser

Just trying to root. Everything went fine until I loaded Superuser. Now, upon reboot, I get the Samsung logo, then the Virgin mobile animation, but it hangs there. I can get into TWRP, I can get into DL mode. Not sure what to try next.
I was reading to maybe flash the stock tar? Should I do that before I go and try custom?

Gamestress said:
Just trying to root. Everything went fine until I loaded Superuser. Now, upon reboot, I get the Samsung logo, then the Virgin mobile animation, but it hangs there. I can get into TWRP, I can get into DL mode. Not sure what to try next.
I was reading to maybe flash the stock tar? Should I do that before I go and try custom?
Click to expand...
Click to collapse
Flash stock recovery

Don't panic, happens all the time
Just take a logcat and post it up here..
As the user above me said, don't flash stock recovery, it would most probably be flashing a stock firmware

http://forum.xda-developers.com/galaxy-j7/development/samsung-stock-recovery-700p-read-t3454061
Follow instructions to fix bootloop
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
believe it or not i made this to fix the bootloop into TWRP.... apparently TWRP bugs the phone to keep booting into recovery

Still hanging
Ugh.. got the file, extracted.. under BL.. ran fine, up top says PASS. Still hanging at the VM animation.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
EDIT.. oh wait do I do a factory reset after then?

UPdate hah
Ok, I'm at least in to the phone again after doing this:
http://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
^^^^^^^^^^^^^^^^^^^^^^^^^^ worked! ^^^^^^^^^^^^^^^^^^^^^^^^^^^
It's taking me thru set up again, so not sure if I'm actually rooted. But at least I dont have a brick, .... yet.
OK, DL'd a root checker..and Congratulations! Root access is properly installed on this device!
Whew!

SykkNyzz said:
http://forum.xda-developers.com/galaxy-j7/development/samsung-stock-recovery-700p-read-t3454061
Follow instructions to fix bootloop
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
believe it or not i made this to fix the bootloop into TWRP.... apparently TWRP bugs the phone to keep booting into recovery
Click to expand...
Click to collapse
My Phone model is SM-J700H/DS.
the phone is not booting after flash SuperSU.
i do get in TWRP and Downloading Mode.
will this solution will fix it ?

Are you on marshmallow? Which version of SuperSu have you flashed?
Sent from my SM-J700F using XDA-Developers mobile app

dodo2244 said:
Are you on marshmallow? Which version of SuperSu have you flashed?
Sent from my SM-J700F using XDA-Developers mobile app
Click to expand...
Click to collapse
this version :
UPDATE-SuperSU-v2.46.zip
android 6.0.1 (marshmallow)
BuildNumber : MMB29K.J700HXXU2BPG4

iTaisHi said:
My Phone model is SM-J700H/DS.
the phone is not booting after flash SuperSU.
i do get in TWRP and Downloading Mode.
will this solution will fix it ?
Click to expand...
Click to collapse
You need to find the device version for your stock recovery. In theory it will work, but since I only own j700p that method fixed my bootloop back then for only constantly booting back to TWRP. They recently fixed that error for ours with rebooting in the TWRP program.

SykkNyzz said:
You need to find the device version for your stock recovery. In theory it will work, but since I only own j700p that method fixed my bootloop back then for only constantly booting back to TWRP. They recently fixed that error for ours with rebooting in the TWRP program.
Click to expand...
Click to collapse
thanks SykkNyzz and Dodo,
Problem Solved,
i had falshed the wront SuperSU version.
falshed again v2.68 and that solve the problem.
i took it from here:
http://rootmygalaxy.net/flash-supersu-using-twrp-recovery-root-any-android-device/

Bravo!
Sent from my SM-J700F using XDA-Developers mobile app

SoNiC_bOoM15 said:
Just take a logcat and post it up here..
As the user above me said, don't flash stock recovery, it would most probably be flashing a stock firmware
Click to expand...
Click to collapse
Bro, with whom are u messing with ? see his thanks meter

SykkNyzz said:
They recently fixed that error for ours with rebooting in the TWRP program.
Click to expand...
Click to collapse
Who fixed the error, Teamwin? Is there a commit?

ashyx said:
Who fixed the error, Teamwin? Is there a commit?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 @Starchild2k did.

SykkNyzz said:
http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 @Starchild2k did.
Click to expand...
Click to collapse
I'm not sure what you're pointing me to as I don't see a reference to it in that thread?

The fixed TWRP that doesn't cause an issue in j700P

SykkNyzz said:
The fixed TWRP that doesn't cause an issue in j700P
Click to expand...
Click to collapse
We must be referring to different issues. Thanks anyway.

download the original 6.0 firmware of the j7 and flash it with the help of odin

First flash the original firmware of j700f download it from sam mobiles website,the again install the twrp file as flashing firmware remove it. Then download the super su file from the given link and only download if u have j700f or otherwise it might brick again
https://bitbucket.org/Serverbee/downloadbee/downloads/BETA-SuperSU-v2.74-2-20160519174328.zip

SM-G930W8 help

hello,
today i received a s7 unlock from ebay, but when i insert my sim card not show nothing, If i go to * # 06 # show me only the serial, if i go under the settings, the imei and baseband show by unknow.. I've seen the phone is already rooted
any solution??
thanks

caccolino said:
hello,
today i received a s7 unlock from ebay, but when i insert my sim card not show nothing, If i go to * # 06 # show me only the serial, if i go under the settings, the imei and baseband show by unknow.. I've seen the phone is already rooted
any solution??
thanks
Click to expand...
Click to collapse
Hi mate
What firmware is installed , what about the recovery , how does it look like?
Install an app like PhoneInfo
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=es
It will give you all information need , Imei , processor type ...if is original

flash with odin latest firmware available for your model, if problem won't be solved this way check in settings, about baseband version, if unknown it means you may have some hardware issues

AntonPres said:
flash with odin latest firmware available for your model, if problem won't be solved this way check in settings, about baseband version, if unknown it means you may have some hardware issues
Click to expand...
Click to collapse
MAX 404 said:
Hi mate
What firmware is installed , what about the recovery , how does it look like?
Install an app like PhoneInfo
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=es
It will give you all information need , Imei , processor type ...if is original
Click to expand...
Click to collapse
now i have a big problem, i try to update with smart swith but not work, after install boot only in recovery...

caccolino said:
now i have a big problem, i try to update with smart swith but not work, after install boot only in recovery...
Click to expand...
Click to collapse
Can you post a picture of your recovery??
Can you get into download mode??

MAX 404 said:
Can you post a picture of your recovery??
Can you get into download mode??
Click to expand...
Click to collapse
I can get into download mode,
in recovery I get these message..( no support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code: 0x02)

MAX 404 said:
Can you post a picture of your recovery??
Can you get into download mode??
Click to expand...
Click to collapse
caccolino said:
I can get into download mode,
in recovery I get these message..( no support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code: 0x02)
Click to expand...
Click to collapse
now try to flash stock with odin, but same error...
(odin log)(<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> modem_debug.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0))
screen recovery( i try to wipe data/factory reset and wipe cache partition but nothing)
http://imgur.com/a/9PB7A

did it came with a box? then you might wanna try to flash the stock rom via samsung kies and if that doesn't work then ask for a refund because the phone seems bugged.

caccolino said:
now try to flash stock with odin, but same error...
(odin log)(<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> ]
Click to expand...
Click to collapse
Ok, what files did you use?

MAX 404 said:
Ok, what files did you use?
Click to expand...
Click to collapse
G930W8VLU2BQB6_G930W8OYA2BQB6_XAC with all 4 file inside

MAX 404 said:
Ok, what files did you use?
Click to expand...
Click to collapse
when odin finish the phone reboot and show installing system 32% and erasing, rebooting and show image with no command, and rebooting alone and go to android recovery...

caccolino said:
G930W8VLU2BQB6_G930W8OYA2BQB6_XAC with all 4 file
Click to expand...
Click to collapse
there are 5 files , did you use CSC or home_csc...anyhow
Flash again use CSC file , this has a PIT and will re partition all partition..
Follow instructions here
https://www.sammobile.com/forum/showthread.php?t=30800

MAX 404 said:
Ok, what files did you use?
Click to expand...
Click to collapse
MAX 404 said:
there are 5 files , did you use CSC or home_csc...anyhow
Flash again use CSC file , this has a PIT and will re partition all partition..
Follow instructions here
https://www.sammobile.com/forum/showthread.php?t=30800
Click to expand...
Click to collapse
ok now try to follow the instruction howenever i use csc file not home csc

caccolino said:
ok now try to follow the instruction howenever i use csc file not home csc
Click to expand...
Click to collapse
Try that , home_csc will not reset-format your phone CSC will.....lets see if it helps
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
caccolino said:
ok now try to follow the instruction howenever i use csc file not home csc
Click to expand...
Click to collapse
Make sure you set re-partition as option under PIT
And use latest Odin

MAX 404 said:
Try that , home_csc will not reset-format your phone CSC will.....lets see if it helps
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
Make sure you set re-partition as option under PIT
And use latest Odin
Click to expand...
Click to collapse
ok i select re-partition and reflesh, but nothing same problem, reboot in recovery

MAX 404 said:
Try that , home_csc will not reset-format your phone CSC will.....lets see if it helps
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
Make sure you set re-partition as option under PIT
And use latest Odin
Click to expand...
Click to collapse
caccolino said:
ok i select re-partition and reflesh, but nothing same problem, reboot in recovery
Click to expand...
Click to collapse
Ok, I do not know what I did but I managed to get into the phone .. i installed the twrp then fleshato root and no-verity-opt-encrypt-5.1 ..

caccolino said:
ok i select re-partition and reflesh, but nothing same problem, reboot in recovery
Click to expand...
Click to collapse
Odd...
As long as the device was already rooted , lets try something else
Flash a custom recovery and root it
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
then try to flash a custom rom like
https://forum.xda-developers.com/galaxy-s7/development/rom-superstoc-rom-v1-0-aroma-t3496520

i want to know you one question it's possible to add language?? have only english and chinese, im italian..

caccolino said:
i want to know you one question it's possible to add language?? have only english and chinese, im italian..
Click to expand...
Click to collapse
No unless is on the firmware or in the custom rom
But i am confused what happened? what did you do? now your phones boots

yes now boot, i flash twrp with odin and on twrp flash root and no-verity-opt-encrypt-5.1 .. and the phone magical boot

Help please

I wanted to install the stock firmware on my galaxy j7 but when I try to flash it with odin I get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplag the cable..
<OSM> Please wait..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialization..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bim
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me?
The model is j710fn (2016)

@r4d0n7 have you verified hash of md5 to be sure it didn't get corrupted during download.. you could try removing the ".md5" so it's just a ".tar" an extract with winrar or 7zip to see if any errors occur you can try flashing without the ".md5" also just flash the tar file otherwise it could be corrupted make sure you download from a reliable source.. use a download manager also. Maybe your partitions got jacked up over time and there not matching when verifying may have to flash a .pit file also
Sent from my LGLS676 using Tapatalk

rick.wardenburg said:
@r4d0n7 have you verified hash of md5 to be sure it didn't get corrupted during download.. you could try removing the ".md5" so it's just a ".tar" an extract with winrar or 7zip to see if any errors occur you can try flashing without the ".md5"
Click to expand...
Click to collapse
Well, I tried what you said so: renaming the .md5 into .tar or just removing the .md5 and letting only .tar. Still I get the same result and on my downloading mode console in my phone I'm getting: SECURE CHECK FAIL: (BOOTLOADER) I tried different firmwares to download... Same result. I tried flashing a custom recovery and it works. This means it's not anything from the drivers.
rick.wardenburg said:
also just flash the tar file otherwise it could be corrupted make sure you download from a reliable source.. use a download manager also. Maybe your partitions got jacked up over time and there not matching when verifying may have to flash a .pit file also.
Click to expand...
Click to collapse
I downloaded the last .tar version from samsung-firmwares.org for j710fn but still no fix... I'm sure it may be from my partitions. If it is, then tell me how can i fix them up?

That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
---------- Post added at 10:13 AM ---------- Previous post was at 09:55 AM ----------
Try loading the firmware in all 4 slots of Odin and flashing, you could always extract the tar and make the 4 file flash seems to work a lot also you can get your PIT from twrp by typing in twrp terminal
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
flash with stock rom if it throws an error about ext4 you'll have to get a PIT from someone with same device an storage capacity
Sent from my LGLS676 using Tapatalk

rick.wardenburg said:
That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
Click to expand...
Click to collapse
Well, I saw different baseband versions for each firmware. I don't know how can I find my baseband version if my OS is wiped and can't check whatever information needed for it so I can get the correct firmware for it.

rick.wardenburg said:
That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
---------- Post added at 10:13 AM ---------- Previous post was at 09:55 AM ----------
Try loading the firmware in all 4 slots of Odin and flashing, you could always extract the tar and make the 4 file flash seems to work a lot also you can get your PIT from twrp by typing in twrp terminal
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
flash with stock rom if it throws an error about ext4 you'll have to get a PIT from someone with same device an storage capacity
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
Nope buddy its not device issue he is downloading wrong firmwares
Dont use sammobile
Its mixed all
Just move to updato.com
And install its firmware
U will pass odin all

Oves786 said:
Nope buddy its not device issue he is downloading wrong firmwares
Dont use sammobile
Its mixed all
Just move to updato.com
And install its firmware
U will pass odin all
Click to expand...
Click to collapse
I'm assuming he has right firmware flashing some ROMs and then Odin factory firmware will cause this also
Sent from my LGLS676 using Tapatalk

rick.wardenburg said:
I'm assuming he has right firmware flashing some ROMs and then Odin factory firmware will cause this also
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
nope he downloaded the j710fn firmware from sammobile and samshung has 2 models named j710fn like on8 and j7 2016 so the firmwares are mixed on sammobie an the on8 firmware says cm.bin fail on j7 2016
and updato.co firmware works on j7 2016 so firmware is the issue
i also hadthat issue i too hav j7 2016

Well, thank you everybody for trying to help me out but I already got a custom rom in which works with the phone really nice, and sorry for bumping the topic.