Hi!
After flashing many custom kernels and swapping them a lot of times with Mobile Odin, I have noticed two days ago that my Recovery (CWM) is fried. Whenever I try entering it I just end with a bootloop, that carries on for a few times, even if I try booting normally. Then everything works fine.
I didn't care too much until today, I am willing to try some custom roms and I am not able to flash them, and I am not able to Nandroid...
So I said "Let's flash the recovery again!" Hell no... Odin 3.04 just stays on Write Nand Start forever, it's been 20 minutes this time (tried 10 times with diferrent files, usb ports, cables, computers EVERYTHING). I am putting the file in PDA section.
I suppose the recovery partition got corrupted somehow? These are the kernels I swapped: Perseus, Note2Core, NEAK, Different versions of stock and others I don't even remember.
Now I don't even see my build number in Settings->About. It just shows "$" WTF?!
What should I do? I would really like to try some of those beautiful custom roms! I am sick tired of Touchwizz and its lags...
<ID:0/017> Added!!
<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> tmp/recovery.img
<ID:0/017> NAND Write Start!!
Flash pit file first then recovery.
4l3xXx said:
Hi!
After flashing many custom kernels and swapping them a lot of times with Mobile Odin, I have noticed two days ago that my Recovery (CWM) is fried. Whenever I try entering it I just end with a bootloop, that carries on for a few times, even if I try booting normally. Then everything works fine.
I didn't care too much until today, I am willing to try some custom roms and I am not able to flash them, and I am not able to Nandroid...
So I said "Let's flash the recovery again!" Hell no... Odin 3.04 just stays on Write Nand Start forever, it's been 20 minutes this time (tried 10 times with diferrent files, usb ports, cables, computers EVERYTHING). I am putting the file in PDA section.
I suppose the recovery partition got corrupted somehow? These are the kernels I swapped: Perseus, Note2Core, NEAK, Different versions of stock and others I don't even remember.
Now I don't even see my build number in Settings->About. It just shows "$" WTF?!
What should I do? I would really like to try some of those beautiful custom roms! I am sick tired of Touchwizz and its lags...
<ID:0/017> Added!!
<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> tmp/recovery.img
<ID:0/017> NAND Write Start!!
Click to expand...
Click to collapse
A good start would be to start reading threads about root, flashing, Odin, recovery, custom roms and kernels. If you don`t know what you`re doing you`are about to crash and burn your device
dr.ketan said:
Flash pit file first then recovery.
Click to expand...
Click to collapse
Pit file failed as well, at getting pit for mapping, but in the end I solved by flashing TWRP through Note 2 toolkit. I don't know what the problem was, I'm happy I solved it though. Possibly there was something going on with kies/drivers/odin 3.04 (toolkit uses 3.07) or God knows what else.
Related
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
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
Hiiyaa..
Mkk, ive tried all solutions, nothing works..
I was randomly using my S3 on stock software, it shut off and now it will not turn on.. Absolute hard bricked, not even a jig will kick this on..
So i made a recovery sd card, finally it kicked it into dl mode..
PROBLEM:
It tries to write 15988 sectors, then pops up FLASH WRITE FAILURE
ODIN MODE.
SYSTEM STATUS: NONE.
Okay, Ive tried flashing stock rom through odin, it will get close and then pops up the error No PIT partition found..
I tried to flash a pit file, it fails.
Im using a rear usb port, different cables. Nothing works..
I tried to do a nand wipe through odin, it gets to userdata partition and then fails when it tries to repartition..
Im at a loss here, any help will be amazing...
EDIT:
Heres the error that odin is giving me
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Some questions you can answer to give more of a frame:
1. What software build are/were you on?
2. If the software had KNOX, had you done anything to attempt to remove/disable it?
3. The firmware was stock, were you also on stock recovery?
Sent from my iPod touch using Tapatalk
thenexusgeneration said:
Some questions you can answer to give more of a frame:
1. What software build are/were you on?
2. If the software had KNOX, had you done anything to attempt to remove/disable it?
3. The firmware was stock, were you also on stock recovery?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I was on JB 4.1.2, it didnt have knox, and i was on stock recovery,
Johnnysauur said:
Hiiyaa..
Mkk, ive tried all solutions, nothing works..
I was randomly using my S3 on stock software, it shut off and now it will not turn on.. Absolute hard bricked, not even a jig will kick this on..
So i made a recovery sd card, finally it kicked it into dl mode..
PROBLEM:
It tries to write 15988 sectors, then pops up FLASH WRITE FAILURE
ODIN MODE.
SYSTEM STATUS: NONE.
Okay, Ive tried flashing stock rom through odin, it will get close and then pops up the error No PIT partition found..
I tried to flash a pit file, it fails.
Im using a rear usb port, different cables. Nothing works..
I tried to do a nand wipe through odin, it gets to userdata partition and then fails when it tries to repartition..
Im at a loss here, any help will be amazing...
EDIT:
Heres the error that odin is giving me
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What did you do to make this recovery sd card? i got the same problem and the jig did nothing!!!!
I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?
same issue.
Erik1805 said:
I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?
Click to expand...
Click to collapse
i have come to a similar dead end.
came from fastdreamV6 rom and odin'd in T210RUEU0COB1_T210RXAC0COB1_HOME .tar .md5
pardon my terminology but i guess you'd say i dirty Odin'd it?> did not wipe or revert.
its where things went wroung for me
soo any ways.. looking for helpful and knowledageble people to begin trouble shooting this issue
after the install it rebooted and showed the tab3 splash screen then android package installer full screen before an OS. when the page installer screen disappeared that was the end of any responsiveness from the device.
mine always boots to black screen. no recovery , no audible/visual anything until odin mode.
always a black screen until i walk through the odin/download mode key' sequence blind
i have only half of what should look like a odin/download mode screen, the android guy has disappeared.
WIN7 does find the tab3 thats in [email protected]$$ odin mode in the device manager
odin also sees the tab3 but odin doesnt want to work to upload anything < hangs at setupconnection.. or pit mapping failed even when i have the new pit file being pushed,
ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
hemidall gives me communication conflicts
adb .. i currently have no os on the tablet as far as i can tell. maybe somebody can tell me if i can fastboot a command to push a recovery into it. but without adb-communication. i dont see it happening?
i presume i have a corrupted .pit file thats its not allowing me to replace.
OR KITKAT needs its own .pit file and i will need help aquiring one.
or its just a really bad flash alltogether. being boot.img. system img. recover img
how should i proceed if there is a way ? looking to get back to stock 4.4.2.
i can solder and make a usb jig if nessasary.
1 week later; further developments and workaround to boot here:
http://forum.xda-developers.com/gal...ably-hard-bricked-t3057440/page2#post60682636
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.