Related
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running XXUAMDC stock rom, network: Three UK.
Attached is a screenshot of what I mean.
Thank you.
Didn't the TWRP site suggest using GooManager to install if you're rooted? Maybe give that a shot.
My unbranded UK s4 also said write protection enabled however I've had no problem installing twrp recovery.
Flashed via odin after putting phone into download mode... Have twrp in pda and it's checked in the box next to it...
Sent from my GT-I9505 using xda premium
chalger said:
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running stock rom, network: Three UK.
Click to expand...
Click to collapse
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Have you tried using Super SU app and unrooting?
Ok.
I tried using GOOmanager, it cannot find suitable recovery for my device (which is strange as you may find it through TWRP web page).
When I choose in GOO to reboot to recovery it actually gets me to stock recovery (I still can NOT get into recovery using power+home+UP)
When i try to flash TWRP using (newly discovered via GOO) stock recovery it looks like that:
There is a broken android icon (see 1st attached file) and the text
-reboot system now
-apply update via ADB
[.....]
# MANUAL MODE #
Applying Multi-CSC
Applied the CSC-Code : H3G (btw H3G is my carrier, three UK)
Successfully applied multi-CSC
when I choose the recovery file to flash I'm getting response that E:\signature verification failed
Again everything I've done with the phone was CFroot, that is it. No custom rom etc or other playing with it.
//edit
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Click to expand...
Click to collapse
I've got EXACTLY the same behaviour. I discovered GOO manager allowed me to boot into stock recovery.
Thanks for your interest.
chalger
If you're having problems check the thread here: http://forum.xda-developers.com/showthread.php?t=2266336
It's the same method I used to root my phone and flash TWRP. (I too have write protection enabled)
write protection enabled means nothing
I have the exact same thing written on mine.
I have CF-Auto-Rooted mine AND TWRP 2.5 placed on mine, both using ODIN method.
No issues at all - both work perfectly fine.
chalger said:
(I still can NOT get into recovery using power+home+UP)
Click to expand...
Click to collapse
Try using just the Vol Up+Power. Once the phone vibrates, let go of the power but keep holding the up key until you see something appear on the screen. That works on my non-rooted phone to get into recovery.
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
problem rooting i9505
chalger said:
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
Click to expand...
Click to collapse
Hi All,
Just got my galaxy s4 i9505 with baseband XXUAME2. Have been trying to root this using CFROOT via odin numerous times but each time it fails. The error message includes "write operation failed" and "No PIT partion".
I have downloaded the correct PIT file and tried again but the same problem again.
I have further tried to flash pre-rooted firmware and another stock firmware but again - nothing I do seems to work.
Have tried the factory reset as well but again does not work.
Have tried flashing using motochopper method but also does not work.
Was hoping if someone could kindly extend his/her expertise - I am completely clueless at this point..
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Still failing to flash anything usin odin
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Anjamil said:
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Click to expand...
Click to collapse
Me too i have the same problem .. any other method to flash back to original fiemware ?
cheers
Indra
problem solved
I used odin 1.85 and original usb cable that came in the
box. Problem solved am now able to flash all roms
I'm having exxcactly the same problem, but i can't boot the phone, it's just stuck on s4 screen, can someone help?
Thanks in advance.
Thanks for this. That solved my issue.
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
First time i tried to install a custom recovery on my S4 I9505 LTE. With Odin.. It didn't work..
I knew about heimdall.. And i gave that a try. And it worked perfectly. The one thing that's a bit weird.. After it first worked through heimdall. I could flash any custom recovery through Odin. But I think you should give heimdall a try..
Here is a link to how to install CWM on the cyanogenmod wiki: wiki.cyanogenmod.org/w/Install_CM_for_jfltexx#Installing_a_custom_recovery_on_Galaxy_S4_.28International_LTE.29 (I can't post links yet. So i just removed the http)
i flashed modern , and, it is fail, what wrong
[/url][/IMG]
my phone have this entry : "write protection : enable"
on my phone is also 'write protected- enable' but odin and cwm work fine
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?
I just flash a custom rom of Note 4 N916L for Note 4 N910L, now my phone is standing Logo Note. I try to flash stock rom by odin but it fail.
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I turn on my phone, it has a comment: Kernel is not seandroid enforcing.
I had lock reactivation, and turn off Kies. As well using lastest Odin and Stock rom.
Please help me.
Thank you so much!
XDA:DevDB Information
Kernel is not seandroid enforcing, Kernel for the Samsung Galaxy Note 4
Contributors
chung06107014
Kernel Special Features:
Version Information
Status: Testing
Created 2015-11-24
Last Updated 2015-11-23
Which Devise are you on N910C or N910L ?
Its normal to get "Kernel is not seandroid enforcing" status due to SELUNIX : permissive + Enabled root permission . Its no issue just due to new bootloader of 5.1.1 update.
djmax81 said:
Which Devise are you on N910C or N910L ?
Its normal to get "Kernel is not seandroid enforcing" status due to SELUNIX : permissive + Enabled root permission . Its no issue just due to new bootloader of 5.1.1 update.
Click to expand...
Click to collapse
My phone is N910L (I flash a wrong rom of N916L -Korea version). Yes, "Kernel is not seandroid enforcing" status is normal when flashing a custom kernel and that phone still run well. But my case, I flash wrong rom and my phone doese not run (just stand logo Samsung Galaxy Note 4)
So. Please help me to guide to solve this popblem.
chung06107014 said:
My phone is N910L (I flash a wrong rom of N916L -Korea version). Yes, "Kernel is not seandroid enforcing" status is normal when flashing a custom kernel and that phone still run well. But my case, I flash wrong rom and my phone doese not run (just stand logo Samsung Galaxy Note 4)
So. Please help me to guide to solve this popblem.
Click to expand...
Click to collapse
You need flash param file alog with Boot loader try Search for your devise .
...
You are on wrong bootloader modem, not compatible with your rom
Check the required bootloader modem the the custom rom page and flash it
Flash again rom just to confirm
djmax81 said:
You need flash param file alog with Boot loader try Search for your devise .
Click to expand...
Click to collapse
Cuold you show me clearly. I try to flash stock stock kernel for my phone (I took it from the stock rom. it is boot.img file, and changed to .tar by tool) then my phone restart and there is nothing change still stand in logo samsung.
After that I try to flash the stock rom by odin failed at all. and :crying:
ankahuja said:
...
You are on wrong bootloader modem, not compatible with your rom
Check the required bootloader modem the the custom rom page and flash it
Flash again rom just to confirm
Click to expand...
Click to collapse
Yes, I think that. But now I cant to flash the custom rom via custom recovery (TWRP...)
I just took my phone to the phone shop to get their help. After an hour a technical had checked it he told me that my phone had lose kernel and it take a few days to repair and he is not sure to finish. I decide take my phone back home ( I think it is a softbrick )
can u share the rom for N916l
the custom rom...
thnx
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.
Hi, when trying to flash my Verizon S7 back to stock (with the correct verizon files) I got this odin log
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to exit I got the "Software Update Failed" and when trying to flash again it's just a stuck bar on my screen. Not sure what to do and I'm kinda of new to this but I'd appreciate any help. Since then my phone has been stuck on the green screen since and whenever I press anything it just returns to the screen.
Any fast help would really be appreciated, it's been like this for hours and I'm not sure what to do ):
I'm gonna take a quick stab at this and say use the other CSC file, whichever one you haven't tried (either csc_vzw or home_csc_vzw).
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Are you going from U firmware? I had to check repartition when I did.
ironbesterer said:
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Click to expand...
Click to collapse
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Sayunoi said:
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Click to expand...
Click to collapse
Same thing here. I can only get into stock recovery with the error "dm-verity verification failed" (most options are disabled), and into bootloader, but unable to flash stock ROM; it just fails every time.
I'd be glad for a solution!
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
azoller1 said:
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
Click to expand...
Click to collapse
Mine still has the error when I included the bootloader file.
Another thing I should mention is in the top right it says "SW REV CHECK FAIL : [system] Fused 3 > Binary 1
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Sayunoi said:
When trying to exit I got the "Software Update Failed"
Click to expand...
Click to collapse
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
JaffXsMan said:
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
Click to expand...
Click to collapse
Really wondering the same thing =/
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Sayunoi said:
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Click to expand...
Click to collapse
You cannot flash a stock rom with an older bootloader than what ever you currently have on your phone. You can only Odin flash a stock rom with same or newer bootloader. So usually you cannot go to an older rom only newer.
Can I try flashing stock rom while in the Software update failed screen, or do I need to be in download mode?
Sayunoi said:
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Click to expand...
Click to collapse
Try re-downloading the firmware. Are you sure you had the right firmware downloaded? The error seems to be caused by some kind of mismatch between the software trying to be flashed and what software you currently have on your phone
Also, make sure you are using the non princecosmy Odin 3.12
When ever I try to flash stock onto my phone, i'm getting the error "SW REV CHECK FAILED : [aboot] fused 4 > binary 2" I don't know what any of this means. Could someone explain this? Also when trying to flash stock i'm in "System Update Failed" screen and a little bar appears at the bottom. Does this mean it is still able to download the stock rom at all? One last thing, if I were to try and flash G935U instead of G935V could that help? Any help would be nice
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone. I ran into the dm_verification failed and the only option was to download the latest firmware and flash that.
JerseyDubbin said:
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone.
Click to expand...
Click to collapse
Do you mean sammobile? https://www.sammobile.com/firmwares/database/SM-G935F/
That or http://samfirm.net/I believe.