Soft-bricked my S4? - Galaxy S 4 Q&A, Help & Troubleshooting

Hi there,
I have the Samsung Galaxy S4 SPH-L720 Sprint (on RingPlus). I just installed Cyanogenmod on a Moto E and loved it, so figured I would install the S4 Sprint version on my S4. I have a feeling I didn't wipe the cache before doing so, because the S4 had a different recovery software (as opposed to TWPR which I was more familiar with). After rebooting I went through the whole "new phone" setup and it looked like the stock Android. So, like an idiot I decided to try installing TWRP so it would be more familiar to then install Cyanogenmod. I saw a few people recommend RASHR as the easiest way to install TWRP. So I used it and happily clicked ok when it asked if I would like to reboot into recovery.
It rebooted and hung with:
Code:
RECOVERY BOOTING.....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
After rebooting again and again I got the same message. Then I read that flashing a stock ROM might do the trick. So I did the vol down, home, and power to get to the screen warning about damaging the OS, etc. Volume up selects the option to continue which does allow me to get to the "Downloading..." screen.
The upper left displays:
Code:
ODIIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I plugged it in via USB (have tried several different USB cables and 2 different computers) it is recognized in Oden. But after selecting AP and choosing the ROM and clicking "Start" it hangs. I have tried a few ROMS now, which in retrospect was probably not wise, but I saw post after post saying, "just install a stock ROM". I've also tried installing TWRP and CWM via Odin and get the same hang. It hangs with Odin reading:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720_OD2_Pre-Rooted_Firmware.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> boot.img
And the phone reading "Downloading... Do not turn off target!!" with a tiny blue progress bar (maybe equivalent to 2%) that sits still indefinitely. The upper left on the phone adds the line:
Code:
START [224, 1440]
after the eMMc BURST MODE line. It is the same progress and same "START [224, 1440]" no matter what ROM or file I'm trying to add via Odin. I simply have to hold down the power key for several moments before it shuts down. I let it sit for 45 minutes with zero difference in progress.
What I didn't realize was that if I choose "cancel" (volume down) in the download confirmation screen it would reboot not in the recovery mode. I was thrilled to see the animated Samsung logo appear but after another 45 minutes of watching the logo continue animating with no boot progress I realized this wasn't going to get me anywhere.
I read that I can use Kies to do a recovery, but it requests a Serial Number, which is nowhere to be found on physical phone... Only the ESN and HEX numbers (and model number, etc.) Looking online everyone tells me to find it in my settings... which I can't access of course.
Since I can communicate via Odin, I still have hope... but it's running thin. What should I try? I'm using Window 10 64bit if that means anything.
Thank you for your help!
-Stephen

Also, I found other forum posts that said I just need to wipe the cache and format to factory, but I can't do that since I can't get to a recovery screen. And finally, I read that the Partition could be jacked up, but I don't even know where to start with that...

You will be fine. Nothing wrong with your phone.
Here you have TWRP.
http://forum.xda-developers.com/showthread.php?t=2262999
1. Flash it using Odin. Uncheck auto-reboot before flashing in Odin. If it fails, then try all the usb ports on your pc.
2. Boot into recovery. Wipe /system, /data and /cache.
3. Flash the rom you want.
If you want CM 12.1 then this is a good choice to flash:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
ps this is the section for you phone:
http://forum.xda-developers.com/showthread.php?t=2262999

Lennyz1988 said:
You will be fine. Nothing wrong with your phone.
Here you have TWRP.
http://forum.xda-developers.com/showthread.php?t=2262999
1. Flash it using Odin. Uncheck auto-reboot before flashing in Odin. If it fails, then try all the usb ports on your pc.
2. Boot into recovery. Wipe /system, /data and /cache.
3. Flash the rom you want.
If you want CM 12.1 then this is a good choice to flash:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
ps this is the section for you phone:
http://forum.xda-developers.com/showthread.php?t=2262999
Click to expand...
Click to collapse
Thank you! What was I doing wrong? I always had Auto-Reboot enabled. Was that it? I also looked at my downloads and see that I was downloading the .img instead of .tar for twrp-2.8.4.0-jfltespr (but I tried other roms that were .tar which also hung). I tried a different USB port this time too (a port I've never used until now). I got it the first try. I had to do a factory reset before it would wipe anything (it complained about not being able to mount the different directories).
Now I need to do some reading into making backups.
Thank you again, I really appreciate it.
-Stephen

If you flash a custom recovery such as TWRP via Odin and you use auto-reboot, the custom recovery will sometimes be overwritten by stock recovery at reboot.

stephenphone said:
Thank you! What was I doing wrong? I always had Auto-Reboot enabled. Was that it? I also looked at my downloads and see that I was downloading the .img instead of .tar for twrp-2.8.4.0-jfltespr (but I tried other roms that were .tar which also hung). I tried a different USB port this time too (a port I've never used until now). I got it the first try. I had to do a factory reset before it would wipe anything (it complained about not being able to mount the different directories).
Now I need to do some reading into making backups.
Thank you again, I really appreciate it.
-Stephen
Click to expand...
Click to collapse
It's possible. Odin is not the most forgiving program there is.
Keep in mind that 2.8.4.0 is outdated and you should update it to the latest version. You will run into issues with Lollipop roms.
Here is the latest. You can just flash it in your recovery.
https://www.androidfilehost.com/?fid=24052804347763625

Related

[PROB] Can't install recovery, Download mode (Write protection: Enable)

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

[Q] [HELP] - Undoing MH8 update

So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.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> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4

[Q] In need of assistance (GT-I9505 UK EE)

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?

[Q&A] [ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore

Q&A for [ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
SamuriHL said:
I specifically decided not to use a rooted image this time due to the fact that being rooted blew up the ota for me. I wanted a place to start from that was clean. I figure our first 5.x update was a good place to kick out a new, fresh baseline build.
Click to expand...
Click to collapse
Are you going to release a rooted version? I used this one for now (Thanks!) but would prefer rooted.
All OK
Hello everyone,
I was wondering why there was a Kernel Source added? Also OTA .zip?
Using the attached downloads (very end of the post): "ODIN 3.09" and "I9505GUEUDNL3_FULL" seemed to work fine for me so far... Lollipop is up and running.
In any event, thanks for sharing.
Alex
pathogen47 said:
Are you going to release a rooted version? I used this one for now (Thanks!) but would prefer rooted.
Click to expand...
Click to collapse
No, these images are pretty big so the one I released is it. Rooting is super easy though. Just download CWM non-touch recovery and then from a command line:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
Go to install, then from sideload
From the command line:
adb sideload BETA-SuperSU.v.2.39.zip (or whatever the latest is at the time you do it)
And you're done.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
ar.richter said:
Hello everyone,
I was wondering why there was a Kernel Source added? Also OTA .zip?
Using the attached downloads (very end of the post): "ODIN 3.09" and "I9505GUEUDNL3_FULL" seemed to work fine for me so far... Lollipop is up and running.
In any event, thanks for sharing.
Alex
Click to expand...
Click to collapse
I add them for completeness of the post. Sometimes people are just looking for the OTA. Sometimes rom devs use my ODIN images and having the kernel source would be beneficial to them. For most users, the ODIN image is fine.
SamuriHL said:
No, these images are pretty big so the one I released is it. Rooting is super easy though. Just download CWM non-touch recovery and then from a command line:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
Go to install, then from sideload
From the command line:
adb sideload BETA-SuperSU.v.2.39.zip (or whatever the latest is at the time you do it)
And you're done.
Click to expand...
Click to collapse
Ok, didn't quite work like that, so for anyone else trying to do this, here's what I had to do.
Files needed:
I used the touch version of CWM and I used the Odin version: http://forum.xda-developers.com/showthread.php?t=2397108
I got the latest stable of SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053 (don't extract the zip).
Copy the SuperSU zip file to your phone. Internal storage or external sdcard, either will work.
1. Open Odin. Uncheck "Auto Reboot".
2. Click AP and select the CWM touch tar file.
3. Power off your phone. Disconnect from USB.
4. Get into download mode for flashing with Odin. Once Odin sees the phone, click Start.
5. When it's done, hold the power button on the phone to power it down. You can disconnect the USB once it's off.
6. Hold the volume up button and press and hold the power button. This will boot into CWM recovery.
7. Use the volume keys to select Install zip and press the power/hold button to select.
8. Select Install from either sdcard (for internal storage) or sdcard1 for the external sdcard.
9. Find the SuperSU zip and select to install it. Follow the prompts.
10. Done. Once it installs SuperSU, just have CWM reboot the phone and you now have root.
It DOES work like that. I wrote a script that does exactly what i wrote. It's how I rerooted myself after I published this unrooted ODIN image. There's no need to flash custom recovery just to install root.
SamuriHL said:
It DOES work like that. I wrote a script that does exactly what i wrote. It's how I rerooted myself after I published this unrooted ODIN image. There's no need to flash custom recovery just to install root.
Click to expand...
Click to collapse
Didn't work for me. When I tried the fastboot part, it just sat on "waiting for device". I tried rebooting the phone while it was at that, tried having it in download mode, tried going into stock recovery... nothing I tried got it to move past that.
pathogen47 said:
Didn't work for me. When I tried the fastboot part, it just sat on "waiting for device". I tried rebooting the phone while it was at that, tried having it in download mode, tried going into stock recovery... nothing I tried got it to move past that.
Click to expand...
Click to collapse
I guess I just assume people know how to get to fastboot mode by now. Power off the phone, hold volume down, press power. You're now in fastboot mode. It doesn't matter, I rewrote my tool for root that walks you through each step. Posting it in a minute.
SamuriHL said:
I guess I just assume people know how to get to fastboot mode by now. Power off the phone, hold volume down, press power. You're now in fastboot mode. It doesn't matter, I rewrote my tool for root that walks you through each step. Posting it in a minute.
Click to expand...
Click to collapse
Ah, well, I'm not a developer and I've never had to use fastboot with this phone before so yeah, I was not aware of it. In the past, I always just flashed pre-rooted versions with Odin. Never had to know anything about fastboot.
Never too late to learn.
lollipop
Would like to know if others are having problems downloading the full update from the link on this page. Tried many times, but mediafire keeps indicating a redirect error. Tried other browsers and cleaning cache, but still no go.
Just tested on my tablet. No issue.
Thanks Samuri - the Odin flushable ROM worked flawlessly for me.
Pre-flashing procedures?
After flashing this with ODIN I was stuck in a bootloop (with the 4 twirling dots). After having 4.3 for a long time, I've decided I finally want to update to 5.0.0. I've only ever used ODIN to root and flash recovery, so I've never used it to perform a system update. I was wondering if the culprit could be anything I've already done? I tried the Wipe Data Factory Reset afterwords but it still bootlooped.
Do i need to uninstall busybox/x-posed/unroot?
I don't have my bootloader unlocked but I don't think i need to. Am I wrong?
Do I have to update to 4.4 then to 4.4.4 then flash this for it to work?
I also tried just to see if using adb sideload with the .zip would work but it didn't.
My guess would be a data issue, but, if you said you wiped data and it's still bootlooping it may be something else. Try flashing the image again.
SamuriHL said:
My guess would be a data issue, but, if you said you wiped data and it's still bootlooping it may be something else. Try flashing the image again.
Click to expand...
Click to collapse
Flashing again did indeed work. Thanks man.
Glad it worked. You're quite welcome.
How to flash this update without my previous problem.
I Managed to flash the "philz_touch_6.58.7-jflte.tar.md5" trough Odin, and my phone is now working again.
I'm not sure, but I guess I didn't have the USB Debugging Mode On. Not sure if it was the only problem, probably not.
Before failure procedure I Used to have on the phone: Model, GT-i9505G, Version 5.0, Baseband I9505VJUFNC1, SuperSU, Busybox and Googy-Max STweaks. Don't know any more what kernel was on it.
Now I have:
Same as above, but Googy-Max STweaks dont work because of the Kernel (3.4.0-2809293 [email protected]#1 Fri Dec 5 20:45:08 KST 2014)
Now, what do I need to do, to have a clean and fresh phone to use and root it. Do I need to mess with Kernel and Recovery stuff to get my phone working again?
Thank you!
I'll try to give as much Info as I can for now.
I got a used i9505G. It had the CWM 6.0.4.9 on it, and used to have a ROM with final "NC1" 5.0.0 Lollipop. It used to have a SU installed and some other app on home screen about Kernel stuff, and Knox was already Flagged on boot.
So, after a lot of reading, I messed my i9505G. Tried to flash this ROM. Got PIT error, changed USB Ports, and OK.
After new Odin session, clicking start, in few seconds I got this error copied below.
Now I'm stuck at boot animation.
At download screen, gets stuck with tiny blue bar if I try to flash this.
At recovery i get: (Android System Recovery <3e> - LRX21P.S012.141205
There is another info on recovery screen that says: E:Can't open /dev/blcok/plataform/msm_sdcc.1/by-name/misc (Permission Denied).
Already tried wiping data and cache. (Im not sure if I did it too before the whole procedure when I had the CWM).
I've never messed with kernel, recovery, etc, only messed with Stock Roms on my i9505.
Click to expand...
Click to collapse
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505GUEUDNL3_FULL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> NON-HLOS.bin
<ID:0/013> FAIL! (Auth)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for any help!
Home button problems
I've flashed this after doing a factory reset (a few times now actually.) The same result each time. When it boots up I go through the setup process and everything is fine. If I reboot my phone the home button single click function goes away as does the ability to lock the screen with power. The other functions still work (double click, long press) If I lock the phone the screen turns off but doesn't lock, If I press power or home the screen just turns back on with no lock screen shown.
I do not have that issue. Try factory resetting it after flashing rather than before.

[SOLVED] Weird white bar while booting SM-N910G (Flashing repair firmware solved it)

Past week when I manually rebooted my phone Samsung galaxy note 4 sm-n910g, it never booted beyond Samsung galaxy note 4 screen.
(Tried flashing stock ROM using Odin , it didn't work.
Also tried flashing twrp recovery using Odin, that too didn't work.)
First thing I observed which was never before was white color half bar nearly as if its indicating 50% of something which I still don't know and have searched everywhere on web about it.. Still its unanswered
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone didn't go beyond Samsung note 4 logo. Led kept on blinking light blue to dark for nealy half n hour ..
I removed battery and again checked, result was same .. Thought may be the latest OTA did something. I tried using three finger recovery boot but unfortunately phone didn't boot into recovery. Tried to go into safe mode boot that too didnt work. When I tried three finger download mode , phone did went into download boot.
I downloaded latest firmware for this phone and used Odin to flash it . it successfully flashed and phone rebooted but still with the same weird white bar and didn't go past Samsung logo and led kept flashing ..
I also tried to flash twrp recovery as I wanted to get into recovery so that from there I would atleast clear cache or do factory reset..
Odin flashed twrp but still stuck at same note 4 logo..
If anyone facing or faced this problem? Plz experts kindly make me understand exactly what might be the problem software or hardware which is causing this ..
Its been one week since phone is like this ..it was my daily driver for 1 year ,had my all work data inside it :crying:
omarrph said:
Past week when I manually rebooted my phone Samsung galaxy note 4 sm-n910g, it never booted beyond Samsung galaxy note 4 screen.
(Tried flashing stock ROM using Odin , it didn't work.
Also tried flashing twrp recovery using Odin, that too didn't work.)
First thing I observed which was never before was white color half bar nearly as if its indicating 50% of something which I still don't know and have searched everywhere on web about it.. Still its unanswered
Phone didn't go beyond Samsung note 4 logo. Led kept on blinking light blue to dark for nealy half n hour ..
I removed battery and again checked, result was same .. Thought may be the latest OTA did something. I tried using three finger recovery boot but unfortunately phone didn't boot into recovery. Tried to go into safe mode boot that too didnt work. When I tried three finger download mode , phone did went into download boot.
I downloaded latest firmware for this phone and used Odin to flash it . it successfully flashed and phone rebooted but still with the same weird white bar and didn't go past Samsung logo and led kept flashing ..
I also tried to flash twrp recovery as I wanted to get into recovery so that from there I would atleast clear cache or do factory reset..
Odin flashed twrp but still stuck at same note 4 logo..
If anyone facing or faced this problem? Plz experts kindly make me understand exactly what might be the problem software or hardware which is causing this ..
Its been one week since phone is like this ..it was my daily driver for 1 year ,had my all work data inside it :crying:
Click to expand...
Click to collapse
Download repair firmware with pit file from tsar3000.com and flash in odin with pit file.
Try odin 3.10 its very stable in my opinion i have never any issues with it.
Download and extract the file you will get repair firmware and pit file choose in odin AP for firmware and PIT for pit file
Uncheck autoreboot in odin and check( nand erase all ) and flash HIT START.
Once odin shows pass take out battery and insert again and boot into recovery.
Then do wipecache & data factory reset and reboot.
Report back and tell me how it goes.
Download link
https://www.androidfilehost.com/?fid=24411628330025773
Trex888 said:
Download repair firmware with pit file from tsar3000.com and flash in odin with pit file.
Try odin 3.10 its very stable in my opinion i have never any issues with it.
Download and extract the file you will get repair firmware and pit file choose in odin AP for firmware and PIT for pit file
Uncheck autoreboot in odin and check( nand erase all ) and flash HIT START.
Once odin shows pass take out battery and insert again and boot into recovery.
Then do wipecache & data factory reset and reboot.
Report back and tell me how it goes.
Download link
https://www.androidfilehost.com/?fid=24411628330025773
Click to expand...
Click to collapse
I will report it back in evening . But will it delete my documents and data? Or they will be there if all things go well? Kindly do reply me back before flash process
They will be delete from internal memory for sure.
Not from microsd card.
Trex888 said:
They will be delete from internal memory for sure.
Not from microsd card.
Click to expand...
Click to collapse
Bro tried to download it whole day, getting very slow download speed of around 15 kbps .. Failed to download with three attempts which hardly went past 40 percent..
Data's inside the phone were really important for my work point of view and mostly were saved on phone memory rather than extcard.. Photos and videos were important but I can manage without them but other data's I am concerned :crying:
Can i find same recovery on web with better speed? Same download crisis was there when I tried to download latest stock ROM . I managed to download from updato website.. Previously I searched for samfirm software which then made be find this website on xda about updato . download was smooth..
Also tmrw I am giving phone to service person even though its warranty is expired. If he can't fix it then I will revert back to download link which u provided .
Bro can you tell me what is that half white bar ? Actually what is it related to ,is it software or hardware.. Also I am thinking this all may be due to faulty battery ..if it might be the case
omarrph said:
Bro tried to download it whole day, getting very slow download speed of around 15 kbps .. Failed to download with three attempts which hardly went past 40 percent..
Data's inside the phone were really important for my work point of view and mostly were saved on phone memory rather than extcard.. Photos and videos were important but I can manage without them but other data's I am concerned :crying:
Can i find same recovery on web with better speed? Same download crisis was there when I tried to download latest stock ROM . I managed to download from updato website.. Previously I searched for samfirm software which then made be find this website on xda about updato . download was smooth..
Also tmrw I am giving phone to service person even though its warranty is expired. If he can't fix it then I will revert back to download link which u provided .
Bro can you tell me what is that half white bar ? Actually what is it related to ,is it software or hardware.. Also I am thinking this all may be due to faulty battery ..if it might be the case
Click to expand...
Click to collapse
No idea about white bar never seen anything like it.
Probably its software issue .
Did you flash any rom or kernel before this white bar begin to appear?
Trex888 said:
No idea about white bar never seen anything like it.
Probably its software issue .
Did you flash any rom or kernel before this white bar begin to appear?
Click to expand...
Click to collapse
No modifications were done. It was running on stock Samsung ROM. Not rooted at all and not even Knox was tripped before it .
Few days ago before start of this major problem I can only remember is that I did December update through OTA. It rebooted and android updated . I remember I didn't went into recovery and didn't cleaned cache or anything ,just normal reboot and phone was working . The day when it started I thought I should clean the screen. I powered off phone and with dry cloth cleaned the screen, back panel and battery .. When I turned on phone, first time I saw this bar, phone didn't go past Samsung logo. It was then when I tried to go into recovery, it didn't go to recovery. I tried to safeboot that too didn't work. Only download mode was working . so I searched on internet about it.. I thought maybe update did something so I downloaded latest stock to check. Every thing went smooth and pass msg was on Odin but phone was having same half white bar and didn't go past Samsung logo.
I really don't understand till date what might have caused it . was it update, battery or some hardware issue
If you can flash twrp you can copy all data from internal memory and then follow repair firmware method that i mentioned earlier.
Flash twrp in odin of your model.
Go to mount and mount usb storage.
And connect via usb cable to pc .
Here you can see your whole internal memory & data you can copy to pc .
Make sure download latest twrp recovery otherwise in older versions usb storage will not work.
Hope that helps
Trex888 said:
If you can flash twrp you can copy all data from internal memory and then follow repair firmware method that i mentioned earlier.
Flash twrp in odin of your model.
Go to mount and mount usb storage.
And connect via usb cable to pc .
Here you can see your whole internal memory & data you can copy to pc .
Make sure download latest twrp recovery otherwise in older versions usb storage will not work.
Hope that helps
Click to expand...
Click to collapse
Bro plz don't get annoyed and kindly send link of latest twrp for n910g..
Previously I downloaded from
https://dl.twrp.me/trltedt/
And installed via Odin successfully but couldn't get phone into recovery boot even doing all things . if I could go into it and save data I could have gone for recovery firmware installation without hesitation.
Plz from ur knowledge provide me a link for latest twrp and I will flash and report back bro
omarrph said:
Bro plz don't get annoyed and kindly send link of latest twrp for n910g..
Previously I downloaded from
https://dl.twrp.me/trltedt/
And installed via Odin successfully but couldn't get phone into recovery boot even doing all things . if I could go into it and save data I could have gone for recovery firmware installation without hesitation.
Plz from ur knowledge provide me a link for latest twrp and I will flash and report back bro
Click to expand...
Click to collapse
This is the latest version of twrp that you have.
Flash twrp.tar in odin 3.10 and most important ( uncheck auto reboot in odin options).
Once odin shows pass take out battery and insert again and immediately press (volume up + home + power button ) you should be in twrp.
Trex888 said:
This is the latest version of twrp that you have.
Flash twrp.tar in odin 3.10 and most important ( uncheck auto reboot in odin options).
Once odin shows pass take out battery and insert again and immediately press (volume up + home + power button ) you should be in twrp.
Click to expand...
Click to collapse
I did all things correctly. There was pass msg in Odin yet again. I removed battery and manually pressed vol up, home and power to get into recovery. Phone had msg booting in recovery but after it its blank black screen only bro..
When I am into my computer device manager and still connected phone with USB I can see its there in portable device and also in universal serial bus controllers
Bro OK let's suppose something is not letting my phone to boot up and also recovery mode boot . is it possible that it might be due to corrupt partition or phone memory which is not letting phone to boot up.
Is there any way using my external SD card as a storage where I can install twrp and get into recovery? So that it may allow me to go inside of recovery mode and select USB mount option ? Is it practical ? Can this be done using external SD card? If so plz tell me
omarrph said:
Bro OK let's suppose something is not letting my phone to boot up and also recovery mode boot . is it possible that it might be due to corrupt partition or phone memory which is not letting phone to boot up.
Is there any way using my external SD card as a storage where I can install twrp and get into recovery? So that it may allow me to go inside of recovery mode and select USB mount option ? Is it practical ? Can this be done using external SD card? If so plz tell me
Click to expand...
Click to collapse
Have a look there mate, it might help you : https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
i have downloaded repair firmware file from https://www.androidfilehost.com/?fid=24411628330025773
there are these files inside them.. how do i install them? i have searched on google but only could find steps for using AP but what about other files? do i have to use them and how to kindly guide me steps
Trex888 said:
Download repair firmware with pit file from tsar3000.com and flash in odin with pit file.
Try odin 3.10 its very stable in my opinion i have never any issues with it.
Download and extract the file you will get repair firmware and pit file choose in odin AP for firmware and PIT for pit file
Uncheck autoreboot in odin and check( nand erase all ) and flash HIT START.
Once odin shows pass take out battery and insert again and boot into recovery.
Then do wipecache & data factory reset and reboot.
Report back and tell me how it goes.
Download link
https://www.androidfilehost.com/?fid=24411628330025773
Click to expand...
Click to collapse
i have downloaded repair firmware file from https://www.androidfilehost.com/?fid=24411628330025773
there are these files inside them.. how do i install them? i have searched on google but only could find steps for using AP but what about other files? do i have to use them and how to kindly guide me steps
@Trex888,
i followed the step and installed repair firmware..
First i selected only AP and PIT file.
after odin passed i removed battery and booted to recovery.. Android robot came with RED dead sign.. still recovery booted and i cleared cache and factory reset.
Phone in bootloop..
SO again i went to download mode and selected all other files like CSC, BL and CP
ODIN came with following fail..
d in Odin
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910GDTU1BOE4_CL4980903_QB5063813_REV00_user_lo w_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N910GDD1BOC1_REV00_CL_1905730.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ODD_N910GODD1BOE1_CL4965595_QB5034215_REV00_us er_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to go into recovery but it said firmware failed please connect to kies for recovery..
I went to ODIN and just flashed AP firmware this time and it passed .. Mannually reboooted to recovery it rebooted and then i rebooted phone and now its on stock rom 5.0.1..
Now i dont see any white half bar while booting.. Phone is booting properly and i checked all sound, camera, torch and wifi, mobile data working..
So steps i did were ok or anything i missed or messed?? some thought here please

Categories

Resources