I have looked and tried and still can't fix my bootloop.
I was on Factory 4.3 rooted with towel and had OTA blocked. I need to update to 4.4 for a bluetooth device I have so set superSU to save root and removed the OTA block, although the updates would fail over OTA. I then downloaded the 4.4 NC4 image and used odin to image the phone. No I didn't do any of the recommend pre-imaging because I failed to look up the procedure as I had done other phones in the past.
I am now in a bootloop where it boots into the setup wizard, locks up after 2-3secs and reboot. Over and over. The phone still shows custom after a factory image flash. i've tried every recover from softbrick option I could find and nothing. It boots into setup, freezes, and reboots. Even went as far as erase nand because nothing else worked and the same thing happens.
These images all give me an auth failed: MJE, MI9, MJ7, MJE, NC2. The NC4 image will let me flash, but still results in a bootloop. Again, the lock still shows custom.
Any chance in saving this thing?
I went thru this very same thing just the other day. Go to my post. I posted the link for all the downloads on it. You'll have to Odin flash a complete stock 4.4 Ota. Then you can root with towel root and go from there. Here is the link.
http://forum.xda-developers.com/showthread.php?t=2914890
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Here is the link for all carriers stock files.
http://galaxynote3root.com/galaxy-note-3-stock-firmware/
i think I tried every image, although i'm more then willing to try again. I'll use the link you provided and see what happens.
Thanks for the reply.
Same thing using the image link provided, still in a bootloop, still showing custom/unlocked.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
pretty desperate at this point so i decided to try a flash the nc2kernel ontop of the nc4 as described in some rom hack, i figured what do i have to lose. it did flash, although never made it passed the vzw screen during the boot. i flashed the factory nc4 image to get it back and was surprised to see a android running an upgrade, i was excited for about 3mins until it went right back to the boot loop again with the unlock/custom screen. damn.
still looking for help if anyone has any ideas i'll try them tomorrow.
Calzoniee said:
pretty desperate at this point so i decided to try a flash the nc2kernel ontop of the nc4 as described in some rom hack, i figured what do i have to lose. it did flash, although never made it passed the vzw screen during the boot. i flashed the factory nc4 image to get it back and was surprised to see a android running an upgrade, i was excited for about 3mins until it went right back to the boot loop again with the unlock/custom screen. damn.
still looking for help if anyone has any ideas i'll try them tomorrow.
Click to expand...
Click to collapse
Make sure you have the right PIT file or use KIES.
Sent from my Note 3 via Tapatalk
donc113 said:
Make sure you have the right PIT file or use KIES.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Kies comes back with "phone not supported", the PIT file I'm using is HLTE_USA_VZW_32G.pit which I believe is correct.
I've tried the verizon recovery assistant as well; it goes through the whole process tell me it's repaired and then just go right back into the bootloop, the lock still showing unlocked/custom.
I tired another computer and then another cable as suggested in another thread, still stuck in bootloop.
Calzoniee said:
I tired another computer and then another cable as suggested in another thread, still stuck in bootloop.
Click to expand...
Click to collapse
Have you pulled battery booted into stock recovery and done a factory reset yet?
RomsWell said:
Have you pulled battery booted into stock recovery and done a factory reset yet?
Click to expand...
Click to collapse
Thanks for the reply, yes I have. I have done all the steps to repair a softroot and to restore to factory. The factory restore steps were not tried until the phone was softbricked and stuck in the bootloop.
I called Samsung, they recommend I take the phone to the Best Buy Samsung repair center. I guess I'll try that tomorrow if nothing else works today.
Related
Hello All,
I have a Samsung Note 3 9005 LTE International Edition. It was working fine till I decided to move from 4.3 to 4.4.2.
This is what I did to upgrade my phone.
1. Flash bootloader (as this is needed to move to 4.4.2)
2. Flash latest CWM as per instructions (n9005-cwm-recovery-6.0.4.6-kitkat(0113))
3. Flash a custom rom, started wtih Sweet ROM (after doing full wipe)
After booting I noticed that my phone was repeatedly getting stuck, especially when opening the dailer... If anyone would call me they would hear the phone ringing but on my phone the screen would be black! A few minutes later I would get a missed call notification... Trying to unlock the phone by swiping would randomly cause the phone to hang! In short, the phone had become unusable!
Then I spent many hours on this wonderful forum to see if I had something wrong. I read somewhere that it is advised to flash a Stock 4.4.2 ROM before attemping to flash a custom ROM. Therefore I tried the following
a. Downloaded and flashed a stock 4.4.2 ROM via Odin (N9005XXUENA6_N9005OXXENA5_XEO)
Tested the phone and same issue was persisting. So I did the additional steps:
b. Flash CF Autoroot (CF-Auto-Root-hlte-hltexx-smn9005)
c. Flash latest CWM as per instructions
Test and again same issue. So did the following
d. Wipe data / factory reset / wipe dalvik etc. etc.
e. Flash Custom ROM
I have tried flashing every ROM on this forum for the N9005 but have faced the same issue.
I really really need some help. My phone is unusable. Technically it "works" but hangs again and again and again. I did read on google that 4.4.2 had dialer issues but this is going beyond that. I don't know what to do.
Any help would be greatly appreciated.
Regards,
- Harris
Is it by any chance a Nordic region phone? (NEE) --- If so, I believe @nex7er has solved this issue with NEE region -- Not sure where he has posted the results, but he's the guy you need find.
EDIT: -- Grab yourself a PIT file for just in case -- then in CWM, format your data in /system then reflash your ROM again. - Your PIT file will be handy if you need to redo your partitions due to a corruption somewhere along the line.
radicalisto said:
Is it by any chance a Nordic region phone? (NEE) --- If so, I believe @nex7er has solved this issue with NEE region -- Not sure where he has posted the results, but he's the guy you need find.
EDIT: -- Grab yourself a PIT file for just in case -- then in CWM, format your data in /system then reflash your ROM again. - Your PIT file will be handy if you need to redo your partitions due to a corruption somewhere along the line.
Click to expand...
Click to collapse
It isn't NEE! So that hope is gone
I have tried formatting /system as well but nothing!
iqsoft said:
It isn't NEE! So that hope is gone
I have tried formatting /system as well but nothing!
Click to expand...
Click to collapse
Last thing I can think of is a total wipe out, ODIN tick NAND erase, then with your PIT file, reflash back to complete stock...I have never done this, so you will need to read up to be 100% sure on the method, but if that doesn't fix it, then I am all out of ideas
radicalisto said:
Last thing I can think of is a total wipe out, ODIN tick NAND erase, then with your PIT file, reflash back to complete stock...I have never done this, so you will need to read up to be 100% sure on the method, but if that doesn't fix it, then I am all out of ideas
Click to expand...
Click to collapse
A noob question, where do I get the PIT from? And any guide on how to do NAND erase as this sounds risky
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
iqsoft said:
A noob question, where do I get the PIT from? And any guide on how to do NAND erase as this sounds risky
Click to expand...
Click to collapse
You'll have to have a look around, normally I'd find the link and post but I Hard Bricked myself this morning so trying to fix it
JimmyVD said:
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
Click to expand...
Click to collapse
Hmm, you had no joy at all then after everything?
---------------- This KK update and the Note 3 are becoming a bit of a ballache for sure...
JimmyVD said:
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
Click to expand...
Click to collapse
Yes that is correct, no sound at all! And the baseband would be reset every time I flashed!
This is a total disaster, now I have to get another phone till there is a fix for this!!!
- Harris
iqsoft said:
Yes that is correct, no sound at all! And the baseband would be reset every time I flashed!
This is a total disaster, now I have to get another phone till there is a fix for this!!!
- Harris
Click to expand...
Click to collapse
You could always try the PIT file from the leaked OXX firmware, re-partition/nand erase via ODIN etc see if it works... That is literally last chance saloon though I am afraid.. Well until Official region FW for you comes out..
I don't know about you guys but I'm just as interested in finding out why this happened to me when the flash was successful for so many other people as what I can do to fix it.
I think I'll swerve the nand erase option as it's already pretty much ruined, and I don't really fancy a 600 quid paper weight.
I'll keep an eye on this thread, if we find a resolution we should make an announcement.
JimmyVD said:
I don't know about you guys but I'm just as interested in finding out why this happened to me when the flash was successful for so many other people as what I can do to fix it.
I think I'll swerve the nand erase option as it's already pretty much ruined, and I don't really fancy a 600 quid paper weight.
I'll keep an eye on this thread, if we find a resolution we should make an announcement.
Click to expand...
Click to collapse
Have you nand erased already? how did it go? what did you do for exactly? PM me please.
When you flashed the stock KITKAT and added the file to AP did you tick "Phone Bootloader Update" ? and check your imei if its empty
radicalisto said:
You'll have to have a look around, normally I'd find the link and post but I Hard Bricked myself this morning so trying to fix it
Click to expand...
Click to collapse
Hardbrick eh?
Try the sd card boot.
http://forum.xda-developers.com/showthread.php?t=2531224
This btw
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
flashare 4.4.2 in caso di errori
flashare pit file
erase nand
bl
ap
cp
csc
con N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX
in caso di loop e blocco scritta samsung flashare solo cp e csc
il mio e andato ok pero dispiace non poter flashare al momento cm11
meawww said:
When you flashed the stock KITKAT and added the file to AP did you tick "Phone Bootloader Update" ? and check your imei if its empty
Click to expand...
Click to collapse
Yup did that, phone has an IMEI, infact it does technicall "recieve" calls, though the screen goes blank and nothing is displayed! So the radio is working in theory!!!
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
---------- Post added at 08:05 PM ---------- Previous post was at 07:46 PM ----------
ok gentlemen,
i just tried flashing stock 4.4.2 the 3rd time and now all is fine again.
sound problem is gone and no hangs anymore.
i am not sure what is different, but i try to describe what might have went wrong before
-during odin flash i recognised that phone stuck because it was connedcted to old usb 1.1port. So i unplugged (i thought it was hardbicked anyway, so nothing to loose)
-without restart phone i plugged into correct usb2 hub and startet over with odin-flash of stock 4.4.2
-after odin flash i did not unplug phone during reset, but was waiting for compete reboot after procedure
et voila, it works
here is the odin-log. i have marked the part where i unplugged the phone...
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Set PIT file..
<ID:0/021> DO NOT TURN OFF TARGET!!
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> aboot.mbn
<ID:0/021> __XmitData_Write
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> sbl1.mbn
<ID:0/022> rpm.mbn
<ID:0/022> tz.mbn
<ID:0/022> sdi.mbn
<ID:0/022> NON-HLOS.bin
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img.ext4
<ID:0/022> userdata.img.ext4
<ID:0/022> persist.img.ext4
<ID:0/022> modem.bin
<ID:0/022> Transmission Complete..
<ID:0/022> Now Writing.. Please wait about 2 minutes
<ID:0/022> Receive Response from boot-loader
<ID:0/022> cache.img.ext4
<ID:0/022> hidden.img.ext4
<ID:0/022> RQT_CLOSE !!
<ID:0/022> RES OK !!
<ID:0/022> Removed!!
<ID:0/022> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Added!!
I know this is more nonsense, thant rocket-science. But it did the job unexpecetly good.
So, maybe this helps somebody to overcome the problem.
Same problem for me. Being excited about new trends really pays off, especially on our Note 3. I guess, we'll have to wait for a fix on this. Hopefully, a solution will come soon.
---------- Post added at 03:31 AM ---------- Previous post was at 03:07 AM ----------
fredofuchs said:
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
---------- Post added at 08:05 PM ---------- Previous post was at 07:46 PM ----------
ok gentlemen,
i just tried flashing stock 4.4.2 the 3rd time and now all is fine again.
sound problem is gone and no hangs anymore.
i am not sure what is different, but i try to describe what might have went wrong before
-during odin flash i recognised that phone stuck because it was connedcted to old usb 1.1port. So i unplugged (i thought it was hardbicked anyway, so nothing to loose)
-without restart phone i plugged into correct usb2 hub and startet over with odin-flash of stock 4.4.2
-after odin flash i did not unplug phone during reset, but was waiting for compete reboot after procedure
et voila, it works
here is the odin-log. i have marked the part where i unplugged the phone...
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Set PIT file..
<ID:0/021> DO NOT TURN OFF TARGET!!
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> aboot.mbn
<ID:0/021> __XmitData_Write
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> sbl1.mbn
<ID:0/022> rpm.mbn
<ID:0/022> tz.mbn
<ID:0/022> sdi.mbn
<ID:0/022> NON-HLOS.bin
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img.ext4
<ID:0/022> userdata.img.ext4
<ID:0/022> persist.img.ext4
<ID:0/022> modem.bin
<ID:0/022> Transmission Complete..
<ID:0/022> Now Writing.. Please wait about 2 minutes
<ID:0/022> Receive Response from boot-loader
<ID:0/022> cache.img.ext4
<ID:0/022> hidden.img.ext4
<ID:0/022> RQT_CLOSE !!
<ID:0/022> RES OK !!
<ID:0/022> Removed!!
<ID:0/022> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Added!!
I know this is more nonsense, thant rocket-science. But it did the job unexpecetly good.
So, maybe this helps somebody to overcome the problem.
Click to expand...
Click to collapse
I tried that but Odin seems to always Fail. Did you close your Odin after unplugging your USB? What's the model number of your unit anyway? Hopefully I can have a workaround like that too. *cross fingers*
i did not close odin after unplug the device. just unplugged and plugged-in to another usb-port. then hit "start" in odin.
I am using SM N9005 (DBT)
--> make sure " phone bootloader update" is ticked in odin.
#update #2
just flashed echoe-rom and all keeps running smoothly. no problems anymore.
So at least this is a good sign that the mentioned issue is not a deadly issue
Fixed
Hi All,
My phone is working perfectly now. I have identified the issue:
a. Do NOT ever flash only the bootloader. Flash the stock 4.4.2 ROM instead
b. If you happen to flash the bootloader, then you will need to ensure that you flash the kernel that comes with the stock 4.4.2 ROM. The baseband should be N9005XXUENA2 and Kernel 3.4.0-340325.
its all fixed at my end. Flashing the stock 4.4.2 has fixed it.
Thanks to all those who helped.
- Harris
fredofuchs said:
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
Click to expand...
Click to collapse
Exact same issue here. Problem with anything to do with sound after flashing a custom rom after flashing 4.4 booatloader
Please let me know if a fix is found as Im stuck with an 800 dollar paperweight and using an iphone 4 !!
Hopefully, I'm not posting something that's already been solved a million times--I've spent two days trying to find a fix given in other threads, but...still no luck.
I rooted my AT&T S4 (SGH-i337ucufnc1) successfully, installed Safestrap without any problems. Then, like a genius, forgot to do a wipe for a clean flash...on top of flashing over my stock ROM. Of course, now there is no OS, and I can still put my phone into recovery and download mode, but only the factory recovery--the Safestrap lock and "Custom" screen come up when the phone starts, but it doesn't go past that.
I DID make a backup and tried to recover through Safestrap with it (before restarting my phone and losing access to Safestrap altogether), but that failed, also. I kept/keep getting the "E:failed to mount /system (Invalid argument)". When trying to recover from my backup, Safestrap wouldn't allow me to check the "system" backup.
I've tried flashing the stock ROM and re-partitioning with the stock .PIT, but everything I've tried to do through Odin gives me a failed result.
I'm really hoping I just missed the solution to my problem and it's already been resolved for ten other people because I'm about to just beat my bricked phone with a brick--or myself for my carelessness.
Oh, this is the output I'm getting from Odin on any recovery I try to use:
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You're trying to flash the mdl firmware, it won't work. You need the nb1 tar file
Go here http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're trying to flash the mdl firmware, it won't work. You need the nb1 tar file
Go here http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You are my hero. Thank you
'm on the Sprint Galaxy S4 SPH-L720. I've spent about 10 hours on this - reading and following posts and trying different flashes with no luck. I was on the Pac Man Rom (with CW MOD 11): pac_jflte-dev-20140831.zip (I believe in my phone it showed KitKat 4.4.4) . I was having issues with reception, getting voicemails, and battery, so I wanted to revert to Stock Rom (I think I tried mk2), and ran into problems. I've been trying to flash NAE (and use the NAE pit file) with different versions of Odin, different USB jacks, etc but with no luck. The error messages I get in Odin are:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> 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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And my phone says in red:
Start {224,1440}
Secure Check Fail: PIT
SV rev. check fail : fused : 5 Binary : 4
Click to expand...
Click to collapse
The NAE i'm flashing is: L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5
I really appreciate any help anyone can offer.
You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?
I think you was flash wrong combination of flashable.. Maybe..
Again. Check your flashable..
daniel4653 said:
You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?
Click to expand...
Click to collapse
Thank you for your replies. Daniel4653, I didn't do any OTA updates (I think because the phone was rooted, I couldn't, no?). What is the correct file to flash? I've downloaded a bunch:
SPR-L720VPUEMK2-20131212171424
SPR-L720VPUAMF9-20130626162512
SPR-L720VPUFNAE-20140224205519
L720VPUAMDC_L720SPTAMDC_SPR
I had used an older version of Philz Recovery (philz_touch_6.07.9-i9300.tar.md5) and when I tried a newer version (philz_touch_6.15.6-jflte.tar.md5), I was able to boot into Clockwork Mod. From there I was able to install a custom ROM again. Phew. Also, I know understand that a phone that has Knox installed (0x1) won't work with Odin anymore. See http://forum.xda-developers.com/showthread.php?t=2447832&page=7
After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.
garbage914 said:
After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.
Click to expand...
Click to collapse
If you can mount everything and wipe all in cwm (follow the steps) you can flashing another roms..
But make sure you can doing mount or etc..
Code:
Hi, I have a serious problem with my Note 4 (SM-N910F).
Since the phone where lagging a lot from a few days, yesterday I choose to do a restore to factory condition, but after that it begun to bootloot.
So I flashed the latest 5.11 firmware available (this from Sammobile for Italy.
As soon as I did, I thought that all my problems were gone, but no. After the firmware, I wanted to get root, so after a quick search on Internet, I choose to get this kernel.
But after the flash of the kernel, I begun to have A LOT of problem. So I decided to flash again only the firmware.
Today I tried again to flash the TWRP recovery to flash the kernel .zip to get the root, but as soon as I did it, the phone didn't go beyong the Samsung logo.
I tried to take these steps: firmware-recovery-root, but after a while, ODIN gave me the error of "PIT binary missing" (or similar).
So, I downloaded a .PIT file for the 5.1.1 (I don't remember where) and I reflashed the firmware with the .PIT file and I didn't got any errors.
After I checked that there were no problems, I tried again to install that kernel.
And I tried again, and again, with different 5.1.1 firmwares.
A thing that I think it's important, it's that I noticed that sometimes while powering on the phone, it went automatically to Download Mode, with a message saying that it couldn't boot in "normal mode" and "MMC read error".
Also I noticed that everytime a powered off, or I rebooted the phone, I had to take off the battery in order to turn on again the phone. It seems like the phone never really turns off.
Now, the phone doesn't boot, the recovery isn't working, and the only thing I have is the download mode.
I tried on 2 pcs, with 2 usb cables, with 2 ODIN versions (3.09 and 3.10.6) to flash a couple of 5.1.1 firmware with and without the .PIT file.
Every time I start the flash on ODIN, while flashing the SYSTEM.img, the flashing stops and on the phone I get this message "ODIN: flash write failure".
I don't really know what to do, unless took it to a warranty center. I think that this problem could be caused by a faulty EMMC, or a brick caused by me.
PS: this is the log from ODIN
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COH4_N910FITV1COH1_N910FXXU1COH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>[COLOR="Red"] FAIL! (Write)[/COLOR]
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE:
I successfully installed the TWRP recovery (twrp-2.8.6.0-trltexx.img.tar) with ODIN, so I wiped all the partitions but one: SYSTEM. The error is "E:Unable to mount '/system'.
At this point I think I messed up with the partitions.
UPDATE2:
I installed the CWM PhilZ, and with that I formatted the /system partition.
So I tried to re-flash the firmware with no success, but I tried again with the .PIT file and it succeeded!
Do you think I should retry to root it?
UPDATE 3:
So, after the first setup (google account, samsung account, time, etc.) I turned the phone off to insert my SIM card.
But as soon as the smartphone turned off, it powered on itself again in Download mode, showing me this error:
Could not do normal boot.
ddi : mmc_read failed
I think that maybe, there's a problem with the eMMC
Hi there
Do you want to flash the firmware?
i have s6 edge and when i choose file(in odin) for (PA) it falis so i tried for (CSC) and it worked.
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
landerhazard said:
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
Click to expand...
Click to collapse
i had a simialar problem with odin but my problem was that the adb wasnt successful i had to do it twice before it said successful then when i ran odin it worked not sure if this will help but i was stuck for days with the odin fail it was frustrating but good luck hope you find a solution
I have spent the better part of two days searching for a solution with no avail so I thought I would post up what I see and determine if someone else has found a solution (I have found similar posts with either no answers or successful outcomes).
I was on OG5 and kept postponing the OTA update (phone was stock, not rooted as I received it with OE1 on it and eventually took the OG5 update since the bootloader was already locked). Last week I fell asleep and forgot to plug in my phone, and when I woke up the battery was dead. When I plugged it in I got the bootloop (without the RECOVERY BOOTING banner at the top). I have Odin 3.09, and have tried flashing different images including just the ROM, the ROM & recovery, etc, as well as the full factory image with the bootloader included. If I try to flash anything with a bootloader in it older than OG5 I get the error (as expected). However, all flashes end up in the blue "RECOVERY BOOTING...." loop. If I force it to recovery I get Maintenance Recovery and not the full factory recovery so that i could clear cache and Dalvik (as many have suggested). Basically, I'm trapped when trying to boot into regular recovery and cannot get there. Even tried repartitioning when flashing, all to no avail.
I saw a thread somewhere a couple days ago back on something with two phones (known good, another with issues) and a way to recover the dead one with the help of the other, but have not been able ot find it since.
Can someone hopefully provide me counsel on how to either fix what I am seeing or perhaps to the other thread as I have access to a working S5 with OE1 on it that I can use to make any custom image and/or something to help out? Below is my output from Odin - appears to work every time it flashes anything that doesn't contain a bootloader older than OG5:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU2BOG5_G900VVZW2BOG5_G900VVRU2BOG5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This is conjecture, based on what I've read recently.
I believe what you're asking about is the Unbrick image, but my understanding is that is only needed when you are not able to get Odin to recognize that your device is even a phone. In any case, you would need to use one that matches the firmware and bootloader version of your phone.
Your Odin output reports that it IS connecting to the phone, that factory image md5 is valid, and that it is flashing successfully.
You cannot downgrade below BOE, but you can always go up. Maybe try using Odin to flash the BOK3 image linked in this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Update 2/1/2016
Well, I was fed up last night and left the phone in the boot loop as I headed off to bed (watched it boot loop about 10 times). Woke up Sunday and it had booted up and was running with all the data intact, even after I had tried to do a Factory Reset from the Maintenance Recovery menu. Got curious, powered it down and it it boot looped a couple times (without the RECOVERY BOOTING banner) and then came up ... after that it seemed to be OK as later in the day I powered it down a couple times and it came up fine.
Thanks for the reference @painiac - I was able to flash either OK3 or OG5 with success from Odin (the full factory images) but behavior was the same.
I got curious and tried to boot into recovery this morning and now it's boot-looping again - sigh... Was going to let it run the battery out trying to boot and after about 12-15 loops it finally came back! Hopefully the patience theme seen above may help others who are in the same scenario as this phone never seems to boot into standard recovery even after flashing full factory images.
At this point, I am planning on (hopefully) getting it booted up one last time, copying all my data off of it, and then walk into Verizon and try to get an exchange as this is not normal behavior and smells to me a bit like a hardware issue but my searches have determined that I am not the only one with this issue - HTH someone...
I agree, it's probably a hardware issue because a fresh factory image should have wiped out any problems that would be causing a bootloop. That combined with the fact that the problem persists across different version flashes.