Related
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Bring to tmobile show Em it won't boot. New phone in mail 2 days later. Just did it last week
Sent from my SM-N900T using Tapatalk
Unfortunately I'm not in the US and I don't have t mobile so warranty replacement won't be so easy.
brinks said:
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Click to expand...
Click to collapse
Did you have any luck acquiring a signed PIT file? Any help is appreciated.
Sent from my SM-P600 using XDA Premium 4 mobile app
NJAZ said:
Did you have any luck acquiring a signed PIT file? Any help is appreciated.
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
None so far.
I'm not seeing any PIT files that will flash under the 4.4.2 bootloader.
brinks said:
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Click to expand...
Click to collapse
Did you ever try using Odin 3.7? I for some reason can flash the PDA file but I have a different PIT file which obviously seems not to work... I think I just need the correct PIT file but am unsure where to get it for 4.4.2... This new update has been a nightmare..
coldcrush390 said:
Did you ever try using Odin 3.7? I for some reason can flash the PDA file but I have a different PIT file which obviously seems not to work... I think I just need the correct PIT file but am unsure where to get it for 4.4.2... This new update has been a nightmare..
Click to expand...
Click to collapse
Yeah, I tried odin 3.7, 3.9 and hemidall. Same results, secure check fail: Pit
Update: Looks like there are two versions of the 4.4BL, the latest of which checks for a signed PIT file. It won't work to flash any 4.4 pit from say, a few months ago. Need a PIT fie from someone who updated their phone in the last 2-3 weeks.
*** Nevermind, after a third Odin flash it worked.
Same thing happened to me, stuck on "BOOTING RECOVERY". Any resolution to this?
No solution that I've found. I've tried flashing multiple SM-N900T pit files found on XDA, all return the SECURE CHECK FAIL: PIT error. The phone will not boot into the stock recovery and returns the RECOVERY IS NOT SEANDROID ENFORCING error with custom recoveries. I've tried the latest versions of TWRP, CWM, etc with the same results.
As this update isn't really out in the wild recently I'd say that updating to 4.4 OTA is a pretty big risk at this point.
Hello everyone. I currently own a T-Mobile Samsung Galaxy S3 SGH T999. For some reason I can't flash in TWRP. When I flash a new ROM it says " Failed MD5 check MD5 file missing" How do I go about to fix this?
Disable md5 check in twrp
I tried that it still doesn't work.
And what happens?
It says the same thing.
Make sure it's the latest version of twrp, if that doesn't work use cwm
How do I update TWRP?
Through Odin, or an app like flashify
Hello everyone, I am in need of some help.
I tried to update my l900 mk4 rooted to NE2 yesterday and it failed and left me in a situation.
My bootloader got updated to NE2 but everything else stayed as MK4.
My issues is when I try to ODIN flash a stock MK4 tar, I get an error Binary:3 Device:2.
After research I getting that everything needs to match up I'm guessing. (I could be wrong)
So what I am needing is a MK4 bootloader to flash via recovery or ODIN or a way to get everything to NE2 (I just need them matching)
Someone has uploaded a MK4 bootloader tar (I cant find the link) but is does not work with ODIN.
If I am completely wrong about all this please chime in, I'm not developer and could have misinterpreted my research.
My status right now is a very early, dirty flash of CM11 (I had a backup) that will not update with nightlys via updater giving MK5 checksum verification error. I am assuming this is related.
Josh
cgi2099 said:
Hello everyone, I am in need of some help.
I tried to update my l900 mk4 rooted to NE2 yesterday and it failed and left me in a situation.
My bootloader got updated to NE2 but everything else stayed as MK4.
My issues is when I try to ODIN flash a stock MK4 tar, I get an error Binary:3 Device:2.
After research I getting that everything needs to match up I'm guessing. (I could be wrong)
So what I am needing is a MK4 bootloader to flash via recovery or ODIN or a way to get everything to NE2 (I just need them matching)
Someone has uploaded a MK4 bootloader tar (I cant find the link) but is does not work with ODIN.
If I am completely wrong about all this please chime in, I'm not developer and could have misinterpreted my research.
My status right now is a very early, dirty flash of CM11 (I had a backup) that will not update with nightlys via updater giving MK5 checksum verification error. I am assuming this is related.
Josh
Click to expand...
Click to collapse
You cant downgrade bootloader without causing issues. Also you don't have to have bootloader, rom, and radio versions match. I am on ne2 bootloader running mk4 rom with the ancient lj1 modem. Not sure what your cm11 issue is not mismatch of versions. You can flash the full ne2 tar with odin if you want but cant go backwards with odin.
Sent from my XT1045 using XDA Premium 4 mobile app
Ah, I see now. So basically the only TAR I can flash is either a NE2 or NK2?
I guess I have something else going on with CM11 and CM12. I cannot update CM11 at all and if I try to flash CM12 I get a boot loop. None of this happened till I tried to upgrade from MK4 to NE2.
Not sure how to fix it, I'm stuck on a Dec of 2013 CM11 rom. Every NE2 TAR I download, both my computers say they are corrupt (I'm thinking it might be a windows 8.1x64 issue)
If you go to androidfilehost.com/dev/jlmancuso and search around you will find a copy of the ne2 tar I uploaded. It should download better/faster. Hopefully it will help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
If you go to androidfilehost.com/dev/jlmancuso and search around you will find a copy of the ne2 tar I uploaded. It should download better/faster. Hopefully it will help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
www.androidfilehost.com/?fid=23501681358546202
cgi2099 said:
Ah, I see now. So basically the only TAR I can flash is either a NE2 or NK2?
I guess I have something else going on with CM11 and CM12. I cannot update CM11 at all and if I try to flash CM12 I get a boot loop. None of this happened till I tried to upgrade from MK4 to NE2.
Not sure how to fix it, I'm stuck on a Dec of 2013 CM11 rom. Every NE2 TAR I download, both my computers say they are corrupt (I'm thinking it might be a windows 8.1x64 issue)
Click to expand...
Click to collapse
Much appreciated.
When I load this into ODIN 3.07 I get a MD5 hash error, and when I load it into ODIN 3.09 I get a binary invalid error.
Josh
You can also get it from here http://samsung-updates.com/device/?id=SPH-L900 , but it will take a long time to download, this is where I downloaded mine from and its worked fine for me many times using odin 3.09.
Hi,
Couple days ago, I decided to root my unused android phone. Everything was working great. Yesterday, I had a OTA update file. I pressed cancelled/put it on hold, but when I woke up this morning, i see my phone installing 29% with the samsung logo, then it said failed. It would be loop this over and over again. I managed to get access to recovery boot using flash rom. I wiped my cache, full factory reset. Now, it just reboots and keeps on entering recovery mode. I did not know that even after wiping data, my phone is still rooted. I tried unrooting using this method using a MD5 file. I couldnt link the site, but I used this method ""[Guide UPDATED] How to Unroot your AT&T Galaxy S3 (Return To Stock I747UCDLK3 JellyBean )""' but it said failed when I tried to write the flash rom onto the phone. Is my phone completely done? How can i fix this? Please help. Thank you
My s3 is an AT&T variant. SGH-I747
What bootloader was on the phone before the OTA update?
You could try flashing a custom recovery and then flashing a custom ROM. This should at least get your phone booted.
audit13 said:
What bootloader was on the phone before the OTA update?
You could try flashing a custom recovery and then flashing a custom ROM. This should at least get your phone booted.
Click to expand...
Click to collapse
Sorry, I am not really sure. I am new to this. Is there a way to check? My phone was stock. I did a full factory reset before I rooted the phone. Next day, it try auto updated and here I am now.
Do you have a custom rom you recommend?
I managed to flash the CWM recovery into the phone, but when I tried to flash a custom rom which is stock rooted, it says failed. Even with CWM on the phone, I can only access CWM recovery or download mode. Restarting phone loops CWM recovery
<ID:0/005> Odin engine v(ID:3.1005)..
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does cwm have a built in terminal emulator like twrp? If so, use it and enter this:
getprop ro.bootloader
If it is a newer version, it is probably why Odin is failing. (Depending on the version it may also explain why it won't flash your custom rom. What error does it show when it fails BTW? ) If it is not, make sure kies is NOT on your computer. Try a different USB cable and USB port.
Also, What version of cwm are you using and what rom did you try?
Sent from my SGH-T999 using Tapatalk
Looks like you are using Odin to flash a custom ROM which cannot be done. Use CWM to flash the custom ROM.
DocHoliday77 said:
Does cwm have a built in terminal emulator like twrp? If so, use it and enter this:
getprop ro.bootloader
If it is a newer version, it is probably why Odin is failing. (Depending on the version it may also explain why it won't flash your custom rom. What error does it show when it fails BTW? ) If it is not, make sure kies is NOT on your computer. Try a different USB cable and USB port.
Also, What version of cwm are you using and what rom did you try?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I am using CWM 6 touch. I tried flashing the stock rom from sanmobile but it keeps failing. My odin version is 3.10.7. I am trying cwm flashing now.
Edit: There's only an option to flash from a zip file so I kept my stock rom in a zip filed. Tried it and it says can't open file. Aborted
Oh OK, you're referring to the stock firmware. Sorry, I'm used to differentiating between the two. Stock firmware is what you are using, and I've always considered stock rom to be just the system and kernel like custom roms.
Odin is primarily just for flashing the full stock firmware. You cannot flash that in recovery. You'll need to figure out exactly what build you were on previously by using the terminal emulator command I mentioned before. If cwm doesn't have a built in terminal emulator, you can flash twrp instead and use it.
I suspect you may be on a newer build than LK3, which may explain why odin won't flash it.
I do not suggest trying to flash a custom rom at this point. If any part of the base firmware was corrupted due to the incomplete ota, it is possible for it to hard brick if you try to boot into the system before flashing it correctly. This is still possible no matter what you try to do. It just depends on where the OTA failed. with a little luck this won't happen, but I thought you should be aware of the possibilty anyway.
The safest way to proceed is to first find out exactly what build is on the device. Then we will be able to determine what you should be trying to flash and how.
I hope I'm not confusing things even more for you BTW! If you need anything cleared up just let us know.
Sent from my SGH-T999 using Tapatalk
I have flashed the newest twrp onto the phone. Is the terminal emulator the "terminal command"? How would I check which build am I on?
Sorry, really new to this.
Yes, that's it. I think you might need to select a folder or something, if so just stay at the root directory. At the command line, enter
getprop ro.bootloader
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Yes, that's it. I think you might need to select a folder or something, if so just stay at the root directory. At the command line, enter
getprop ro.bootloader
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It gave me I1747UCUFNE4
Ok, it sounds like it's updated at least partially to NE4. You cannot flash anything older than that which is why you couldn't get Odin to work.
Your best bet is to go to enewman17's thread for NE4 and flash following his instructions. This will finish what the OTA started and should fix the device.
http://forum.xda-developers.com/showthread.php?p=53984772
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Ok, it sounds like it's updated at least partially to NE4. You cannot flash anything older than that which is why you couldn't get Odin to work.
Your best bet is to go to enewman17's thread for NE4 and flash following his instructions. This will finish what the OTA started and should fix the device.
http://forum.xda-developers.com/showthread.php?p=53984772
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
How do I flash the zip flash? I unzipped and did not see any files I can load on odin. I tried using external sd on twrp but it failed. This is what it said.
Checking for MD5 file..
Skipping MD5check: no MD5 file found
assert failed: getprop("ro.bootloader") == "I747UCALEM"
[] getprop("ro.bootloader") == "I747UCALG1"
[] getprop("ro.bootloader") == "I747UCDLK3"
[] getprop("ro.bootloader") == "I747UCDMG2"
[] getprop("ro.bootloader") == "I747UCUEMJ2"
[] getprop("ro.bootloader") == "I747UCUEMJB"
E: error executing updater binary in zip '/external_sd/d2att_I747UCUEMJB_bootloader_modem_4.3.zip'
error flashing
updating partition details...
done
I think you got the wrong one. That says you are trying to flash MJB. You need to flash the NE4 bootloader/modem package, and probably the system/kernel one too.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I think you got the wrong one. That says you are trying to flash MJB. You need to flash the NE4 bootloader/modem package, and probably the system/kernel one too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I have just tried the NE4 file on twrp, it gives me a
Checking for MD5 file..
Skipping MD5check: no MD5 file found
assert failed: getprop("ro.bootloader") == "I747UCUEMJB"
E: error executing updater binary in zip '/external_sd/d2att_I747UCUEMJB_bootloader_modem_4.3.zip'
error flashing
updating partition details...
done.
Not sure what is going on
Can you give me the link you used to download it. I'll download and take a look at it. (I'd go get it myself but I want to make sure I am getting exactly the same thing you got.)
Sent from my SGH-T999 using Tapatalk
I got it from the link you posted about enewman17's thread. It has the MJB link for precaution and the NE4 link. I downloaded both them. Tried both and it gave me those 2 messages as you see
Not sure if I can post links yet.
The MJB one
http://www.androidfilehost.com/?fid=23269279319197285
The NE4 one
http://www.androidfilehost.com/?fid=23501681358559161
Are you sure you didn't accidentally download the wrong one? Double check the file name if you would.
The reason I am asking is because according to the log you posted above, it's trying to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip
That file can't be flashed because it is older than your current build, NE4.
Sent from my SGH-T999 using Tapatalk
File name for the MJB I have in my download folder:
d2att_I747UCUEMJB_bootloader_modem_4.3.zip
NE4:
UCUEMJB_to_UCUFNE4_Firmware_update.zip
I just noticed you said i am using an old file. Could you link me to an updated file? I downloaded everything exactly in the first page of that thread
Ok, do not flash the MJB package or it'll make things worse. You're device says it's already on NE4, but because the OTA failed part way through, we can't be sure what exactly got flashed. This means you need to reflash only the NE4 package to rewrite the firmware so we can be sure of what is on the device.
I just took a look at the NE4 file though, and as-is, it will not work because it doesn't write the full modem. Instead it patches the MJB modem to bring it to NE4. Since you may not have the MJB modem, this cannot work.
I'll try to redo that portion so instead of patching MJB, it will flash the full NE4 modem. Doing it this way should work. I'm going to shoot a pm to enewman17 too. We did have some issues with NE4 and i want to make sure we don't make things worse! The NJ1 and NJ2 packages include the full modem, so since those are confirmed working we can probably use the script from there with the NE4 files.
I will work on that while waiting to hear back from @enewman17.
I am sorry for not being more clear on what to flash earlier. I know this is probably getting a bit frustrating by now....
Sent from my SGH-T999 using Tapatalk
---------- Post added at 06:22 AM ---------- Previous post was at 05:33 AM ----------
Well it looks like he already had one!
From this post in one of his NE4 threads: http://forum.xda-developers.com/showpost.php?p=55206211&postcount=268
This is the package linked to in that post: https://www.androidfilehost.com/?fid=23578570567720263
So download that file. ( d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip)
Also download the stock/rooted system and kernel package (I747UCUFNE4_Stock_Rooted_3-31-15.zip):
https://www.androidfilehost.com/?fid=24052804347765735
Flash the bootloader/modem first, then flash the stock rooted zip. (Don't reboot between them)
After flashing both reboot. Hopefully everything will be working again!
Now reboot twrp and flash the NJ1 file.
Reboot
Do the same for NJ2
This will leave you with NJ2 as your base firmware and modem. The Android O/S will still be NE4. You can download and flash the NJ2 system to be fully up to date!
If you plan on flashing a custom rom, don't bother with the NJ2 system. You can go straight to flashing whatever rom you want instead.
let me know if I wasn't clear on anything or if you have any questions.
Sent from my SGH-T999 using Tapatalk
I flashed both the bootloader and stock rooted files onto the phone. The phone finally booted to the OS. I am now on the NJ1/NJ2 step. Where could I find these 2 files?
My phone is broken. I rooted it and then installed a custom rom. After that it kept on randomly rebooting. I Then tries putting it back to stock with an md5 file, but it failed half way through. Now it just says firmware upgrade issue. Use recoverymode in kies. I tried but it says my phone is not supported. Now I keep on trying to install ota firmware updates but they keep failing. Please help get my phone up and running asap
Also telling me there is no pit binary
Go here to grab the zip file. Unzip and odin the tar file to bring your phone back.
That did not work it said auth fail
using a different kernel it succceeded
red2481 said:
using a different kernel it succceeded
Click to expand...
Click to collapse
For future reference. When this happens and Odin fails to flash official software you first need to make sure you odin the same software version that is currently running on your phone. If that fails then you can flash the stock unrooted kernel that matches your current software. Another tip, major software update's tar packages will include a sprint pit file. So if you are stuck and unable to flash the stock software with odin then try the first things I mentioned first and if that fails then odin an official rom tar that includes the sprint pit file. (incremental monthly security patches usually do not contain a pit file. Only the first release of a major update will include a pit) The tar packages do check the current kernel so that's the first thing you want to get back to stock when odin fails to flash stock software. I posted this for reference incase others have this problem in the future.