Related
Hi ,
My phone is soft-brocked and I can't get it back. Let me explain what happened, maybe you can suggest next course of action:
1- I tried to install KitKat official release via ODIN (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 version). Odin FAILED in the middle of the process, and got soft-bricked. When I turn the phone on now I get "Firmware upgrade encountered an issue. Please selecr recovery mode in Kies and try again" :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2- I tried to install previous Poland version, so that I could just perform an OTA update, and it also failed. Then I investigated further and realized my Note 3 is actually a model from Hong Kong (16GB) and seems to be the only version not compatible with other SM-N9005 firmwares.
3.- I found a version of the FW for this specific device (TGY-N9005ZHUDMK1-20131111204936) and tried to install it, then I got to a ext-4 error in Odin (again), unresolved)
4- I got a FW version for my phone with all files separate (N9005ZHUBMI7_China) and tried to upload individualy, I got everything but BL and AP
5- I tried with a forum suggesting to upload Bootloader from leaked KitKat version, and PI, AP, CP and CSC from Chinese version, that did not fix the problem
6.- Now, for any version I try to install I get this:
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> NON-HLOS.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried with ODIN 3.07 and 3.09. Results are exactly the same
7- I tried Kies and I get "The connected device is not supported by Kies 3 (I have the latest version)
8- In Kies, when I try to perform a "Firmware upgrade and initialization" after requesting Model and seial# I get "SM-N9005 does not support initialization"
9- I took my phone to the official Samsung Support in my country (argentina) and they said the model is not sold in Argentina, so there's nothing they can do
What do I have
1.- I can still access download mode and upload via Odin (works fine for CSC, CP and PIT, not for AP and BL)
2.- I can still access recovery mode (after installing CSC alone, the phone starts in recovery mode)
3- Fortunatelly, I have 2 batteries and an external charger, so no battery issues
I have ran out of ideas. Is there anyone around who can lend me a hand with this, please? I am desperate.
Thanks a lot!!!
Have a look at the procedure mentioned here..
http://forum.xda-developers.com/showthread.php?p=49527507
Edit: From the same thread-
* Is this Poland KitKat support Hong Kong N9005 - No, Hong Kong N9005 is not friendly with others country N9005, cannot cross flashing.
* What to do if I accidentally flash it under Hong Kong N9005 and soft brick now - The only solution now is flashing custom recovery (Knox trip due to custom recovery) for KitKat and later flash SweetROM v7 KitKat custom ROM.
Sent from my SM-N900 using Tapatalk
Same thing happened with mine, flashed Cwm with odin and it sprang to life...
Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
rinuvimal said:
This is for Hong Kong 16GB N9005 who were stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Many Thanks to @Volrath for his/her post in another forum with this solution. I have tried and it worked. I've tried almost every other solution without avail. So, this is probably the only solution available at the time I'm writing this post.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/showthread.php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/showthread.php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Click to expand...
Click to collapse
FeralFire said:
Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
Click to expand...
Click to collapse
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Try some other custom ROM. Try Echoe.
http://forum.xda-developers.com/showthread.php?t=2616103
Sent from my SM-N9005 using Tapatalk
con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Please delete. Wrong post.
i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m
uglybb88 said:
i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m
Click to expand...
Click to collapse
Do you have the 16gb or the 32gb hongkong version?
Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
is a 16gb
filchi756 said:
Do you have the 16gb or the 32gb hongkong version?
Click to expand...
Click to collapse
Question
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
maumarti2k said:
Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
Click to expand...
Click to collapse
Maybe I can help
fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Maybe I can help.
Please read my article at http://forum.xda-developers.com/showthread.php?p=49831876
fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Actually, I only got it to work with the version I mentioned in the post, I don't think I tried with the version you mention. If it failed, I'd suggest you start over, but this time try with the version I suggested, since at least I know this worked for 2 people already. Also, I believe you need to own a 16GB HK version, just in case, Hope this helps
Ask for Help
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
can not..............hix hix hix
working solution
Download and ODIN flash N9005ZHUENB5 in sam mobile. Works on my HK Note 3
minhluansgk said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
can not..............hix hix hix
Click to expand...
Click to collapse
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk
How about smart switch? Did you try flashing firmware from there?
icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I also heared that the very latest Odin will manage that issue.
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Sorry, I forgot to mention in that I've tried the option in the thread by Nameless no less than 4 times. I realized after I started my own post that I mentioned it not working on that thread instead.
sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
I've also tried various versions of Odin, 3.09, 3.10 and the latest 3.12 without success
sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
Nameless said:
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
Click to expand...
Click to collapse
Sorry, I forgot to mention in that I've tried the option in the thread by Nameless no less than 4 times. I realized after I started my own post that I mentioned it not working on that thread instead.
sayyro said:
I think it's the new Odin, try an older version
Also be sure to use the original cable , try USB 3.0 , 2.0, try a different cable , try a different USB host
I feel so sad for you man, the phone still new, it's not a good idea to root it before even trying it for the first time
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
I was using the original cable, thanks. I had gotten to use it for a day, but yeah, pretty dumb of me.
njdan30 said:
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I have not tried this yet but I will. I may have to wait until after work this evening. Never heard of modded Odin but just did a Google search. Thanks for the suggestion.
tasked28m said:
How about smart switch? Did you try flashing firmware from there?
Click to expand...
Click to collapse
Not yet. I saw it in another thread but didn't try it yet because I was too scared to be disappointed again. Yeah, I'm crazy. *embarrassed*
Will probably have to try it this evening after work.
Thanks for the reminder.
tasked28m said:
How about smart switch? Did you try flashing firmware from there?
Click to expand...
Click to collapse
I tried it and it wouldn't recognize the phone but when I put it in download mode, it said it was an unsupported device. According to the instructions it seems like you have to be able to at least boot your phone. Sigh
I really can't believe that I'm the only moron who hasn't been able to fix this issue. Everyone that's had it has fixed it. Must be operator error.
icydius said:
I just bought and received the unlocked S8+ Int'l version (955FD) yesterday. I'm not a newbie to rooting but I'm by no means advanced. I haven't had an unlocked phone in years and was anxious to root it. I tried using CF Root but afterward my phone got stuck on the black setup/title screen with the message "Recover is not SeeAndroid Enforcing." I realized after it was probably because I was already on the latest firmware version (it updated the same day I received the phone).
From this point I tried many things but everything I do in ODIN fails. I noticed that it says "there is no PIT partition" when I try to flash anything and for that reason it keeps failing. I even tried to install a PIT file as suggested here: https://forum.xda-developers.com/showthread.php?t=2659635 but with no success. I've searched on Google for hours and didn't find a way to resolve this issue yet (and I seem to be the only one in this spot).
How do I flash Odin files to get my phone working if there's no PIT which will prevent Odin from failing? UGH :crying:
Click to expand...
Click to collapse
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
drparvez said:
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
Click to expand...
Click to collapse
You received this message because your 64GB internal storage was corrupt. You have to reformat it.
njdan30 said:
Look for the newest modded version of Odin. I saw it over day try that
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
The only download I can find is here http://d-h.st/gsDA and it keeps giving me a time out error that the page took too long to long to respond.
Although I'm not convinced it will work, I'll be dumb and try it. Can you suggest some place to find an Odin mod?
drparvez said:
Hi
You are not the only one with this problem. I solved it when i root my phone.
First flash TWRP latest version using Odin.
Go to twrp recovery.
In recovery go to wipe option.
Select data and click on format
Change its type to Fat32 done
Again select data an format it in ext4 file type.
And last go back select wipe
Type yes
Ok
Then see in backup option
Is internal storage show its size or not if yes
Flash supersu zip file to root your phone.
And reboot
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
You received this message because your 64GB internal storage was corrupt. You have to reformat it.
Click to expand...
Click to collapse
I have tried flashing TWRP recovery yesterday twice as well but as everything else I did using ODIN, I got the FAIL after pressing START.
Are you saying I should reformat it before I flash TWRP because nothing works using ODIN? Anything I try to flash fails. Thanks
I'm running late for work so I'll check back later. Thanks for everyone's help so far!!
icydius said:
I have tried flashing TWRP recovery yesterday twice as well but as everything else I did using ODIN, I got the FAIL after pressing START.
Are you saying I should reformat it before I flash TWRP because nothing works using ODIN? Anything I try to flash fails. Thanks
Click to expand...
Click to collapse
Use this method to flash twrp
Go to download mode
Uncheck reboot option in odin
flash twrp file
Press 3 button combination to reboot it when it boot hold volume down bixby button to go download mode again tben flash the same file with uncheck reboot option in odin.
Flash twrp file boot it and again go to download mode.
Now this third time flash the file normally with reboot option.
Hope this will fix your issue.
Best of luck
Okay, so I'm home and was able to try this. I got the same results = FAIL. I think I should clarify what happened.
My S8+ was on the latest firmware (AQF7) and I didn't read enough to find out that CF Auto Root could only be used on the previous firmware. When I flashed CF Auto Root using ODIN and the phone rebooted, it got stuck on the S8+ title/boot which shows "Recovery is not Seandroid Enforcing."
Since then, I've tried to flash TWRP and all of the suggestions listed above (all but one I tried before I started this post) and ALL fail because ODIN said something about the PIT partition. Now it seems it doesn't mention the PIT partition since I'm using ODIN 3.12 but it still fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried flashing the previous firmware as well (see copied and pasted text) but again unsuccessfully.
icydius said:
Okay, so I'm home and was able to try this. I got the same results = FAIL. I think I should clarify what happened.
My S8+ was on the latest firmware (AQF7) and I didn't read enough to find out that CF Auto Root could only be used on the previous firmware. When I flashed CF Auto Root using ODIN and the phone rebooted, it got stuck on the S8+ title/boot which shows "Recovery is not Seandroid Enforcing."
Since then, I've tried to flash TWRP and all of the suggestions listed above (all but one I tried before I started this post) and ALL fail because ODIN said something about the PIT partition. Now it seems it doesn't mention the PIT partition since I'm using ODIN 3.12 but it still fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried flashing the previous firmware as well (see copied and pasted text) but again unsuccessfully.
Click to expand...
Click to collapse
Did you try my method flashing twrp 3 times without let your phone boot.
Try this.
Hi
Please it's possible back downgroad to marshmallow ?
stootie said:
Hi
Please it's possible back downgroad to marshmallow ?
Click to expand...
Click to collapse
Not as of now, as the bootloader has been updated on exynos variants in january update patch. If you haven't updated to january patch, you could downgrade using odin, but be sure to check repartition and select CSC in csc tab of odin, NOT THE CSC_HOME.
Sent from my S7 Edge using XDA Labs
Thanx for answer !
I don't update the patch january
shah22 said:
Not as of now, as the bootloader has been updated on exynos variants in january update patch. If you haven't updated to january patch, you could downgrade using odin, but be sure to check repartition and select CSC in csc tab of odin, NOT THE CSC_HOME.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Well, in theory it is. I just done it, after I upgraded to newest bootloader. The only thing is (at the moment) vibration does not work on Marshmallow. Everything else seems to be fine.
I'm surprised they would block downgrading with the january update patch.
Cholek3 said:
Well, in theory it is. I just done it, after I upgraded to newest bootloader. The only thing is (at the moment) vibration does not work on Marshmallow. Everything else seems to be fine.
Click to expand...
Click to collapse
were you able to flash old firmware after flashing the jan 2018 update..?if yes .how ? i tried everything was able to flash but the most of the system apps force closes and not able to use the phone .
saurabh808 said:
were you able to flash old firmware after flashing the jan 2018 update..?if yes .how ? i tried everything was able to flash but the most of the system apps force closes and not able to use the phone .
Click to expand...
Click to collapse
I flashed BL and CP (BTU) from newest firmware and AP and CSC from desired old firmware (BTU). In that case it was going back to MM. Aparat from no vibration, no other issues found.
i tried downgrading once ,, camera didnt work
No issue with camera here, at all.
so is there any way to downgrade after installing January security update?
TBS2002 said:
so is there any way to downgrade after installing January security update?
Click to expand...
Click to collapse
Read post #7
Cholek3 said:
Read post #7
Click to expand...
Click to collapse
after done lateraly what they say in #7 the devive refuse to boot and stays on the logo screen
so now what ? my device is 7 edge with model sm-g935f?
---------- Post added at 12:32 PM ---------- Previous post was at 12:24 PM ----------
Please anyone can you send me the marshmallow and nougat flash files for the model 7 edge sm-g935f M
TBS2002 said:
after done lateraly what they say in #7 the devive refuse to boot and stays on the logo screen
so now what ? my device is 7 edge with model sm-g935f?
---------- Post added at 12:32 PM ---------- Previous post was at 12:24 PM ----------
Please anyone can you send me the marshmallow and nougat flash files for the model 7 edge sm-g935f M
Click to expand...
Click to collapse
Just flash now newest firmware (all files) and make sure you use CSC files (not home_csc).
Cholek3 said:
Just flash now newest firmware (all files) and make sure you use CSC files (not home_csc).
Click to expand...
Click to collapse
I have made it and now we are at the point 0.
my phone is looked with FRP and the problem is that I have forgotten the last email and I want to open it ?also i have updeted it with January 2018 update accidentally
Frp lock lasts something between 24 and 72 hours. So you have to wait. In the meantime, you can try flashing again (BL and CP you just used, and AP and CSC, not home_csc, of old software of you desire).
Thanks for the guide I used it successfully to get to Marshmallow as I wanted to get the Galaxy Labs feature, I now want to get back to Nougat but when I use the automatic update it says that I am on the latest version.
Hey, i have a S7 Edge, but my issue is the same: odin.
I try to root S7 Edge, now my Wlan, my Camera doesn’t work and my screen is to half red.
Now i try to flash my phone to 6.0.1 with G935FXXU1BPLB
The driver of Smart Switch and Kies are installed, but deinstalled and the Driver Booster installed the last driver what i need.
On my Download Screen stay:
Produkt Name: SM-G935F
Current Binary: Custom
System Status: Custom
Fap Lock: OFF
Secure Download: Enabled
Warranty VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
SW REV, Check Fail. Device: 2. Binary: 1
Allte the same Odin v3.12 Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After i googled, someone says that i should do a factory reset, now my phone can start and the Bootloop is gone, but i have the same error like before.
Every times when i try to flash 6.0.1 i get the same error like above, what should i do ?
How can i fix my Camera Issue?
How i can flash Mashmellow and deinstall the false SuperSu version ?
No work for me
i tried it several times and always it stuck on boot.. And i can only enter download mode...
Maybe you have some idea??
I use:
NEW:
BL_G935FXXS2DRAA_CL12365438_QB16535167_REV00_user_low_ship.tar.md5
CP_G935FXXU2DRA9_CL648265_QB8671796_SIGNED.tar.md5
Old:
AP_G935FXXU1APAW_CL7042588_QB8405580_REV00_user_low_ship.tar.md5
CSC_OXX_G935FOXX1APB1_CL7114241_QB8433836_REV00_user_low_ship.tar.md5
Maybe it is something wrong with this file??
It's a mystery to me..
But flash custom rom MM over newest Nougat is possible? I reached max 2h40min with last update, battery is new, 3 full chargings. On MM battery life was much better ...
LE : After flashing SupermanROM V1.15.5 over stock rooted nougat, with last security patch from march(i think), vibration doesn't work and on "Always On Display" no icon for notifications.. I tried to flash BL and CP but not working .. I will try more next week ...
Cholek3 said:
No issue with camera here, at all.
Click to expand...
Click to collapse
I flashed as you said and it went well on Odin, but it wont boot from the galaxy edge logo. is there any solution for it?
Hi
My Phone is (was?) an SM-935T on Firmware G935TUVS4BRA1 unlocked by Tmobile.
Odin repeatedly freezes on "<ID:0/005> system.img.ext4" about 3/4 through the flash (freezes as in stops for hours. No movement in task manager either).
My steps are as follows:
1. Installed Samsung USB Drivers
2. Installed Samsung Tools into windows path
3. Downloaded G935TUVS4BRA1 firmware from Sammobile
4. Downloaded Odin 3.13.1 (see INI below)
5. Rebooted phone into Firmware update mode (Odin Mode)
6. Connect phone to PC
7. Run Odin as admin
8. Add BL, AP, CP, CSC files to Odin, all check OK (have also tried only adding BL and AP, and Only doing AP. Same Freeze)
8. Verified that Options haven't been changed from below INI
9. Click Start.
The process starts writing and gets to "<ID:0/005> system.img.ext4".
The progress bar gets to about 3/4 of the way and then hangs. (Hours and no progress)
I've tried with 3.12.3 Prince Comsy Version and 3.12.7 as well of Odin.
I made sure Developer mode was on, OEM Unlock was ON, & USB Debug mode was on before I started. I can't boot into anything now. I get the cyan "An error has occurred updating the device..." screen.
I've tried 2 different cables.
I tried using the Smart Switch software but it says SM-G935T does not support initialization.
Any suggestions?
Thanks!
Odin INI:
Code:
[Option]
Title=odindownloader.com
FactoryResetTime=1
OptionEnable=1
DeviceInfo=0
Warning=1
[APOption]
RePartition=0
AutoReboot=1
FResetTime=1
FlashLock=0
TFlash=0
NandErase=0
[CPOption]
PhoneEFSClear=0
PhoneBootUpdate=0k
[UIOption]
LED=0
[ButtonOption]
Bootloader=1
PDA=1
Phone=1
CSC=1
UMS/PATCH=1
Gmo21 said:
Hi
My Phone is (was?) an SM-935T on Firmware G935TUVS4BRA1 unlocked by Tmobile.
Odin repeatedly freezes on "<ID:0/005> system.img.ext4" about 3/4 through the flash (freezes as in stops for hours. No movement in task manager either).
My steps are as follows:
1. Installed Samsung USB Drivers
2. Installed Samsung Tools into windows path
3. Downloaded G935TUVS4BRA1 firmware from Sammobile
4. Downloaded Odin 3.13.1 (see INI below)
5. Rebooted phone into Firmware update mode (Odin Mode)
6. Connect phone to PC
7. Run Odin as admin
8. Add BL, AP, CP, CSC files to Odin, all check OK (have also tried only adding BL and AP, and Only doing AP. Same Freeze)
8. Verified that Options haven't been changed from below INI
9. Click Start.
The process starts writing and gets to "<ID:0/005> system.img.ext4".
The progress bar gets to about 3/4 of the way and then hangs. (Hours and no progress)
I've tried with 3.12.3 Prince Comsy Version and 3.12.7 as well of Odin.
I made sure Developer mode was on, OEM Unlock was ON, & USB Debug mode was on before I started. I can't boot into anything now. I get the cyan "An error has occurred updating the device..." screen.
I've tried 2 different cables.
I tried using the Smart Switch software but it says SM-G935T does not support initialization.
Any suggestions?
Thanks!
Odin INI:
Code:
[Option]
Title=odindownloader.com
FactoryResetTime=1
OptionEnable=1
DeviceInfo=0
Warning=1
[APOption]
RePartition=0
AutoReboot=1
FResetTime=1
FlashLock=0
TFlash=0
NandErase=0
[CPOption]
PhoneEFSClear=0
PhoneBootUpdate=0k
[UIOption]
LED=0
[ButtonOption]
Bootloader=1
PDA=1
Phone=1
CSC=1
UMS/PATCH=1
Click to expand...
Click to collapse
Have you tried the patched Odin versions? I noticed you are on Nougat with the firmware version you shared. Have you considered oreo? If you want to flash oreo firmwares (once in oreo you can't go back) use the patched v3.13.1 odin version attached. I think for Nougat you can use the other one I'm attaching (used it for MM and it worked flawlessly). I do remember that I got failed flashes in odin when I added the CSC file instead of the Home_CSC one(it will wipe all your data though). Good luck.
Mr. Clown said:
Have you tried the patched Odin versions? I noticed you are on Nougat with the firmware version you shared. Have you considered oreo? If you want to flash oreo firmwares (once in oreo you can't go back) use the patched v3.13.1 odin version attached. I think for Nougat you can use the other one I'm attaching (used it for MM and it worked flawlessly). I do remember that I got failed flashes in odin when I added the CSC file instead of the Home_CSC one(it will wipe all your data though). Good luck.
Click to expand...
Click to collapse
Switching to 3.13.1 Patched solved this for me. Thanks!
Gmo21 said:
Switching to 3.13.1 Patched solved this for me. Thanks!
Click to expand...
Click to collapse
Good to know it worked.
Hello
My Phone is (was?) an SM-935T now bricked Odin 3B Version 3.13 repeatedly fails.
My steps are as follows:
1. Installed Samsung USB Drivers
2. Installed Samsung Tools into windows path
3. Downloaded G935TUVU4CR12 firmware from Sammobile
4. Downloaded Odin 3B patched 3.13.1
5. Rebooted phone into Firmware update mode (Odin Mode)
6. Connect phone to PC
7. Run Odin as admin
8. Add BL, AP, CP, CSC files to Odin, all check OK (have also tried only adding BL and AP, and Only doing AP. Same Freeze)
8. Verified that Options haven't been changed from below INI
9. Click Start.
I made sure Developer mode was on, OEM Unlock was ON, & USB Debug mode was on before I started.
Part of the way through the cable got bumped and the process stopped
I can't boot into anything now. Boot loop
I've tried 2 different cables. One of my cables had a short and the process stopped part of the way, I tried to restart the process, but it fails very quickly. The phone fails when I try to put it into recovery mode and boot loops.
Here is what run looked like when I tried it again.
Odin INI:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1301)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 4560 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> emmc_appsboot.mbn
<ID:0/009> lksecapp.mbn
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm stucked into booting logo "Samsung" and i've only access to the download mode, where i tried everything i could find online: reinstall recovery, flash stock rom, and so on. From what i've find i suppose there is a problem about partitions so i even tried to flash .pit file, but Odin gets stucked at "SetupConnection" or "Initialzation" proccess. It takes forever, even for the recovery. I tried the emergency restore from Smart Switch but it cannot recognize my phone...
At the moment im writing (im trying another time to flash twrp), after 15 mins of initialzation now it's stucked on "Get PIT for mapping"...
Thanks in advace for any help.
Tick nand erase in odin and try again.
UsmaniMustafa said:
Tick nand erase in odin and try again.
Click to expand...
Click to collapse
I tried that already... I can try one more time but... But i'm hopeless to be honest. What should i flash while i tick nand erase?
Nekrux said:
I tried that already... I can try one more time but... But i'm hopeless to be honest. What should i flash while i tick nand erase?
Click to expand...
Click to collapse
Don't be hopeless. Bricking a phone tbh is not that easy.
Just find the latest firmware for your model on sammobile and then place the files in there respective slots. In the option check nand erase and re partition and flash. Hope this helps. https://forum.xda-developers.com/s7-edge/help/help-unbrick-s7edge-sm935w8-please-t3927240
This is a thread with someone having a similar problem.
Also try changing the cable your using and making sure on the latest odin or version 3.1. Also try different usb ports on your laptop.
UsmaniMustafa said:
Don't be hopeless. Bricking a phone tbh is not that easy.
Just find the latest firmware for your model on sammobile and then place the files in there respective slots. In the option check nand erase and re partition and flash. Hope this helps. https://forum.xda-developers.com/s7-edge/help/help-unbrick-s7edge-sm935w8-please-t3927240
This is a thread with someone having a similar problem.
Also try changing the cable your using and making sure on the latest odin or version 3.1. Also try different usb ports on your laptop.
Click to expand...
Click to collapse
This is the log...
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3993 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Nekrux said:
This is the log...
Click to expand...
Click to collapse
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?
Your firmware has to be an exact match otherwise it won't work, my advice is to download Sam firm to find out the exact match of your firmware, download the files suggested by sam firm and flash with the latest Odin.
UsmaniMustafa said:
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?
Click to expand...
Click to collapse
Nope, on screen i have only classical logo and this on the left upper corner:
Odin mode
Download speed: fast
Product name: SM-G935F
Current binary: Custom
System status: Official
Fap lock: Off
Secure download: Enabled
Warranty void: 1 (0x030c)
Rp Swrev: B:5 K:3 S:4
Shauqeen said:
Your firmware has to be an exact match otherwise it won't work, my advice is to download Sam firm to find out the exact match of your firmware, download the files suggested by sam firm and flash with the latest Odin.
Click to expand...
Click to collapse
I'm sure enough i'm flashin last and exact firmware. My model is S7 Edge Italy no brand. Thats the file i've downloaded: G935FXXS5ESF6_G935FITV5ESF6_ITV.zip.
UsmaniMustafa said:
Can't open the file. Maybe the download is corrupted. Re download and also try without pit file. One more thing you can try is just put AP in odin and leave everything else blank and try.
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Any error on the phone screen?
Click to expand...
Click to collapse
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3921 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 43 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...
Nekrux said:
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...
Click to expand...
Click to collapse
Before trying all this I'm assuming you enabled OEM Unlock in developer settings, if so try to flash twrp. Maybe that will give you access and from there ypu can flash a custom rom
UsmaniMustafa said:
Before trying all this I'm assuming you enabled OEM Unlock in developer settings, if so try to flash twrp. Maybe that will give you access and from there ypu can flash a custom rom
Click to expand...
Click to collapse
Twrp is flashed in recovery.img partition. I am afraid he will receive same error because Odin would try to open PIT file for recovery flashing. If there isn't any user error then the phone can only be fixed by AnyWay box.
Nisar Ahmed Nisar said:
Twrp is flashed in recovery.img partition. I am afraid he will receive same error because Odin would try to open PIT file for recovery flashing. If there isn't any user error then the phone can only be fixed by AnyWay box.
Click to expand...
Click to collapse
What is user error? I assume it's kinda errors should appear on phone screen like UsmaniMustafa asked me before. Also i suppose AnyWay Box is a tool that only Samsung customers service or some tricky people have.
Nekrux said:
I tried by setting only AP with nand erase and re-partition, after re-downloading firmware from SamMobile. No pit file at all [as well last time] and i get that error again:
Now i'm trying to download the firmware also from Updato
Edit:
Updato keeps aborting the firmware download. I used SamFirm but files inside are the same of the Sammobile archive.
Anyway while trying to flash PIT file yesterday or two days ago i got this error tho:
I've searched a bit online but nothing works... I gonna buy new phone i guess. I'm sad cause i wanted a Pixel or a Xiaomi but i have to get a Samsung since my things are all backed up on their cloud.
A little vent: i'm not that expert at modding or coding or whatever, but i always liked to mod my old Nexus 5. It served me for years and i never had hard things to do, or dangerous situations or critical bricks/unsolvable problems. Now first time i put hands on my S7 Edge [i waited warranty's end]... This...
Click to expand...
Click to collapse
A few things to check, Odin version and binary numbers of firmware you're trying to flash vs your current binary number. If trying to flash oreo software ensure you are using Odin 3.13.1.
Aimless Rambler said:
A few things to check, Odin version and binary numbers of firmware you're trying to flash vs your current binary number. If trying to flash oreo software ensure you are using Odin 3.13.1.
Click to expand...
Click to collapse
I started with Odin 3.13.1, later i even tried 3.12.7 since i've read something somewhere... I don't remember. How do i get my current binary number? I cannot access to anything but download mode...
Nekrux said:
I started with Odin 3.13.1, later i even tried 3.12.7 since i've read something somewhere... I don't remember. How do i get my current binary number? I cannot access to anything but download mode...
Click to expand...
Click to collapse
In a previous post you noted that you have this "Rp Swrev: B:5 K:3 S:4" in download mode. The B:5 = Binary 5, you would need to match the binary number against firmware you intend to flash in Odin. For example, for the following firmware G935XXXX9CSC2, counting from right to left the 5th number would be the binary number. In the example it is '9'. In your case you would need Binary 5 firmware. If you have downloaded the correct binary firmware and it has still failed to flash you may need to try a different version of Odin (if firmware is Android Oreo, Odin 3.13.1 is needed due to lz4 format). You may need to flash incrementally, please see the link below and follow suggestion as posted in my italicized text below.
In Odin v3.13 U must add all 4 files (BL,AP,CP,CSC)
And in PIT tab you must add pit file
In options you apply Re-Partition, Auto Reboot, F. Reset Time
Click Start
https://www.sammobile.com/forum/threads/40890-Odin-error-(can-t-open-the-specified-file-)-line-1892
Further suggestions:
If flash fails add USERDATA Home CSC in slot
If flash fail ... add all except CP
Forgot to mention the obvious ... make sure you are using OEM USB cable.
Redownload the firmware files, I think they are corrupt.
Redowmload odin 3.13.1 (only this version works with oreo firmwares)
Redownload italy's bootloader 5 firmware.
Don't use pit file.
Don't check repartition.
Don't check nand erase.
(All these options are useless and won't do any good (if not bad) on s7 edge)
To explain : pit file is already in csc md5, no need to extract and do pit mapping again..
Nand erase was a dangerous option only used for older samsung phones to repair hard bricked phones in samsung service centers. It erases all the nv data like imei / serial no. and even the download mode (accordingly on old samsung phones). This option is obsolete on latest samsung phones which are hard coded to not delete nv data and download mode etc so this option does nothing in new phones, also internal memory gets erased when csc.md5 is flashed !
Repartition option is useless too, as csc.md5 file repartitions automatically.
(Repartition option's only use is that when people want to upgrade from a previous android version WITHOUT losing data, they can select HOME_CSC.md5 while flashing the newer firmware and repartition box checked, I don't know if it works correctly..)
Just select auto reboot and F.reset timer in odin options.
If still it throws some error then phone's internal memory got some hardware problem.
Sent from my S7 Edge using XDA Labs
shah22 said:
To explain : pit file is already in csc md5, no need to extract and do pit mapping again..
Nand erase was a dangerous option only used for older samsung phones to repair hard bricked phones in samsung service centers. It erases all the nv data like imei / serial no. and even the download mode (accordingly on old samsung phones). This option is obsolete on latest samsung phones which are hard coded to not delete nv data and download mode etc so this option does nothing in new phones, also internal memory gets erased when csc.md5 is flashed !
Repartition option is useless too, as csc.md5 file repartitions automatically.
(Repartition option's only use is that when people want to upgrade from a previous android version WITHOUT using data, they can select HOME_CSC.md5 while flashing the newer firmware and repartition box checked, I don't know if it works correctly..)
Just select auto reboot and F.reset timer in odin options.
If still it throws some error then phone's internal memory got some hardware problem.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Good information, if OP isn't thanking you I will. I'm an old time Samsung fanboy but there's been a slight break in time for me and things seem to change.
Stuck in Samsung Logo Screen. Recovery Mode not loading. FRP Lock on
Suddenly My phone stopped working. Stuck in samsung logo screen . cannot enter recovery mode. I have only option is to use odin to install software. have downloaded files from sammobile site. Always stuck in initialisation for 30 min and then proceed and fails at re partition operation failed. tried to install twrp . download was halfway and stopped because of FRP Lock ON. How to proceed .. Pls help me..
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
Aimless Rambler said:
Good information, if OP isn't thanking you I will. I'm an old time Samsung fanboy but there's been a slight break in time for me and things seem to change.
Click to expand...
Click to collapse
Suddenly My phone stopped working. Stuck in samsung logo screen . cannot enter recovery mode. I have only option is to use odin to install software. have downloaded files from sammobile site. Always stuck in initialisation for 30 min and then proceed and fails at re partition operation failed. tried to install twrp . download was halfway and stopped because of FRP Lock ON. How to proceed .. Pls help me..
Use 7zip to extract the CSC file from the firmware you downloaded from sammobile. After extraction you'll find the PIT file in the folder.
Start Odin 3.14
Go to options tab and enable re-partition and nand erase
Go to pit tab
Click on pit and select the pit file you extracted from the firmware
Now preload the BL, AP, CP and CSC md5 files
Click start and wait
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
And for removing FRP lock the easiest way of doing this is by using a tool named FRP HiJacker by Hagard