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
Hello everyone,
I'm trying to flash a stock rom on a Verizon GS5. I say trying because so far it hasn't been working, unless I'm doing something wrong, which I think I am. When I got the phone, it had a Sprint rom flashed to the GS5. The original Verizon IMEI under the battery is clean and verified good with Verizon. There is nothing physically or cosmetically wrong with the phone, it powers on sometimes and randomly restarts. When it does turn on, the Sprint Spark logo comes up, the phone boots up normally and then randomly shuts off, taking a long time to be able to power back on. The only way that it says on is by putting it on Download Mode.
When in download mode, it shows as a G900P,
As far as my understanding goes, shouldn't it be a G900V?
I attempted to flash a stock Verizon rom I downloaded and tried to flash it with Odin 3.04 but it fails each and every time. I have installed the Samsung drivers that I got from the website, I restarted the computer, I restarted the phone but Odin give me a fail error.
Then I tried a newer version of Odin 4.43 but I'm not sure I'm using that one correctly but it's not working for me either.
I left the phone in Download Mode and it has been on for about 30 mins (the longest so far without it restarting on me).
Is there something that I'm missing here? Something else I could try to fix this?
Any ideas? Suggestions?
Any help would be greatly appreciated!!
..
-> It's a Verizon Galaxy S5 Phone I got from eBay
-> It's flashed with the Sprint rom version of the GS5
-> The phone restarts on and off, randomly, unless it is in Download Mode
-> I want to flash it back to the original Verizon GS5 rom.
-> I attempted to flash the phone with Odin 3.09 and rom SM-G900V_VZW_1_20140331185350
-> I get an error message when using Odin 3.09, it FAILS
-> The progress bar in the GS5 phone advances a small amount but that's it.
-> I attempted to use Odin 4.43 with the same rom file but that also fails and I get an error message.
-> I researched on Google before signing up and asking for help.
-> I have read many Threads and Posts on several Forums, and I have also tried many tutorials without any luck.
-> I researched how to use Odin, there is lot's of pictures, easy explanations but that's not it.
-> I found a GS5 stock rom, file name mentioned above.
-> Samsung drivers are installed, phone is recognized by Odin.
1.) Am I using the correct rom?
2.) Which version of Odin should I use?
..
SewerDweller said:
Hello everyone,
Any ideas? Suggestions?
Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Download this version of Odin and extract the folder in the zip.
Make sure you have downloaded the correct firmware, extract the MD5 / tar file from inside the firmware.zip file you downloaded and put it in the Odin 3.07 folder
Start Odin.exe, put your phone in download mode and connect to your PC, if you have Kies installed make sure it is not running, Odin and Kies don't mix.
Once you have the Blue ID.COM indicated, click on PDA, find the MD5 / .tar file wait for teh file check Odin runs then click Start, wait for Odin to finish and your phone reboots.
Guide for Odin use here it is from the S3 but the use of Odin is the same for the S5
It took me a while to get it to turn on but here's what I got from trying ag4751's suggestions.
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANI2_G900VVZW1ANI2_G900VVRU1ANI2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
It's the same thing that I was getting before, I'm sorry if I did not explain myself in detail at first.
I have used 2 versions of Odin 3.09 (which I used on my own and got the above message).
3.07 as suggested by ag4751.
I have used 2 different roms and both fail.
->G900V_VZW_1_20140331185350
->G900VVRU1ANI2-20140919141518
@fffft
To answer your question as to what tutorial I followed, I followed ag4751's tutorial/explanation on his reply. It's basic, just like all the other tutorials I googled.
1.) Put the phone in download mode
2.) Open Odin
3.) Select PDA
4.) Wait for the file check
5.) Click start
and then it fails.
That's what @ag4751 suggested, that's what I tried, that's what I tried before, that's what I'm trying now and all that is failing for some reason.
..
..
Good evening,
for unknown reasons my phone (Unbranded Samsung Galaxy S4) started to show weird signs of system failures. It kept restarting and hanging on the boot screen; often rapidly changed the battery percentages and then crashed. A day after these weird errors appeared the phone suddenly refused to boot at all. The boot process stopped at the Samsung logo and completely froze.
So I tried booting into recovery... But it didnt work? Sometimes it simply rebooted after showing "Recovery booting..." in the top left side of the screen and sometimes it displayed an red error showing "No command". On the 15th try or so it suddenly showed a kernel error instead:
"SET WARRENTY BIT: KERNEL"
Instead of using recovery mode I instead booted into Odin mode, where to my surprise I found that the current binary was no longer the official Samsung one, but a custom one. I decided on downloading stock firmware from the Samsung database and flashing it with Odin v3.11.
Name of the used firmware pack: " I9505XXUHOJ2 [5.0.1]"
I put it into Odin mode and then applied the firmware md5 file under AP in Odin 3.11 and it started working. Flashing the image was successful until half through the system.img.ext4 part where after half of the operation it suddenly failed and disconnected. Recovery.img and so on, however, was flashed successfully. I rebooted it into Odin mode, where the binary was now "Samsung Official" and retried the procedure.
This time it failed instantly. Shortly after starting the operation Odin said it could not open the specified file and the operation was aborted. The phone is now stuck in a "Firmware Update Failed - Use Kies Recovery" bootloop that remains even when I turn the phone off. (It simply turns back on again)
Is the phone screwed now? Re-Partioning was unchecked so I don't know if the partition table was ruined or not.
Does anyone have an idea?
Info shown after operation in Odin mode:
PRODUCT NAME: GT-I9505
CURRENT BINARY: SAMSUNG OFFICIAL [CUSTOM before operation]
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLED
eMMC BURST MODE: ENABLED
I can't even turn off the phone now :victory:
No customization has occured on this phone. I have never used any custom roms or custom kernels. It simply started doing weird stuff on its own.
maybe hardware faulty? NAND corrupt?
Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
KNOX WARRENTY VOID: 0x1
Click to expand...
Click to collapse
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.
ThePrick said:
Perhaps try flashing TWRP until it's successful, and then use it to flash the framework file(s) you've placed on the SD (use another phone for this end, or an mSDcard adapter that comes with the SD (most laptops have a slot for this). This does away with many underlying assumptions, like the soundness of the cable, port, laptop/pc, and flashing software.
First just charge the battery until it's full.
Seems like a potential security threat. Are you sure you haven't rooted your phone somehow?
Btw, if the partition is indeed ruined, use TWRP to make a backup of the phone (even if there's nothing to backup). It'll restore the partition table. Then proceed to flash the framework from the SD via TWRP.
Click to expand...
Click to collapse
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
EDIT: Flashed TWRP successfully but S4 is refusing to boot into recovery
following error is dÃsplayed:
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY
Noroxuz said:
Before I read your post I tried flashing a 4.X software for GT-I9505, which was successful with ODIN.
Recovery still wont work, as it crashes the phone instantly. Booting normally got to the Samsung logo part and then froze.
Sometimes the phone shows very weird graphical glitches. It boots up with a green dotted screen and slowly turns brightness up to max. I think this might mean its hardware faulty.
Concerning the KNOX issue: The phone was never rooted nor modified. I have no idea how the system picked up a rooting process when there was none.
I'll try flashing TWRP... Atleast download mode still works even though everything else doesnt.
Thanks for your reply
Click to expand...
Click to collapse
I LITERALLY had the EXACT same problem.
See the thread here for some ideas: http://forum.xda-developers.com/gal...oft-bricked-s4-gt-i9505-t3430921/post68024954
I didn't mention the green screen and glitching because I didn't see it as relevant.
Just happenstance that it worked eventually.
I flashed the framework and it was successfully, but the system still didn't boot. I tried flashing the framework after a couple of days of persistent failure as a last ditch effort, and it worked, surprisingly, and I cannot explain it fully. I had planned to put the framework on an SD card and use TWRP i.e. recovery to flash it. That's still the best method imo. Try flashing TWRP and doing just that! It should work if there isn't any hardware damage. By the way, I tried older versions of Odin (3.07) when the newer versions didn't work. Additionally, perhaps flashing more recent ROMs would be a better idea (5.0.1, 5.1.1 (if Samsung has bothered updating it to that point)).
Once TWRP ((((or CWM )))) is flashed successfully, boot into recovery mode and do a backup. This should automatically restore the partition table. Then flash the framework file/tar and reboot. If it doesn't work, try flashing different firmware versions (5.0.1, 5.1.1) using the older versions of Odin, say, if TWRP was flashed successfully but the phone still won't boot into recovery.
Alternately, maybe the battery is dying, but I doubt it. Be ABSOLUTELY sure the power button is in perfect condition. The Galaxy S3, S4, Note 4, have a terrible history with defective power buttons causing all sorts of problems.
ThePrick said:
if TWRP was flashed successfully but the phone still won't boot into recovery.
Click to expand...
Click to collapse
Yeah... I flashed TWRP but got the
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRENTY BIT: RECOVERY
stuff instead. Last time I tried flashing a 5.X rom ODIN failed halfwax through so
Then I flashed stock ROM again and it got to the Samsung logo with the jingle but it goddamn crashed again.
Booted into recovery (which suddenly worked) and deleted user data/ cache.
Now it doesnt do anything anymore lol?
Probably broken GPU or NAND corrupting itself every 2 sec.
I dunno.
Samsung should really fix their stuff.
HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
abdulkareemsid said:
HELP ME IM NOT ABLE TO FLASH STOCK ROM ON GT I9505 <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I9505XXUHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_OXA_I9505OXAHOA7_CL3996895_QB3867680_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
Try a different USB port and/or cable.
Odin failures can happen when using incompatible USB cables and ports so try everything available.
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
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)