Develop Bugs

[Q] Bricked and tips aren't working so far. Help, please!

Well, dang... I've tried everything I can think of and am stuck. If any of you have suggestions, I'll be forever in your debt.
So I was trying out a few ROMS on my I747. The last working one I had was LiquidSmooth Android (v2.1 I believe) but it was rebooting on me more often than I'd like, so I tried booting into TWRP to restore my last Nandroid of the rooted stock ROM I had been running fine. I know that Nandroid backup was a good one because I have restored it before. So anyway, I boot into TWRP and suddenly TWRP asks me for a password, which it has never done before. It almost looked like TWRP thought my device was encrypted, which it wasn't. But then when I hit "cancel" and tried to use the TWRP Factory Reset wipe, all of the attempts to mount the partitions failed! So I decided to let TWRP reboot the device, thinking something weird was going on with TWRP that would be fixed the next time I loaded it (DOH!) and I've been hosed ever since.
I am in a stange position with my I747 now. The OS won't boot at all. It forces the phone to try to boot into recovery, which is the latest TWRP. Unfortunately that just hangs at the "teamwin" screen and never goes on. First thing I decided to try was to flash a fresh TWRP thinking my TWRP had gotten mucked up. When got the latest TWRP tar from your Toolkit "recovery" folder (I am a donator from a day or two ago) it looked like it successfully flashed the TWRP to the phone, although I'm a bit worried maybe I don't understand Odin's output. Here is what it shows when I flash the TWRP:
------
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
------
The phone reboots like the re-write of TWRP was successful, but then it just hangs at the "teamwin" screen again. So then I thought I'd try flashing CWM instead.. The output from ODIN looks basically the same, but when I reboot into recovery I again am stuck at the "teamwin" screen from TWRP! WTH?
Why am I still seeing the "teamwin" screen if I just flashed CWM and Odin says it succeeded? I'm guessing it has something to do with the "RQT CLOSE !!" line in the log above. Is that actually a failure message that I thought was a success message? It isn't real clear..
So then my last fall back was just to flash the whole stock ROM again. Sadly, that didn't seem to work either. It actually gives me a WRITE (Fail!) message. Here is the output of Odin when trying to write the stock ROM to the phone in Download mode. I'm trying to flash the files called "I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5".
----
Code:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
----
As you can see, the MD5 checks passed with no problems, but the actual writing of the code to the NAND fails immediately. At this point I have no idea what to try next.
And for the record, I also tried flashing back the original boot image from your Toolkit called "boot-stock-dlk3-SGHI747.tar". Here is what I get when I try to flash that with Odin.
----
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
-----
Any suggestions anyone might have for what to do next would be most appreciated. Sadly, this is my only phone, and my employer pays for it. I need to get it up and running as soon as I can, if it is possible. Probably shouldn't have been messing with it in the first place, but I'm a tinkerer at heart.. What can I say?
Thanks for taking the time to read this and thanks for any tips any of you can share!!
MrSimmonsSr

Are you using the automated process from the toolkit?
Try using odin alone and flashing back to stock
http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/

MrSimmonsSr said:
Well, dang... I've tried everything I can think of and am stuck. If any of you have suggestions, I'll be forever in your debt.
So I was trying out a few ROMS on my I747. The last working one I had was LiquidSmooth Android (v2.1 I believe) but it was rebooting on me more often than I'd like, so I tried booting into TWRP to restore my last Nandroid of the rooted stock ROM I had been running fine. I know that Nandroid backup was a good one because I have restored it before. So anyway, I boot into TWRP and suddenly TWRP asks me for a password, which it has never done before. It almost looked like TWRP thought my device was encrypted, which it wasn't. But then when I hit "cancel" and tried to use the TWRP Factory Reset wipe, all of the attempts to mount the partitions failed! So I decided to let TWRP reboot the device, thinking something weird was going on with TWRP that would be fixed the next time I loaded it (DOH!) and I've been hosed ever since.
I am in a stange position with my I747 now. The OS won't boot at all. It forces the phone to try to boot into recovery, which is the latest TWRP. Unfortunately that just hangs at the "teamwin" screen and never goes on. First thing I decided to try was to flash a fresh TWRP thinking my TWRP had gotten mucked up. When got the latest TWRP tar from your Toolkit "recovery" folder (I am a donator from a day or two ago) it looked like it successfully flashed the TWRP to the phone, although I'm a bit worried maybe I don't understand Odin's output. Here is what it shows when I flash the TWRP:
------
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
------
The phone reboots like the re-write of TWRP was successful, but then it just hangs at the "teamwin" screen again. So then I thought I'd try flashing CWM instead.. The output from ODIN looks basically the same, but when I reboot into recovery I again am stuck at the "teamwin" screen from TWRP! WTH?
Why am I still seeing the "teamwin" screen if I just flashed CWM and Odin says it succeeded? I'm guessing it has something to do with the "RQT CLOSE !!" line in the log above. Is that actually a failure message that I thought was a success message? It isn't real clear..
So then my last fall back was just to flash the whole stock ROM again. Sadly, that didn't seem to work either. It actually gives me a WRITE (Fail!) message. Here is the output of Odin when trying to write the stock ROM to the phone in Download mode. I'm trying to flash the files called "I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5".
----
Code:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
----
As you can see, the MD5 checks passed with no problems, but the actual writing of the code to the NAND fails immediately. At this point I have no idea what to try next.
And for the record, I also tried flashing back the original boot image from your Toolkit called "boot-stock-dlk3-SGHI747.tar". Here is what I get when I try to flash that with Odin.
----
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
-----
Any suggestions anyone might have for what to do next would be most appreciated. Sadly, this is my only phone, and my employer pays for it. I need to get it up and running as soon as I can, if it is possible. Probably shouldn't have been messing with it in the first place, but I'm a tinkerer at heart.. What can I say?
Thanks for taking the time to read this and thanks for any tips any of you can share!!
MrSimmonsSr
Click to expand...
Click to collapse
Flash a rooted stock Rom and reinstall recovery. I would recommend using root66 rooted stock by mr. Robinson.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Or rooted stock...I have had luck in the past going to pure stock and starting over. When your restored use the beginners guide to rooting in the general section. Once root is achieved....use the goo.im app to install most current version of TWRP.
Sent from my SGH-I747 using XDA premium

Sorry for not being more clear.. I was using the various tar files, and the Odin exe file from the Toolkit, but I was using them on their own. I would go into the Toolkit install folder and crank of Odin binary by itself, outside of the other tools..
And when I tried flashing a Stock ROM, it would give me the "WRITE (FAIL!)" error.. When I tried re-flashing any recovery, CWM or TWRP, it would say success but when I booted into recovery it would always be TWRP and it would always freeze at the "teamwin" screen and never get past it.
Thoughts?
Thanks!
thegodsquirrel said:
Are you using the automated process from the toolkit?
Try using odin alone and flashing back to stock
http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
Click to expand...
Click to collapse

dima470 said:
Flash a rooted stock Rom and reinstall recovery. I would recommend using root66 rooted stock by mr. Robinson.
Click to expand...
Click to collapse
If you read my post again you will see that I have tried both flashing a stock ROM (non-rooted, got a WRITE error) and flashing a recovery (seems to be successful, but doesn't actually change the recovery on my phone), and neither seem to be working.
Is there any way you guys know of to get passed the messages I'm seeing in ODIN?
Thanks! Much appreciate you guys taking the time to respond!
MrSimmonsSr

MrSimmonsSr said:
Sorry for not being more clear.. I was using the various tar files, and the Odin exe file from the Toolkit, but I was using them on their own. I would go into the Toolkit install folder and crank of Odin binary by itself, outside of the other tools..
And when I tried flashing a Stock ROM, it would give me the "WRITE (FAIL!)" error.. When I tried re-flashing any recovery, CWM or TWRP, it would say success but when I booted into recovery it would always be TWRP and it would always freeze at the "teamwin" screen and never get past it.
Thoughts?
Thanks!
Click to expand...
Click to collapse
I would bet it is a case of goofy android device hijinks. If you have another cord use that (this has worked for me in the past). Use that tutorial I linked and see if you can get it back to stock stock stock.
Sent from my SGH-I747 using xda premium

thegodsquirrel said:
Or rooted stock...I have had luck in the past going to pure stock and starting over. When your restored use the beginners guide to rooting in the general section. Once root is achieved....use the goo.im app to install most current version of TWRP.
Click to expand...
Click to collapse
You are right and I don't mind going back to stock ROM at all. I downloaded the stock ROM and tried to flash it with ODIN directly. As you will see in my original post, I got a message from ODIN saying the NAND write had failed.. No idea why! That is why I'm stuck and not sure what to try next.
I have a good Nandroid backup that I could restore if I just had access to TWRP, but it seems hosed up and won't get past the "teamwin" screen, but when I try to reflash TWRP, or CWM Recovery for that matter, it looks like ODIN says it was successful but I always end up stuck right back at that teamwin screen. Even after I just flashed CWM Recovery!! So something isn't right.
Any other ideas?

I don't think you are going to get back in to the recovery. Pull the battery and sim. Let it sit for a while. Did you go and download the tar from link I provided? It could be that the one you have is corrupted. I dunno. Good news is you are not bricked, just soft bricked. We just need the right combo to get it back into the os. It sounds stupid but try another USB cable if you have one.
Sent from my SGH-I747 using xda premium

I have tried multiple USB cables but that didn't help. The tutorial you linked was actually what I was reading last night to try to fix this myself without bothering anyone here. Unfortunately I get down to step 11 and that is where the problem happens. Odin gives me the output in my oringinal message and tells me the stock ROM could not be written to the NAND. That is why I'm stuck. If you look at my original post, it is in the second quote of ODIN output, and it says:
Code:
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Write)
I always thought if I could get back to download mode, I'd be able to recover, but unless I can figure out why ODIN can't write the stock ROM to my NAND, I do not know what to try next..
Thanks! Any other ideas?
MrSimmonsSr
thegodsquirrel said:
I would bet it is a case of goofy android device hijinks. If you have another cord use that (this has worked for me in the past). Use that tutorial I linked and see if you can get it back to stock stock stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Son of *****...well if you haven't tried it yet pull battery and sim. Let it sit for an hour
Sent from my SGH-I747 using xda premium

I did download the same Stock ROM referenced and that is what I've been trying to load. The TAR file seems fine because ODIN says it passes the MD5 checks before it tries to flash it. I have tried it after pulling the battery for a while. Will pull the SIM also, just in case..
Thoughts?
thegodsquirrel said:
I don't think you are going to get back in to the recovery. Pull the battery and sim. Let it sit for a while. Did you go and download the tar from link I provided? It could be that the one you have is corrupted. I dunno. Good news is you are not bricked, just soft bricked. We just need the right combo to get it back into the os. It sounds stupid but try another USB cable if you have one.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

For the record, here is a screenshot of what ODIN looks like when I try to flash the stock ROM..
I'm starting to wonder if I need to start using some of the other options in ODIN. Obviously need to understand what they do much better before I start trying things. I don't want to hard brick the device. At least I can still get into download mode at this point!
Any other suggestions? Thanks for the help!
MrSimmonsSr

Make sure you are using the stock usb cable that came with the phone. Most micro usb cables are 5 pin, whereas the GS3 has an 11 pin connector and usb cable.

suprtrukr425 said:
Make sure you are using the stock usb cable that came with the phone. Most micro usb cables are 5 pin, whereas the GS3 has an 11 pin connector and usb cable.
Click to expand...
Click to collapse
Hmm.. That is interesting. I don't know if I have the original cable or not. Is there a marking on the original that will let me know. I have some many USB cables laying around from Blackberries and other devices, I'm not sure which one is which anymore..
I have successfully flashed stuff with these cables before.. Thoughts?
Del

Unchecked auto reboot and f. Reset time. Let it sit. Then button combo into recovery.
Sent from my SGH-I747 using xda premium

Any time I try to go into recovery I just hang at the TWRP startup screen that says "teamwin".. Even after ODIN tells me "success" on flashing CWM Recovery!! Obviously the flashing of recovery isn't really working even though ODIN is telling me it is a success.
I'm starting to think I have NAND corruption and need to repartition. Does anyone know where to find a STOCK ROM file that is safe to use with the ODIN repartition option?
Thanks!
thegodsquirrel said:
Unchecked auto reboot and f. Reset time. Let it sit. Then button combo into recovery.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Edit: nm checked the setup looks good.
I wouldn't completely give up...yet. Are you using the stock cable?
Sent from my SGH-I747 using xda premium

I have so many microUSB cables lying around here from various devices (BB 9800, Playbook, etc..) I don't know which one is the one that came with the GS3 anymore. Is there a way to tell?
That having been said, aren't they all the same as long as they were made for data sync and power?
And I'm not giving up, I'm just pretty sure I am suffering from what I see referred to in other threads as NAND Corruption. I think I might need to re-partition in order to get it resolved. But in order to do that, of course, I need a good PIT file for my device. Anyone know where I can find a PIT file that is made for this phone (SGH-I747)? I'm not worried about loosing any data. I have a good Nandroid I know I can recover with if I can just get TWRP working again..
thegodsquirrel said:
I wouldn't completely give up...yet. Are you using the stock cable?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse

Yea...that's got to be it. Gs3 cable all black with a black shiny micro SD connector. Keep us up to date if you fix it.
Sent from my SGH-I747 using xda premium

[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)

Stuck a Teamwin-logo, cant go into recovery mode

I flashed my Galaxy Tab S 8.4 a while ago with TWRP and installed CM12. Worked fine until a couple of days ago when I turned on the tablet. It got stuck on the Teamwin-logo and I cant do anything what so ever... Cant turn it off, reboot, go into recovery etc no matter what I do. Even if I let the battery die out the **** starts again as soon as I turn it on again. Can this be fixed and if so, how? Thanks a bunch!

Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.

ashyx said:
Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.
Click to expand...
Click to collapse
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*

Lunaspice78 said:
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*
Click to expand...
Click to collapse
Well of course it worked. You have to flash TWRP!

ashyx said:
Well of course it worked. You have to flash TWRP!
Click to expand...
Click to collapse
How am I suppose to flash it when I cant get any further than "Downloading..." ?

Lunaspice78 said:
How am I suppose to flash it when I cant get any further than "Downloading..." ?
Click to expand...
Click to collapse
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.

ashyx said:
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.
Click to expand...
Click to collapse
I did just like that... going into download mode. But as I said, when I go into download mode I get stuck at "Downloading... Do not turn off target!" I cant get any further. The only thing to do is a reboot -> power + vol up and down which results in being stuck in another TWRP-loop. When ever I try to enter recovery mode by power + home + vol up, either when in the TWRP-boot screen loop or when being stuck in the download mode nothing happens. Oh, and also... I cant turn off my device. I try to empty its batteries and when I plug in the charger it boots up and gets stuck at looping the TWRP-logo.
Sorry for the doublepost.

OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?

ashyx said:
OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?
Click to expand...
Click to collapse
No no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.

Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Well, you dont have the same problem because you actually have the option to flash which I dont. I´m stuck at the screen showed in the screenshot in the above post.

no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.
Click to expand...
Click to collapse
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
xronofag said:
Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
According to that nothing flashed, did you flash using the AP slot?

ashyx said:
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
According to that nothing flashed, did you flash using the AP slot?
Click to expand...
Click to collapse
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

xronofag said:
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.

I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!

ashyx said:
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.
Click to expand...
Click to collapse
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page

Lunaspice78 said:
I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!
Click to expand...
Click to collapse
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
xronofag said:
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page
Click to expand...
Click to collapse
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633

ashyx said:
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633
Click to expand...
Click to collapse
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.

xronofag said:
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.
Click to expand...
Click to collapse
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.

ashyx said:
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.
Click to expand...
Click to collapse
Thanks. This is still an issue for me.
I only know how to flash from recovery(reboot to recovery choose ROM from internal FLASH etc) but the problem is that I can not enter the recovery mode. I am stuck in this cyclic TeamWin logo. Do you know how to act in such case top proceed wtih stock ROM flashin as advised above?

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...