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
Related
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or <ID:0/003> There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
re: cannot get into recovery.
EvilM0narch said:
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or <ID:0/003> There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
Click to expand...
Click to collapse
During your unsuccessful flashing of the google edition rom you have lost ROOT and the custom and or stock recovery.
That is why you cannot go into recovery mode.
You are lucky that the .pit file did not flash, you could have ended up with a brick (unusable phone).
The .PIT file is the partition information table, if that is changed or damaged you would need to send
your phone to samsung or other phone repair shop to get it fixed.
What you need to do is to download and Odin flash the stock-rooted i9505 rom which can be found here:
http://www.androidfilehost.com/?fid=23060877490003683
This rom is pre-rooted and you will be able to get into recovery mode without any issues.
Once this is odin flashed, be sure to make a nandroid backup before flashing other cwm/twrp zip file roms.
The "phone cannot be located" error most likely means that you either do not have the proper samsung usb
driver installed or you need to check the usb cable connections to your computer and phone.
Perhaps use a different usb cable and a different usb port will fix this issue.
Just in case you need it, here is the link for the official usb drivers for the samsung s4 phone:
http://org.downloadcenter.samsung.c...5728593/MCCI_WHQL_USB_Modem_Driver_4.40.7.exe
Good luck!
No luck
Misterjunky said:
During your unsuccessful flashing of the google edition rom you have lost ROOT and the custom and or stock recovery.
That is why you cannot go into recovery mode.
You are lucky that the .pit file did not flash, you could have ended up with a brick (unusable phone).
The .PIT file is the partition information table, if that is changed or damaged you would need to send
your phone to samsung or other phone repair shop to get it fixed.
What you need to do is to download and Odin flash the stock-rooted i9505 rom which can be found here:
(Removed link due to under 10 posts)
This rom is pre-rooted and you will be able to get into recovery mode without any issues.
Once this is odin flashed, be sure to make a nandroid backup before flashing other cwm/twrp zip file roms.
The "phone cannot be located" error most likely means that you either do not have the proper samsung usb
driver installed or you need to check the usb cable connections to your computer and phone.
Perhaps use a different usb cable and a different usb port will fix this issue.
Just in case you need it, here is the link for the official usb drivers for the samsung s4 phone:
(Removed link due to under 10 posts)
Good luck!
Click to expand...
Click to collapse
Firstly thank you so much for reaching out to help me with this matter. :good:
Sadly no such luck, running odin 3 v1.85
This is the result I had...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.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> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Going to try again using the drivers you have provided (restarting now)
Still no luck...
Odin v1.85
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
With no readout on the phone (as if the process never took place)
& using v3.07
Odin v3.07
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Through all these process only AutoReboot was checked...
The last attempt on v3.07 had the same result as a previous flash in which the process bar appears on the phone in download mode, but fails with the same read out on the device..
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
EvilM0narch said:
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
Click to expand...
Click to collapse
Are you definitely using PDA (not Phone) mode in Odin when flashing ROMs? Also are you running Odin using 'administrator' mode if using Windows?
Sent from my Nexus 7 using xda app-developers app
PDA
gsmyth said:
Are you definitely using PDA (not Phone) mode in Odin when flashing ROMs? Also are you running Odin using 'administrator' mode if using Windows?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes 100% sure that I'm selecting PDA and Admin privileges.
Honestly I'm baffled I'm now charging the battery now to ensure the phone has enough to attempt this process again.
The battery icon fails to display a meter... Just an empty battery with a loading circle inside, assuming this is because the phone cannot access the images for the battery charging display? (The display that is present when the phone if turned off and you are charging)
I'm still stumped with what to try here. Any suggestions?
I'm sure if I can get at least back into recovery mode I could resolve it, but with odin failing due to pit each time it's just like banging my head against a wall :silly:
Screen Capture
Attached is a capture of the process using odin
Hope this can help in some way...
Edit: wrong thread
EvilM0narch said:
Attached is a capture of the process using odin
Hope this can help in some way...
Click to expand...
Click to collapse
No pit partition = YOUR PARTITION TABLE IS CORRUPTED. flash stock firmware with pit file in Odin 3.04, untick "auto-reboot", when it "pass", take off battery, inset it, boot into recovery, reset the phone, reboot
Sent from my Galaxy Nexus using xda premium
FAIL
samersh72 said:
No pit partition = YOUR PARTITION TABLE IS CORRUPTED. flash stock firmware with pit file in Odin 3.04, untick "auto-reboot", when it "pass", take off battery, inset it, boot into recovery, reset the phone, reboot
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for this, have tried flashing with the rom that Misterjunky provided (with pit from samersh72) and fail
also tried the EE rom I found on the forum that samersh72 provided (with pit from samersh72) fail
tried flashing just the pit alone... fail
**making sure that "auto-reboot" was unticked**
In each process >> re-partition operation failed?
:crying:
I'm now downloading the EE rom direct from sammobile (Although for some reason I'm sure this device was originally Orange network)
Will update the situation when all has downloaded and I can try again.
Thanks to all for your input on this.
EvilM0narch said:
Thanks for this, have tried flashing with the rom that Misterjunky provided (with pit from samersh72) and fail
also tried the EE rom I found on the forum that samersh72 provided (with pit from samersh72) fail
tried flashing just the pit alone... fail
**making sure that "auto-reboot" was unticked**
In each process >> re-partition operation failed?
:crying:
I'm now downloading the EE rom direct from sammobile (Although for some reason I'm sure this device was originally Orange network)
Will update the situation when all has downloaded and I can try again.
Thanks to all for your input on this.
Click to expand...
Click to collapse
re-partition must work. make sure that you are using the right pit for your variant, unzip it before putting it in pit window in odin
flash your original EE official rom from sammobile
Making sure all is right
samersh72 said:
re-partition must work. make sure that you are using the right pit for your variant, unzip it before putting it in pit window in odin
flash your original EE official rom from sammobile
Click to expand...
Click to collapse
Pit variant I have is from you for my device "i9505", so that would be the correct pit file?
Still waiting on the EE official rom from sammobile to download, as long as all is correct I will try again once downloaded.
Flash MH8 or newer...
In my case it was not possible to downgrade... i think that if you flash a mh8 or higher, after that is not possible downgrade because new bootloaders.
Enviado do meu GT-I9505 utilizando Tapatalk 4
MH8
sanespro said:
Flash MH8 or newer...
In my case it was not possible to downgrade... i think that if you flash a mh8 or higher, after that is not possible downgrade because new bootloaders.
Enviado do meu GT-I9505 utilizando Tapatalk 4
Click to expand...
Click to collapse
Reading more on this it does seem you are right, can you elaborate as to what is mh8?
Is this a specific rom? Reading what I could find it seems it will only allow custom roms on the device or a rom that is MH8?
Can anyone shed some light on this?
Going to download the latest BTU MH8 for UK and give that a try? Hopefully I'm making progress as the MH8 rule would explain why it's not working
EvilM0narch said:
Reading more on this it does seem you are right, can you elaborate as to what is mh8?
Is this a specific rom? Reading what I could find it seems it will only allow custom roms on the device or a rom that is MH8?
Can anyone shed some light on this?
Going to download the latest BTU MH8 for UK and give that a try? Hopefully I'm making progress as the MH8 rule would explain why it's not working
Click to expand...
Click to collapse
be aware MH8 firmware will lock your bootloader, so you will not be able to downgrade.
your problem is in partition table. your solution is with the pit file flashed with your stock firmware.
if it fail, see odin troubleshooting in my thread
samersh72 said:
be aware MH8 firmware will lock your bootloader, so you will not be able to downgrade.
your problem is in partition table. your solution is with the pit file flashed with your stock firmware.
if it fail, see odin troubleshooting in my thread
Click to expand...
Click to collapse
I believe I am already flashed to MH8, but I am not sure.
I have tried flashing the pit located in your sig for my GT-I9505 but it always fails?
Is there something else I am missing or not doing correctly? I have been following each guide and double checking the steps before I try anything.
No matter what action i take the pit flash with the file "I9505_pit file.zip" located here >> http://forum.xda-developers.com/showthread.php?t=2265477
always fails? I have no idea why? Or which steps to take.
Sorry to be such a pain,
EvilM0narch said:
I believe I am already flashed to MH8, but I am not sure.
I have tried flashing the pit located in your sig for my GT-I9505 but it always fails?
Is there something else I am missing or not doing correctly? I have been following each guide and double checking the steps before I try anything.
No matter what action i take the pit flash with the file "I9505_pit file.zip" located here >> http://forum.xda-developers.com/showthread.php?t=2265477
always fails? I have no idea why? Or which steps to take.
Sorry to be such a pain,
Click to expand...
Click to collapse
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Another machine...
samersh72 said:
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
Have tried all except another computer, someone mentioned that an XP based machine works best.
Those are like gold-dust around here, I will try this process on a laptop and see if I can get it to work... That seem to be my best bet for now
Again kudos for all of the help and the quick replies. :good:
All hope seems lost....
After finally trying every method on this PC
(All versions of Odin I could find, all usb ports, original usb lead, kies is disabled, drivers un-installed/re-installed)
And having no luck...
I have had some different results on the laptop;
all other versions of odin I tried (v1.83, v1.85, v3.04, v3.06) just fail;
(again all usb ports, original usb lead, kies is disabled, drivers un-installed/re-installed)
And this read out...
flashing pit and rom > Complete(write) operation failed.
flashing only pit > Complete(write) operation failed.
However on Odin3 v3.07
flashing pit and rom > There is no pit partition
flashing only pit > There is no pit partition
and on v3.09
flashing pit and rom > re-partition operation failed.
flashing only pit > re-partition operation failed
I'm at a total loss now. I have a chance to send it back to cash generator as thats where my friend had purchased it from.
Is it worth doing so?
Any one have any thoughts or suggestions to aid this situation?
:crying:
I guess my only option here as I cannot get it to flash, is to either sell the phone in the state it is in.
Or send it back to Cash Generator to see if they will replace/refund it.
:crying:
samersh72 said:
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
Okay so just got my device back from my friend with the Jtag, and this is the report he run for me
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
Where can I get eMMC chip repaired?
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression
samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe
@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware
samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!
EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?
bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).
Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.
Possible not a genuine Note 3?
This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..
Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.
Flashed Rom zip. Note 3 back to health.
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.
If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.
Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?
I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?
I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...
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.
..
..
I tried rooting my phone using Odin from this tutorial:
https:// theunlockr(dot)com/2016/02/04/root-samsung-galaxy-s6-edge-plus/
It failed and now my phone reads "Kernel is not seandroid enforcing" and will not enter recovery mode.
I tried installing the proper firmware but when I try using that it fails and my phone then reads "SW REV CHECK FAIL DEVICE 3 BINARY 2"
This is what Odin says:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, and any help would be greatly appreciated!
Also, the firmware I used is G928TUVU2COI5_G928TTMB2COI5_TMB and my model is SM-G928T
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
I'm on the most updated software, that's entirely possible. I can get on download mode, I will try to use the link you gave me and give you an update, thank you very much
kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
Okay so I tried it but since my phone doesn't turn on I cant put in the files from that link, I tried using oden and it failed again. On Odin it says Pass but my phone continues to say Kernel is Not seandroid enforcing, I've been at this for so long and I can't find a fix :'(
Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
kdogguk said:
Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Click to expand...
Click to collapse
It's a three file flash I believe, I've just been putting one huge file in the AP, I haven't heard of the three file thing, I've tried the Sammobile firmware stock too and it hasn't worked. It fails on Odin. Do you know anything else I could try?
You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
kdogguk said:
You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
Click to expand...
Click to collapse
Sorry this is really late, apparently nothing worked, I took it to the uBreakiFix and they apparently had to install the firmware by it's build number which took like a week cause I had to go through every single build number. But thank you very much for your help