Develop Bugs

Boot loop frozen ??

I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?

nerys71 said:
I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?
Click to expand...
Click to collapse
That screenshot is due to her having stock android recovery, not custom recovery. The link you sent is good to Odin. Dave the tar to your computer, put computer in download mode, flash tar. Good luck...btw, you said s2, make sure it's epic 4g touch before you flash that sucker(sph-d710).
Sent from my SPH-D710BST using xda premium

Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?

nerys71 said:
Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?
Click to expand...
Click to collapse
Lol....I believe there is. I know there was for ICS. It was a zip called otakill I believe. Flashing that stock rom should be fine. And if she had custom recovery before, and ran an update, it flashed over the custom, that's what I would think . You have to partition between gb and jb custom roms, but that rom you are flashing should be fine. If you run into issues, let me know. Good luck.
Sent from my SPH-D710BST using xda premium

ok got the file downloaded. phone in download mode. open one click. plug in usb cable. got yellow box 0:[COM25]
click start and I get this and it just stops
<ID:0/025> 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/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> cache.img
I know its a big file but even if we assume usb 1.0 speeds it should be done by now. how do I know if its working or not? how long should it take?

You are flashing an entire jb stock ROM..it takes a little bit. I would give it awhile. And the last time I flashed a one click it didn't take the first time. If it doesn't take after a considerable amount of time, say 10 minutes, download the tar again, and try the new download. Sometimes you get a bad download, but pc Odin a Rom takes a bit, be patient
Sent from my SPH-D710BST using xda premium

its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.

nerys71 said:
its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.
Click to expand...
Click to collapse
Hmmm...that's odd. Maybe you need to start from scratch, stock unrooted, before you try to flash rooted. If it doesn't take next time, that's what I'd do. I know you're doing this anyway(hopefully), but make sure you read all of the OPs, watch the recommended videos, etc. Good luck man.
Sent from my SPH-D710BST using xda premium

no joy. downloaded the bone stock tar md5 file
odin 3 under pda
same thing. stops at cache.img
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710_GB27_1014481_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> NAND Write Start!!
<ID:0/025> cache.img
what do I do?

Try flashing a one click instead of a tar. And if that hangs up, try flashing just a custom recovery. If that takes, you can get into cwm and flash a zip version of the rom.
Sent from my SPH-D710 using xda premium

I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?

nerys71 said:
I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?
Click to expand...
Click to collapse
Dl a stock jb zip, gb27 will work. If it flashes in recovery, you won't have cwm, but that's ok, we'll cross that bridge when we get to it. And use stock el26 cwm tar by chris41g. If it flashes in Odin, it may reboot to Samsung logo, that's ok, just reboot to recovery.
Sent from my SPH-D710 using xda premium

ok I am grabbing this rom now
http://forum.xda-developers.com/showthread.php?t=2224230 (3 hours to download)
and using this CWM
http://forum.xda-developers.com/showthread.php?p=24987585
grabbing the GB08 modem from here
http://forum.xda-developers.com/showthread.php?t=1764210
and the agate63 source kernel from here
http://forum.xda-developers.com/showthread.php?t=1662295
I just tried to odin the StockCWM-EL26.tar.md5
stops at
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> StockCWM-EL26.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> zImage
<ID:0/017> NAND Write Start!!
Grrrrr now what ?
I tried re booting to recovery anyway thinking maybe it worked. no joy
says Firmware upgrade encountered an issue please select recovery mode in kies & try again
when I try to boot into recovery.

You're still able to get into download mode correct?
If you can get to download mode do the following:
Uninstall kies and Samsung drivers,Download ODIN 1.85 from here and install it (the newer versions have been known to fail flashes on occasion), plug your usb cable into pc not the phone, open ODIN and navigate to PDA (like you did before) and open, choose the GB27 tar file. Make sure that repartition is NOT checked, now connect your phone and wait for the com light to come on, once it lights up press start.
Now the reason I suggest this yet again is because you're trying to flash from ODIN v3+, Kies and Odin are known to conflict sometimes, and the repartition box will always cause issues without a pit file (these are dangerous to play with if you're not familiar with them)
It's unusual, but not unheard of, for a one click would fail. If all else fails, and this doesn't work for you, please post the exact model number under the battery of your device, so that we can determine if there are any discrepancies.

ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)

nerys71 said:
ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)
Click to expand...
Click to collapse
OK, do you happen to have another cable to try? Or perhaps another usb port on your pc?
Slithering from the nether regions of a twisted mind and tarnished soul

so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.

nerys71 said:
so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.
Click to expand...
Click to collapse
Man, what got flashed? LOL
OK, you're able to get to Odin mode, the PC recognized your device, but install fails as soon as it begins to write the images...
4 cables one of them should have worked if that was the issue, and several different pc's...
Reinstalling drivers didn't do anything...
Different version of Odin...
I assume you've verified md5?
Have you tried other downloads, or the same file?
Maybe try flashing say, FL24 with Odin, then the GB27. If FL24 flashes then you know its the GB27 thats failing. Where are you grabbing your download from?
Slithering from the nether regions of a twisted mind and tarnished soul

I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.

nerys71 said:
I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.
Click to expand...
Click to collapse
Try this link http://www.sxtpdevelopers.com/showthread.php?t=166 download that tar and try flashing it

[Q] Please help. simi-bricked galaxy s 2

Here is the background. I upgraded my s2 to a note2 and added an extra line for my son to keep the s2. they did not register the sim at the store. I had rooted and installed custom rom, so wanted to return to stock. I then odin'd a tar from here sampro.pl/firmware/android/samsung-sgh-t989/ which worked for a week(allowed me to log his apps acct etc). Today, the day of his birthday I called tmobile and activated the sim. I called my phone from the sg2 sucsessfully. I then turned it off and packaged it/ wrapped it. an hr later my son opened it and turned it on. it then boot looped on the tmobile splash with the blue loading bar. I reflashed with the latest. failed after a few files, mid flash. It now gives me a screen i have never seen before. It says "Firmware upgrade encountered an issue. please select recovery mode in kies and try agian." I have tried other firmwares from the site and 2 from the sticky threads here. it either fails after a few files or instantly giving the same error screen. I have odin recognising it. I cant get kies to connect but it does try. I have been using costom roms from the start and am well versed in the processes and this phone in perticular. Someone please save my boys birthday, and tell me I dont need to jtag it. I have been through the posts and cant find anything that works. The toolkit is having issues on my laptop so am limited to odin. I will have him all weekend so any help in the next 2 days would be most apreciated!!!!!
PS: I can hold vol down on power up to see my usual message of up to continue or down to reboot. up goes to the prediscribed error and down does not reboot. I got the toolkit to launch(forgot about admin) and it doesnt recognise any hardware. odin fails on all flashes. I am thinking it has to do with the recovery. i am going to try to flash a custom now.
Here is the flash record of odin <OSM> Please wait..
<OSM> T989UVMC6_T989TMB_T989UVMC6_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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> amss.bin
<ID:0/008> boot.img
<ID:0/008> cache.img.ext4
<ID:0/008> mdm.bin
<ID:0/008> __Xmit Write fail
<ID:0/008> XmitData Fail..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try to Odin TWRP 2.5.0.0 tar from here
http://techerrata.com/browse/twrp2/hercules

Icy0ne said:
Here is the background. I upgraded my s2 to a note2 and added an extra line for my son to keep the s2. they did not register the sim at the store. I had rooted and installed custom rom, so wanted to return to stock. I then odin'd a tar from here sampro.pl/firmware/android/samsung-sgh-t989/ which worked for a week(allowed me to log his apps acct etc). Today, the day of his birthday I called tmobile and activated the sim. I called my phone from the sg2 sucsessfully. I then turned it off and packaged it/ wrapped it. an hr later my son opened it and turned it on. it then boot looped on the tmobile splash with the blue loading bar. I reflashed with the latest. failed after a few files, mid flash. It now gives me a screen i have never seen before. It says "Firmware upgrade encountered an issue. please select recovery mode in kies and try agian." I have tried other firmwares from the site and 2 from the sticky threads here. it either fails after a few files or instantly giving the same error screen. I have odin recognising it. I cant get kies to connect but it does try. I have been using costom roms from the start and am well versed in the processes and this phone in perticular. Someone please save my boys birthday, and tell me I dont need to jtag it. I have been through the posts and cant find anything that works. The toolkit is having issues on my laptop so am limited to odin. I will have him all weekend so any help in the next 2 days would be most apreciated!!!!!
PS: I can hold vol down on power up to see my usual message of up to continue or down to reboot. up goes to the prediscribed error and down does not reboot. I got the toolkit to launch(forgot about admin) and it doesnt recognise any hardware. odin fails on all flashes. I am thinking it has to do with the recovery. i am going to try to flash a custom now.
Here is the flash record of odin <OSM> Please wait..
<OSM> T989UVMC6_T989TMB_T989UVMC6_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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> amss.bin
<ID:0/008> boot.img
<ID:0/008> cache.img.ext4
<ID:0/008> mdm.bin
<ID:0/008> __Xmit Write fail
<ID:0/008> XmitData Fail..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Readownload the file and try it again T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5
Sent from my SGH-T989 using Tapatalk 2

:chuckle:
esema1o said:
Readownload the file and try it again T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
This made me laugh a little as it sounds like what i tell my coworkers before my first cup of coffee. Followed by did you restart it? I am re downloading for the 3rd time to be sure. as i am waiting i tried to reflash the stock recovery that i had laying around. that brought me back the boot ani with the tmobile logo and blue loading bar. I reflashed an original os i had in my files from a long time ago and got the first error screen. i am now attempting to reflash the working recovery and then the latest dl of T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5. will update as soon as done. thank you very much for the response on a saterday and all. you rock for effort!!

uggg
So I have used old recovery and several stock roms to no avail. I have tried 5 different ones now. it all hangs for wayyy too long. I just did a fresh dl'd copy of latest from predefined site. Back to original message. I am now going to try canogen mod with custom rom. please add if you have any thoughts.
edit: Ps : I have been flashing phones for a while now so when i say way too long i mean atleast 45 to an hour, which is longer then any sucsesful flash I have done.
2nd edit: I sucsefully installed twrp. in mid dl of jedi mind trick rom to install.

Sucsess!!
Icy0ne said:
So I have used old recovery and several stock roms to no avail. I have tried 5 different ones now. it all hangs for wayyy too long. I just did a fresh dl'd copy of latest from predefined site. Back to original message. I am now going to try canogen mod with custom rom. please add if you have any thoughts.
edit: Ps : I have been flashing phones for a while now so when i say way too long i mean atleast 45 to an hour, which is longer then any sucsesful flash I have done.
2nd edit: I sucsefully installed twrp. in mid dl of jedi mind trick rom to install.
Click to expand...
Click to collapse
I have flashed jedi mind trick sucsesfully!!!! I have twerp 2.5. I should be able to enable debugging and apps.reboot into twrp fix permissions, clear delvik cache and reboot into recovery then odin the latest stock from the previos posts.
Please reply as I dont want to send him back to moms with a hacked os, but dont want to make a move now that it is usable.
Thank you very much!!!!

Thank you!
meekrawb said:
Try to Odin TWRP 2.5.0.0 tar from here
Thank you for the link as I was having trouble finding on xda. the links have been shaky since the mega debaucle. Can you please link to your preferred stock as I dont have faith in the sanpro.pl links
Super Thanks!!!
At the least He now has a usable device. Even beter is the impact of seeing the effort to fix it. He now knows to use xda and the steps taken which is more valueable then the phone itself.
Thank you.
Click to expand...
Click to collapse

Icy0ne said:
Thank you for the link as I was having trouble finding on xda. the links have been shaky since the mega debaucle. Can you please link to your preferred stock as I dont have faith in the sanpro.pl links
.
Click to expand...
Click to collapse
I use
http://www.sammobile.com/firmwares/
Just type t989 in the search box.
Never had a problem with the files from there. You have to sign up for an account though.

Had the exact same thing happen to me, phone wouldn't boot or anything, no button combo worked and couldn't boot to recovery, what I did was to Odin twrp recovery tar. flash recovery and it fixed it, of course it roots the phone to but u can always odin back to stock after it boots up
Sent from my SGH-T989 using Tapatalk 4 Beta

Sprint Galaxy S III - Soft Brick problem

I think I soft bricked my phone, but I don't know how to get it resolved. I can get into my recovery and download mode, which leads me to believe that it is soft bricked. I'm trying to flash a stock rom using Odin and I am getting an error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how I can fix this?

dasignz said:
I think I soft bricked my phone, but I don't know how to get it resolved. I can get into my recovery and download mode, which leads me to believe that it is soft bricked. I'm trying to flash a stock rom using Odin and I am getting an error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how I can fix this?
Click to expand...
Click to collapse
Go here...... http://www.sxtpdevelopers.com/showthread.php?t=233. Download the one-click rooted no data and try again. If that doesn't work, you can always try using a different cable. Do you have TWRP as the recovery or CWM? If you have TWRP, you can always boot into recovery, connect your phone to the computer via USB, mount the USB drive and then push any ROM to your external SD card and then just flash from there.

tkepk181 said:
Go here...... http://www.sxtpdevelopers.com/showthread.php?t=233. Download the one-click rooted no data and try again. If that doesn't work, you can always try using a different cable. Do you have TWRP as the recovery or CWM? If you have TWRP, you can always boot into recovery, connect your phone to the computer via USB, mount the USB drive and then push any ROM to your external SD card and then just flash from there.
Click to expand...
Click to collapse
I have CWM installed. It's having trouble mounting things, such as
cache/recovery
/sdcard/.android_secure
/data
I had just installed CM10.1 on it, and it suddenly started rebooting in a loop and I received these errors when trying to anything with the phone.

Your trying to use odin correct? But you have kies also set up?
Also do you have the MD4 updated bootloader installed?
Sent from the future via Tapatalk 4

edfunkycold said:
Your trying to use odin correct? But you have kies also set up?
Also do you have the MD4 updated bootloader installed?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I believe I am using Odin correctly, I have flashed other things with it in the past, I am running it in administrator mode. I do not have Kies set up. And I don't entirely know what you mean by MD4 Updated Bootloader.

dasignz said:
I believe I am using Odin correctly, I have flashed other things with it in the past, I am running it in administrator mode. I do not have Kies set up. And I don't entirely know what you mean by MD4 Updated Bootloader.
Click to expand...
Click to collapse
In order to flash any of the new 10.1 cm it is required that the bootloader be updated to the latest release MD4. There us a script which checks for it. Can you boot into CWM? If yes then boot into CWM and flash this first. http://db.tt/Qt6NcH0a
Sent from the future via Tapatalk 4

edfunkycold said:
In order to flash any of the new 10.1 cm it is required that the bootloader be updated to the latest release MD4. There us a script which checks for it. Can you boot into CWM? If yes then boot into CWM and flash this first. http://db.tt/Qt6NcH0a
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
You'll have to forgive me, I am a little new to this. Where would I get the MD4 bootloader?

dasignz said:
You'll have to forgive me, I am a little new to this. Where would I get the MD4 bootloader?
Click to expand...
Click to collapse
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4

edfunkycold said:
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Sorry, I got it. I have tried to flash through CWM, but I am having a problem with mounting as I mentioned in previous comments. I can flash CM10.1 in CWM and it says updated successfully, but it's stuck in a bootloop because the /data and /.android_secure are missing. So I am trying to go back to stock with the firmware to start over, but odin is not working as I thought it would.

Flash the update i gave you then flash 10.1 again and try to boot up. Make sure you wipe cache and dalvik and do a factory reset before flashing
Sent from the future via Tapatalk 4

edfunkycold said:
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I tried to flash that modem you sent me. It failed saying
Updating SBL1 OTA
assert failed: package_extract_file("sbl1.mbn","/dev/block/mmcblk0p2")

dasignz said:
I tried to flash that modem you sent me. It failed saying
Updating SBL1 OTA
assert failed: package_extract_file("sbl1.mbn","/dev/block/mmcblk0p2")
Click to expand...
Click to collapse
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4

edfunkycold said:
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
This thing is all messed up. This is what happens when I try to use Odin to flash CWM
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

edfunkycold said:
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Is there a .PIT file that I can use to re-partition my phone? Seems like the partition is bad or corrupted. All attempts to install stock firmware have failed. CWM works fine, but I cannot mount anything. The only thing I can mount is my external SD card.

dasignz said:
Is there a .PIT file that I can use to re-partition my phone? Seems like the partition is bad or corrupted. All attempts to install stock firmware have failed. CWM works fine, but I cannot mount anything. The only thing I can mount is my external SD card.
Click to expand...
Click to collapse
Does anyone know where I can get a .PIT file for a Sprint Galaxy S3? I have tried just about everything, and the failure keeps happening when it tries to write an .img to the phone in odin 3.0.7. I want to try and re-partition the phone to see if that fixes any corrupt partitions to be able to write to the phone.

dasignz said:
Does anyone know where I can get a .PIT file for a Sprint Galaxy S3? I have tried just about everything, and the failure keeps happening when it tries to write an .img to the phone in odin 3.0.7. I want to try and re-partition the phone to see if that fixes any corrupt partitions to be able to write to the phone.
Click to expand...
Click to collapse
http://invisiblek.org/sph-i710/ (sic)

Screen says There is no PIT partition after Firmware Install Failure

So I've been at this for a total of 9 hours now...here's the story:
Yesterday I have my trusty Note 4 on the charger, it charges fully and I unplug from the cord.
I hit the home button and the screen stays black like it was frozen.
I hit the power button, nothing happens.
I pull the battery, put it back in, nothing.
It finally goes back on and I get the Cant do normal boot:"MMC_Failed" and I'm stuck on the Odin screen.
Try to just re-flash the stock rooted ROM I was using at the time of this disaster and I kept getting the same message so I bring the phone to a Sprint service center where, when I walk in the front door and tap the power button, the phone lights right up and works. Now I look like a clown.
I leave the store and it freezes again so I try a factory reset, which sets this whole process in motion again once I set it up...freezes, "can't do normal boot" etc.
Then after someone suggested to flash the latest TWRP (3.0.0.0) and a stock firmware, I get a "system write fail" in Odin (both 3.09 & 3.10) so I try to flash the stock ROM again now I get a "No PIT File" error.
I flash the PIT file specific for my phone I got from SamMobile along with the same ROM and the phone wouldn't start.
I noticed the "system" was unchecked in TWRP so I checked it before doing anything but still no luck as of last night/this morning at 3:00am.
I wake up this morning and it goes right on with no issue just like a fresh/factory reset device.
Is there something i can do to make sure everything is ok so I don't have to go through this again?
I need this Note 4 to work.
I have been running stock OJ6 rooted ROM and that's it. No mods or anything, just root so for this to start acting up the way it did or why it happened is beyond me.
Someone recommended to install ClockworkMod so that would fix the "system" error but I'd rather see if anyone else had the same problem and how they fixed it before I attempt anything else.
Usually, any time I ever had a problem I clear the dalvik/cache, factory reset or flash firmware in Odin and everything is straight.
Thanks ahead of time for any help.

What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk

samep said:
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night

broad_st_bully said:
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
Click to expand...
Click to collapse
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk

samep said:
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...

Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_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> 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> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:

broad_st_bully said:
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Click to expand...
Click to collapse
If it dus not boot try to flash repair firmware

broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
Removed!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
RQT_CLOSE !!
RES OK !!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
If you've wiped everything but extSdCard and flashed the stock tar in Odin, there shouldn't be any trace of root. You're not rooted.
Did you try factory reset in stock recovery? Can't recall, but is there also a format data option in stock recovery? If so, try that too.
Sent from my SM-N920P using Tapatalk

broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_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> 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> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped

waheem said:
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
Click to expand...
Click to collapse
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!

broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:

broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...

broad_st_bully said:
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
Click to expand...
Click to collapse
Just press thanks buttons if help

broad_st_bully said:
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
Click to expand...
Click to collapse
@broad_st_bully any luck on this issue since last post? or had you given up? I am experiencing the same issue but with the tmobile version running cmremix rooted.... at least it was...

New problem!! Help ASAP!!

so, i decided to flash back to 5.1.1 but i have unfortunately was not be able to pull this move from some weird error.
After many attempts here's what I've done.
I used the Flashable Tar for 6.0.1 MM and after awhile for my experience i went and tried to flash back to OL1 5.1.1 the latest rev and now i was stuck with Odins "Set Partition" or "BootLoader" wont flash or format nothing phase,
After i rebooted the phone, i noticed i could still access TWRP and Download mode and left with nothing to flash but going to TWRP and charge my phone....
In Twrp i was left with its "Unable to mount" and "Invalid arguement" issues after each little label for trying to mount and everything from the log, i've tried zip from a OTG and that didn't work even sideloading wouldn't help. I was left with nothing and it kept confusing.
My drivers were up to day, i tried a different Odin 10.7 and even tried Kies but that didn't even work so.
I made another attempt with Odin one more time and i was left with this log.
for flashing the 5.1.1 again G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.md5
it goes to
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
It would hang from this point doing nothing, and sometimes even after words it would say "Set Partition" or "Bootloader" in bold, and when i reset the phone to go back into "TWRP" it sends me this response.
<ID:0/010> __XmitData_Write
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I'm ultimately stumped,
So earlier which took about 1-2 hours to finally figure this out, i've tried wiping data,cache and etc or anything for that matter, and then I received a slew of "Failed to mount '/data' (Invalid argument)" and "Unable to mount storage" when trying to flash anything. Surprisingly enough, my internal memory shows up as 0mb aswell, then i went to "Wipe" - "Format Data"- "Yes" and it formatted with it's function and i rebooted back into Twrp it reads its original storage but i'm still left with no way to boot up completely.
sometime after i've tried flashing the 6.0.1 tar and i recieved this
6.0.1\ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar.md5
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
hangs again, left with "Set Partition" and i restart the phone
<ID:0/010> __XmitData_Write
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I have googled around XDA and around the general web, and I see a lot flashing for PIT or extracting the tar to make odin read it and attempt to flash it 1by1 but im not sure how to entirely do that I'd like this to be as easy as possible since i only have very little knowledge for Attempts to solve this.
I am not sure where to find the other files, let alone Bootloader for the MM stock flashable 6.0.1 or the 5.1.1 latest rev, I have the stock tar but not the rest.
I am genuinely asking for help, with someone that has maybe had this issue, or what can be done to solve it.
Any help would be vastly appreciated.

so, i've tried multple tars and nothing has worked for me it is always stuck that one file sboot.bin i've tried the OL1 5.1.1 and 6.0.1 stock tar it just isnt cutting it, BUT what i've notcied is that i was able to flash the Renegade rom in TWRP via OTG and it worked, iwas able to access the phone like usual and everything was written just fine but im still lost as to why it wont flash that sboot.bin file. i practically cant reset or reformat my phone.

How bout restarting the computer, Maybe a differnt one. How many times have you flashed that phone? Maybe this might start happening to others time will tell. personally i dont like odin I only use it only when needed to reset update firmware or recovery update. Its not often. Is your cable wore out hey at least you got the renegade rom and can flash something.

You know you can't downgrade right? Once you update you can't go back.

Saafir said:
That is not entirely true. And you can always JTAG back even, lol.
Click to expand...
Click to collapse
Yes. Regardless, your going to break something if you flash different bootloaders.

how would i be able to do that? i've tried different cables and im now trying the different odin and twrp im scared it will just keep saying sboot.bin forever i mean it was just a simple flash mm6.0.1 tar from the threads not the official one :/ and then downgradin didnt let me is there a way i can log that?

provided any links? or bootloader files?

I was able to flash back to 5.1.1 via offical TAR with no bricking, many people have done the same, granted, usually this isnt possible, but has worked for me many times now on customer devices as well as once on my own, just to test it lol.

can u send me your tar file? by chance?
anderd said:
I was able to flash back to 5.1.1 via offical TAR with no bricking, many people have done the same, granted, usually this isnt possible, but has worked for me many times now on customer devices as well as once on my own, just to test it lol.
Click to expand...
Click to collapse
could you send methe tar file by chance?

IAmTechFreq said:
could you send methe tar file by chance?
Click to expand...
Click to collapse
Here. I did the downgrade 6.0.1 to 5.1.1 too with no problem.
http://www.sammobile.com/firmwares/download/60059/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR/

So for right now I'm still unable to flash the Tars still. Even with the same and different tar I downloaded. I've tried different cables, computers, I just i don't seem to figure this out.... What do I do? Is there a way to capture an Odin log or even on my phone??
The xmit data writ happens after I restart my phone because it just hangs or freezes on the sboot.bin file or item..... Is there a way to flash it seperately??? I'm still some how running the 6.0.1 renegade custom rom tho and everything else is fine

Evidence
Pics of evidence

Try this one.
https://www.androidfilehost.com/?fid=24345424848486725

I recommend getting a pit file and flashing it. You seem to be having partition issues as noted by the TWRP error logs when it tries to mount things.
I made one awhile ago, it's for the 32GB variant if that's what you have try and Google search for it. Don't ask me for it because I'll have to Google search too but don't have the time right this second.
Sent from my SM-G920P using Tapatalk

elesbb said:
I recommend getting a pit file and flashing it. You seem to be having partition issues as noted by the TWRP error logs when it tries to mount things.
I made one awhile ago, it's for the 32GB variant if that's what you have try and Google search for it. Don't ask me for it because I'll have to Google search too but don't have the time right this second.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
If you have the 32GB variant, here is a PIT file I made awhile back that has helped and worked for others.
http://forum.xda-developers.com/attachment.php?attachmentid=3582475&d=1450575695

Sorry for such late replyss, and yes i have the 32Gb version, and it just says or i've been seeing that appears in Odin as well, the "Set Partition" or "Bootloader" i wil ltry out that PIT file and see if it works and etc and will keep you updated.

elesbb said:
If you have the 32GB variant, here is a PIT file I made awhile back that has helped and worked for others.
http://forum.xda-developers.com/attachment.php?attachmentid=3582475&d=1450575695
Click to expand...
Click to collapse
@elesbb, do you want me to put this up on my Android File Host account, so it doesn't get lost? PM me if you do.

thank you so much~ @elesbb This actually flashed completely trhoguh and it worked for me c: i just i was so just , i can't believe it worked i couldnt thank you enough c: seriously saved my life lol

Well problem solved always glad to follow along figure out what worked. I have the same phone lol.
The PIT File flash fixed it then well good to know. Good luck to you on you way.

IAmTechFreq said:
thank you so much~ @elesbb This actually flashed completely trhoguh and it worked for me c: i just i was so just , i can't believe it worked i couldnt thank you enough c: seriously saved my life lol
Click to expand...
Click to collapse
So you flashed the PIT file then flashed Stock TAR and it all worked?
Saafir said:
So what did we learn from this? Always make a nandroid?
Click to expand...
Click to collapse
Nandroid can't restore partition information. Only PIT can lol.