Related
The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1
griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.
Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.
griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.
Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?
Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.
Hey everyone.
I'm helping fix my friend's GS3 (SGH-i747). He said that he ran out of battery, and then went into a bootloop. He's running on one of the CM Nightlies from a while back.
We've tried to wipe cache, dalvik cache, factory reset, etc, but nothing works because internal storage fails to mount. I've tried flashing stock via Odin, but with no success. When I flash a recovery however, it says it was successful but when I boot into the phone, I still have the old recovery.
The phone is on TWRP. When I go into "mount", internal storage is shown having 0mb. I cannot click on anything else (data, cache, etc) except system and external sd card (when it is present).
I've tried flashing the CM zip that was on the external SD card but had no success either.
No idea what to do from here. Any help would be appreciated. Thanks!
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
!
audit13 said:
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
Click to expand...
Click to collapse
I get "NAND WRITE START!!" and then FAIL. It shows that the phone is connected to my PC. I've tried flashing CWM. It says it's successful, but when I boot into recovery, the recovery is still TWRP.
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
audit13 said:
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
Click to expand...
Click to collapse
I kinda figured that too. I tried flashing a pit file for the sgh-i747 16gb alongside a stock ROM but nothing happened. How should I go about finding one for the phone?
Btw, the internal storage was already at 0mb before I tried flashing a pit file.
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I'd try it but I don't have access to a 16GB or higher SD card. How do I go about getting a pit file for the phone?
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Thanks for the link. To be sure, I flash this along with a stock rom right? Is there a specific stock rom that I have to use? I got one from Sam Mobile.
audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Here's the log in Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.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> 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
That's what I usually get.
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
audit13 said:
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
Click to expand...
Click to collapse
Should I flash stock 4.3 then? Unless this phone has Kit Kat (I think the CM version my friend was using is Kit Kat)
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Pretty sure that I had put Stock 4.3 at one point. Thanks for the info, I'll try finding a stock 4.3 for Odin and report back.
audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Okay so I tried flashing stock 4.3 and Odin fails at system.img.ext4
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I747UCUEMJB_2024954_REV04_user_low_ship.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> 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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
I got the stock 4.3 from here: http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/
I tried the .pit file included in that as well as the .pit file from the other thread you linked.
Also, the phone was on CM11 4.4.2 before all of this happened. No idea if that makes a difference, but if I recall correctly, the phone did have stock 4.3 at one point.
If you manage to get the thing booted then you might want to run a memory test to see if all the nand is still good
Did you check re-partition?
audit13 said:
Did you check re-partition?
Click to expand...
Click to collapse
Yep
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
audit13 said:
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
Yep, I downloaded that exact one and I get the error. What should I do now?
i have a Samsung S4 that i bought from a friend of mine couple weeks ago. It was working fine until recently it starting doing this:
https://www.youtube.com/watch?v=ZjJH...=youtu.be&hd=1
As you can see it boots up but doesnt go to the main screen and then restarts. I hard resetted it. I tried to install stock rom using odin but i get an error and it fails. Its a Samsung M919 from tmobile. I have no idea how to fix it. I tried different battery but same problem. I would really appreciate some help.
i downloaded the rom here: http://galaxys4root.com/galaxy-s4-stock-firmware/
this is the error i get with Odin. I tried different usb cables and computers but same error
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/017> Removed!!
Thanks
can somebody please help
You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.
PanchoPlanet said:
You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.
Click to expand...
Click to collapse
thx for your reply. So i got Odin 3.07. Is this stock rom u talking about: http://samsung-updates.com/device/?id=SGH-M919. So all i have to do open ODA and put this into PDA and start?
i thought stock meant going back to the origal firmware wht the phone came with which would be androind 4.2?
also is there a better download link where i dont have to wait 6 hours?
thx
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
whts the difference between NK2 and NH7?
thx for all your help so far
PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
it failed again.
i followed all your steps:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<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> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Where you able to do a factory reset?
Can you access recovery stock /custom?
What rom was running on phone before first flash attempt?
Was phone running properly when you got it?
You sure it's a t-mobile version M -919?
What color is the phone?
Pp.
PanchoPlanet said:
Where you able to do a factory reset?
YES
Can you access recovery stock /custom?
Not sure what you mean?
What rom was running on phone before first flash attempt?
I have no idea as i am not into flashing or installing "roms"
Was phone running properly when you got it?
Yes
You sure it's a t-mobile version M -919?
Yes as it says on the back of the phone
What color is the phone?
Black
Pp.
Click to expand...
Click to collapse
....
If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.
PanchoPlanet said:
If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.
Click to expand...
Click to collapse
I see stock recovery and i already tried wipe data/factory reset many times but same problem
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om
x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)
Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...
Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.
x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?
1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting
1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<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)
Yet I am still getting the same issue: rebooting about every minute to being turned on
koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode
Updated main
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
I am having a very similar issue, can't seem to figure out how to fix it.
x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...
x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<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)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?
Hi all,
I am failing to flash anything I try to, with the errors you can see in the screesnhot.
Odin fails as well on everything with
Complete (write) operation failed.
Any suggestions?
Thanks,
Kmosh.
Dunno because I can't tell what you're trying to do to?
From that snapshot, it looks like you're trying to flash something in stock recovery. Stock recovery only allows verified OTA to flash manually so it rejects it. Are you trying to flash a zip from sdcard in stock recovery?
A snapshot of phone when Odin fails might help. Does it say something like rejected by R/L? That would mean you have reactivation lock enabled in Settings/Security. Boot system, unlock lock-screen, open Settings and unlock it.
A snapshot of Odin log would help too. What are you trying to flash? Did you verify md5 against the zip when you downloaded (zipped re-uploaded tar.md5 usually include a md5 to check)? Did you drag the tar.md5 of the zip to folder after right click/show archive? Which stock tar, tar.md5, img.tar or root are you trying to flash in Odin?
Regarding the questions above, you can only Odin stock tars for Android 5.1 and 6.0+ if your bootloader is updated past Android 5.0
So there are limits to what and where you can flash. It's not clear what you're doing so I need more input if my reply doesn't help any.
Make sure your reactivation lock is unlocked, enable USB debug in engineering mode. Make sure Samsung USB driver for PC is installed. Use stock USB cable if possible but any certified cable with data lines should work. Make sure you see COM added in Odin when you USB connect to flash (before you start flash). And watch Odin log and phone screen for errors.
If you're truly stuck and can't flash anything, you may have wiped system while reactivation lock was enabled (this only applies to newer bootloader on Android 5.1 and up). This trips and activates factory reset protection. If you suspect that happened, you need to Odin the update the phone was on before you wiped. You will need to sign in with same Google user and password that was registered before the wipe during setup wizard.
Another workaround that once worked for issue above was to flash Chainfire Auto Root for Note 4 and auto reboot. Depends on if OS was actually wiped though. Won't boot without OS.
Sent from my SM-N910P using Tapatalk
Hi samep,
My problem is that the phone is locked and I can't unlock it.
so getting into settings or whatever inside the phone is not possible.
I've just tried to flash N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar using Odin, and got the below -
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
getting the below on the device, and it is freeze up
kmosh said:
getting the below on the device, and it is freeze up
Click to expand...
Click to collapse
I could be wrong but it looks like you're on an older bootloader that doesn't include the reactivation lock.
But it's not rooted and not writing because it encountered an eMMC error.
Correct? It's covered under factory warranty or other warranty? I wouldn't advise rooting or further flashing but return for replacement immediately.
IMO, the eMMC failure on Note 4 is all too common. It's been known to happen when flashing or taking an OTA. I wouldn't recommend volunteering that you tried to flash it though. Just say it failed on OTA update.
Sent from my SM-N910P using Tapatalk
Thanks samep,
I do not live in the US, and the phone was sent to me as a gift.
So actually at this point it is just a brick for me, tho fully working, just locked with fingerprint and code which I can't obtain.
I don't mind trying anything that will give me access to the phone and use it, even by deleting everything.
would you suggest re-partition?
It may have the earlier version of reactivation lock on it. In that case, the OS is still intact but you run the risk of tripping an efuse fixing this with Odin.
Given what you replied with, the registered fingerprints are unknown and the backup password is unknown as well? The person gifting that gem must have a sense of humor. It would be best if the original gifter could forward the backup password. Once in the Settings, disable the reactivation lock in Security, remove the user accounts and factory reset within Settings before trying to do anything with it. (If the phone was setup in advance to use on your carrier, don't factory reset).
I can't help any further but if you'll Google Factory Reset Protection, you may find blog posts and YouTube videos showing how to get past that with OTG and downloads.
FWIW, I don't think Sprint phones make good gifts nor should they be considered easily unlocked to use on another carrier. Sprint OS and Samsung's regional lock are other obstacles to consider. But it's not within my knowledge base to say for certain how bad things actually are. It has been done. I welcome another's help in this thread.
Sent from my SM-N910P using Tapatalk
kmosh said:
Hi samep,
My problem is that the phone is locked and I can't unlock it.
so getting into settings or whatever inside the phone is not possible.
I've just tried to flash N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar using Odin, and got the below -
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You have to install a newer version of bootloader. Odin in the latest firmware.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
Thanks planb234, but it didn't help. same results.
seems the device is write protected. can't flash anything, or adb sideload anything as well.
kmosh said:
getting the below on the device, and it is freeze up
Click to expand...
Click to collapse
I have this exact issue. The internal storage chip has physically failed. It happens due to our phone heating up and causing damage to the emmc and over time it will meet its demise.