need some assistance, i think my phone is soft-bricked
i have a i9505 that when using odin to load a rom it always stop and gives the error nand write failed
it had TWRP as recovery and i was able to load CWM recovery no problem but still can't load a rom
i can boot into recovery and adb sees the device when i use sideload, however i cannot write to the device
the device will not boot it just goes into download mode now
any help will be greatly appreciated
thank you
neonflx said:
need some assistance, i think my phone is soft-bricked
i have a i9505 that when using odin to load a rom it always stop and gives the error nand write failed
it had TWRP as recovery and i was able to load CWM recovery no problem but still can't load a rom
i can boot into recovery and adb sees the device when i use sideload, however i cannot write to the device
the device will not boot it just goes into download mode now
any help will be greatly appreciated
thank you
Click to expand...
Click to collapse
Did you close all Kies tasks running in windows taskmanager? Kies prevents Odin from functioning correctly.
Put the .tar.md5 file in PDA, only checked Autoreboot and F.Reset.Time?
Or maybe a corrupt download, you could try to download the firmware again and flash that one.
yes i disabled everything, antivirus, closed kies etc
i can sideload arom on zip file using CWM recovery it looks like it is installing but phone still not booting, also i tried sideloading the same tar file and it failed just like with odin.
i also try installing the rom on zip format from CWM from internal sdcard and again it seems that it is installing but phone doesn boot
the install process is only taking a few seconds at best so i'm not sure what is going on
odi ngives me an error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-KNOX-FREE-HD-VOICE.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
any suggestions
thank you
Had the same problem, nothing worked, really bricked the phone.
Returned it to the retailer, they sent it back to Samsung and they gave me a new phone. I asked the retailer what happened but they said Samsung just sent a new phone without further info.
Verstuurd van mijn GT-I9505 met Tapatalk
isit hard bricked or soft bricked, i can still boot into recovery and download mode
please advise
I couldn't boot into recovery so I think you just soft-bricked it.
Verstuurd van mijn GT-I9505 met Tapatalk
XeroFox said:
I couldn't boot into recovery so I think you just soft-bricked it.
Verstuurd van mijn GT-I9505 met Tapatalk
Click to expand...
Click to collapse
Do you have usb debugging enabled in developer settings? As long as you can get in downloadmode it is not hardbricked afaik.
gee2012 said:
Do you have usb debugging enabled in developer settings?
Click to expand...
Click to collapse
Yes I did, but like I said before I got a new phone from Samsung.
Back on topic: Did you try flasing the stock firmware?
XeroFox said:
Yes I did, but like I said before I got a new phone from Samsung.
Back on topic: Did you try flasing the stock firmware?
Click to expand...
Click to collapse
Was adressed @ OP
gee2012 said:
Was adressed @ OP
Click to expand...
Click to collapse
Haha sorry!
Verstuurd van mijn GT-I9505 met Tapatalk
the phone does not boot into OS, when it boots it goes straight into download mode
I can flash recovery tar's i went from TWRP and CWM back and forth and that flashes ok, but if i try to flash a rom on tar from odin or install a rom on zip format from CWM or TWRP it does not work the phone keeps booting into download mode no matter what
i just need to load something to be able to get into the phone
thanks for the suggestions
neonflx said:
isit hard bricked or soft bricked, i can still boot into recovery and download mode
please advise
Click to expand...
Click to collapse
change usb port
use original usb cable
try with odin 1.85
i have tried several different odin's
one thing i did not mention is that on the screen of the phone the last line is in red and says
secure check fail
i also tried sideloadin a zip file but still the same
neonflx said:
i have tried several different odin's
one thing i did not mention is that on the screen of the phone the last line is in red and says
secure check fail
i also tried sideloadin a zip file but still the same
Click to expand...
Click to collapse
I have got secure check fail when i pushed a .bin file to the wrong adress on the partition. Fixed it with flashing original firmware via odin.
But since you fail when flashing you can't try that.
Could you have ****ed up your partition while trying to flash?
Perhaps flash with original PIT file and original ROM and choose re-partition? Make sure you have good usb cable and a usb port connected directly to your motherboard.
Tampering with tthe partition can make it worse. So don't do it unless you have thought it trough.
btw... when you are in twrp can you mount all partitions and enter archive manager and browse the directorys?
Yes I can browse the file system, /system is empty just a /bin folder nothing in it
all the other folder have data/files in it
i can also sideload a zip file but after isntal is the same
i have a pit file named CSB_signed_Fusion3_EUR_0325_V2, is that the right pit file?
there is also a back up on the restore section date 1970??? i restored it but still the same
confused, any help!!
thank you
i tried the pit file however, it failed
errot
re-partition operation failed
any ideas
changed USB port and everything is ok (USB3.0) and grabed original cable. maybe 0.5 Ampers is to small.
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?
Hy, I own an S5 G900F. I flashed a stock rom latest version then my S5 root before flashing a rom Omega 2. Everything worked perfectly until I decided to change my sdcard having taken care to move all the files present on my old sd card on news.
At start of my S5 nothing worked, I have the screen that lights up with the SAMSUNG GALAXY S5 logo, powered by ANDROID but the top right I have the following message in red: kernel is not enforced seandroid and yellow: set warranty bit kernel.
I can not switch to recovery since disappeared, I just can enter download mode.
With odin so I tried to flash my S5 with stock rom (XEF-G900FXXU1ANE2-20140519102224).
Here is the odin message when I load this rom:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> 900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully
<OSM> ..
<OSM> Leave CS.
My S5 is well recognized by odin, it tells me blue com port 3 and
<ID:0/003> Added!
Top right of the screen of my S5 I have these messages:
ODIN MODE
PRODUCT-NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
LOCK REACTIVATION (KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CBS)
SWREV RP: S1, T1, R1, A1, P1
UDC: START
I run flash with odin:
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
The flash stops with S5 on the screen messages:
MMC: mmc_read fail
ODIN: flash read failure
I do not know what to do! Is it a hardware brick or a simple software problem??
Thank you for trying to help me if it is possible. I hope to have been clear
best regards,
Sorry for my english, this is a google translation
Not bricked but you need to flash a pit file along with the firmware, look here http://forum.xda-developers.com/showthread.php?t=2737448 for the correct pit file or how to extract one if yours isn`t listed (need root for that).
Thank you for your quick response but I already tried to flash the pit with odin without success always with the same message MMC: mmc_read fail etc ...
SM-G900F_pit_16GB.zip (fail)
SM-G900F_pit_16GB_SER.zip (fail)
SM-G900F_pit_16GB_ETL.zip (fail)
Something, some glitch apparerently corrupted your kernel. And that (probably subsequently) corrupted your partition structure. You are soft bricked at this point.
As gee2012 suggested, you now need to flash both the PIT and a full stock image. Stop trying to flash random PIT files or you may end up hard bricked. You need to identify the correct PIT and use that one. The PIT file should match your phone model, original carrier (i.e. match your baseband) and ROM size.
Flash the correct PIT in conjunction with a full stock Odin image from the matching carrier. Note that stock firmware is flashed as a tar file, but the PIT file needs to be flashed as a PIT file, if you are trying to flash it while it's still zipped that alone will cause it to fail.
.
i having the same problem
i'm having the same problem with my sm-g3502L, i have the corect pit file and the correct rom, but always failed, please someone help me, its very important