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?
After tried flashing rom from other regions (e.g. XME, TGY, THL, SFR) with odin 3.09, but fail every time. Now, I cannot use my phone. When turn on my Note 3, it will be in Odin Mode, cannot get into recovery mode at all.
So, I let someone help to solve this problem, but it get worse as show in below link.
Could anyone help me with this problem??
imagizer.imageshack.us/v2/800x600q90/191/w28d.jpg
Solved this issue by this link: http://forum.xda-developers.com/showthread.php?t=2614787
wittaya73 said:
After tried flashing rom from other regions (e.g. XME, TGY, THL, SFR) with odin 3.09, but fail every time. Now, I cannot use my phone. When turn on my Note 3, it will be in Odin Mode, cannot get into recovery mode at all.
So, I let someone help to solve this problem, but it get worse as show in below link.
Could anyone help me with this problem??
imagizer.imageshack.us/v2/800x600q90/191/w28d.jpg
Click to expand...
Click to collapse
Did you try to upgrade to 4.4.2?
radicalisto said:
Did you try to upgrade to 4.4.2?
Click to expand...
Click to collapse
Not yet. I've just tried with 4.3
Here are Odin shown to me:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can anyone help me, please?
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Andrewtst said:
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Click to expand...
Click to collapse
I did flash back to origin country, which is SFR (France) with Odin, but it still fail.
In Odin, I tick "Auto Reboot" and "F. Reset time".
wittaya73 said:
I did flash back to origin country, which is SFR (France) with Odin, but it still fail.
In Odin, I tick "Auto Reboot" and "F. Reset time".
Click to expand...
Click to collapse
It's failing on bootloader, did you attempt to upgrade to 4.4.2 and change your mind? Or trying to downgrade ?
radicalisto said:
It's failing on bootloader, did you attempt to upgrade to 4.4.2 and change your mind? Or trying to downgrade ?
Click to expand...
Click to collapse
I've never attempted to upgrade to 4.4.2.
I've just tried to flash with international firmware in order to get local language menu.
My Note 3 is SM-N9005 SFR, but I want to flash with SM-N9005 THL or XME. But flash fail every time, and it cannot go into normal screen, even recovery mode. I just stuck in Odin mode when I turn on my phone.
Andrewtst said:
Try flash back your origin country ROM. What had you tick at PC Odin?
and you mention TGY, if not wrong that is for Hong Kong.
Hong Kong N9005 is unfriendly with any others country ROM, it can't cross flashing.
Click to expand...
Click to collapse
Hi, sorry to hijack, but how do I know if a ROM is going to be compatible with my phone?
I don't think the ROM thread would say what country's Note 3 it will be compatible/incompatible with, right? I'm getting a Note 3 and planning to flash a custom ROM.
fterh said:
Hi, sorry to hijack, but how do I know if a ROM is going to be compatible with my phone?
I don't think the ROM thread would say what country's Note 3 it will be compatible/incompatible with, right? I'm getting a Note 3 and planning to flash a custom ROM.
Click to expand...
Click to collapse
You are right. I don't know either. I only get the ROM which others already did before.
wittaya73 said:
Not yet. I've just tried with 4.3
...
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What does it say on the "download mode" initial screen? (knox and the other flags).
Was the phone carrier-locked on SFR?
wittaya73 said:
I've never attempted to upgrade to 4.4.2.
I've just tried to flash with international firmware in order to get local language menu.
My Note 3 is SM-N9005 SFR, but I want to flash with SM-N9005 THL or XME. But flash fail every time, and it cannot go into normal screen, even recovery mode. I just stuck in Odin mode when I turn on my phone.
Click to expand...
Click to collapse
Flash BTU firmware, it should be OK.
Find the download link below:
- BTU MJ7: http://www.sammobile.com/firmwares/3/?download=21277
- BTU MK2: http://www.sammobile.com/firmwares/3/?download=23215
Firstly try BTU MJ7
xclub_101 said:
What does it say on the "download mode" initial screen? (knox and the other flags).
Was the phone carrier-locked on SFR?
Click to expand...
Click to collapse
knox 0x1
aboot fused 3 > binary 2
I did try with BTU firmware, but it still fail flashing with Odin 3.09
Thanks for your replys
I had this error (among others) when I soft bricked & couldn't get MJ7 to flash but it worked after flashing pit, BTU MK2, modem & csc with Odin 3.0.4
zoso28 said:
I had this error (among others) when I soft bricked & couldn't get MJ7 to flash but it worked after flashing pit, BTU MK2, modem & csc with Odin 3.0.4
Click to expand...
Click to collapse
Can you give me the instruction to flashing pit, BUT MK2, modem & csc with odin? Thank you.
wittaya73 said:
knox 0x1
aboot fused 3 > binary 2
I did try with BTU firmware, but it still fail flashing with Odin 3.09
Thanks for your replys
Click to expand...
Click to collapse
Which version of BTU have you tried?
Did you try MK2 BTU?
vndnguyen said:
Which version of BTU have you tried?
Did you try MK2 BTU?
Click to expand...
Click to collapse
Yes, I've flashed (AP) MK2 BTU with Odin 3.09 and 3.04; but result still the same, Fail !!
I don't know that the first error (fail) was because I chose BL instead of AP or not.
I noticed that I did wrong after I clicked start button; and Odin told me Fail, then I flashed again with odin in AP with the same file.
wittaya73 said:
Yes, I've flashed (AP) MK2 BTU with Odin 3.09 and 3.04; but result still the same, Fail !!
Click to expand...
Click to collapse
What is the bootloader version of XME, TGY, THL firmware you have used to flash?
Make sure the bootloader of the firmware is being flash (BTU) should be equal or higher the bootloader version of the above firmwares.
You can not use a lower bootloader to flash over a higher one.
vndnguyen said:
What is the bootloader version of XME, TGY, THL firmware you have used to flash?
Make sure the bootloader of the firmware is being flash (BTU) should be equal or higher the bootloader version of the above firmwares.
You can not use a lower bootloader to flash over a higher one.
Click to expand...
Click to collapse
With my stupid, I didn't look what was my current bootloader that came with the mobile phone. I've just downloaded "N9005XXUDMJ7_N9005OLBDMK2_THL", and flashed it with Odin.
Hello. I tried to flash my phone. But i download the wrong flash. . This is my first android phone. Then The odin fail. it say's <ID:0/006> Complete(Write) operation failed. Is my phone bricked? And when i press up+home+power, it says firmware upgrade encountered an issue. Please help me. . What will i do? I try other odin. It says Fail! (SAVE) at last. .
I try Odin 3.04 and 3.07 and 3.09. All fail. 3.07 Says Fail!(Save). while the other two says complete(write) Operation failed.
My phone is g900f.
Can someone please help me? Im downloading other firmware to my phone. I hope this works.
What region is your phone?
Hi. can anybody help me? sorry for my bad English
the phone works in recovery and download mode but can't load the oficial firmware with odin :\ (i downloaded the oficial s5 verizon firmware 5.0 for sammobile)
fotos.subefotos.com/ba14a0012d1d4795413aa15d32d12581o.jpg
fotos.subefotos.com/0c4acf9eb3819fa45133a3659831d1c4o.jpg
ERRORS:
UDC START
SECURE CHECK FAIL: aboot
SECURE CHECK FAIL: PIT
odin:
aboot.mbn
NAND WRITE start!
FAIL(auth)
succeed: 0 / failed: 1
Was the file you downloaded compressed, and needed extracted before flashing in Odin?
When you load it into Odin using the AP button, what messages do you get?
Sent from my SM-G900V using XDA-Developers mobile app
I got this S7, wanted to flash 930U firmware to use T-Mobile but a failed flash has me in a boot loop. I fully updated before trying to flash, so it is I assume on the newest bootloader, etc.
I have attempted the newest firmware files that I can find (G930AUCS4BQL1) but am still getting the SW REV CHECK FAIL through Odin.
Are there files available that will fix this, do I just need to wait for them to come out, or have I bricked this thing?
Thanks for any help and have a great day!
Update:
- Using PrinceComsy Odin results in: FAIL! (Auth)
- USB Debugging is OFF and I am unable to boot to change that
- I am leaving the BL file blank in ODIN
perhaps you should try using offcial odin when flashing official images.
try version 3.12.3. whatever you do, don't use the princecomsy version unless for flashing engboot