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] SDS, sboot.bin + PIT fail, alternatives?

Hi all, i have a n7100 and the problem was that it just rebooted from nothing and was stuck on samsung logo, then i took it to the official repair center and they couldn do anything and told me that they needed to send it to samsung for repair but they will not do that due to root... so i took it to samsung autorized repair center and the same, they just tried to upload the stock rom but nothing... wont boot, buy a new board will cost me around $600 with those guys... so the problem is this
I can enter download mode and recovery:good:, so:
using odin, all roms (4 dif roms) fail to upload at sboot.bin
<ID:0/011> sboot.bin
<ID:0/011> FAIL!
(using 2 dif machines and 2 dif cables, all 4 roms)
then i tried to reformat using pit "N7100_t03g_0907-stock.pit" and
checking [Re-Partition] then it says there is no pit partition
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
the only rom i was able to fully upload was N7100UBALJ2_N7100TCEALJ1_TCE
but because it contains not the sboot.bin file...
still not booting
also using CWM recovery 6.0.1.4 i can't mount cache, system, data, sdcard neither format
[Error mounting /cache!] etc etc etc
i even used aromafm http://forum.xda-developers.com/showthread.php?t=1646108 to see files on internal sdcard but all those mentioned folders-partitions apear as empty folders but folders like dev, etc, lib, proc, res, sbin, sys, tmp apear ok (files inside)
and one final thing i cant replace CWM recovery for TWRP or stock recovery, i have both odin and sdcard versions but after finishing succesfully, rebooting and entering recovery again there is CWM...
so my questions are:
is there any other way to repartition not using odin+PIT
is there any utility to check internal sdcard integrity?
what about sboot.bin not being able to flash
any ideas?

At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom

mrshdw said:
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom
Click to expand...
Click to collapse
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?

vagsvag said:
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?
Click to expand...
Click to collapse
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!

mrshdw said:
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!
Click to expand...
Click to collapse
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.

vagsvag said:
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.
Click to expand...
Click to collapse
yaep already tried that before, and now green button says PASS
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
but still cache cant mount in CWM, some messages [Can't mount /cache/recovery/command] and [Error mounting /cache] as those msgs appears always

Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.

vagsvag said:
Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.
Click to expand...
Click to collapse
via odin it passes - green button
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.15.0-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Added!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
after rebooting same CWM 6.0.1.4 appears
the zip file installed file via cwm also passes it took a while but at the end all ok
reboot but again same CWM
and yes sure kies is not in the system as only installed and uninstalled for the drivers
tried few different recoverys - different versions - oding & cwm install zip file from sdcard but all refuses to stay

Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539

See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100

vagsvag said:
Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539
Click to expand...
Click to collapse
already tried before with those 3 roms, first 2 failing on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and third one 4 parts + PIT stoping at PIT when ticking [Re-Partiton]
<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.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
and if not, stopping like first 2 on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and yes i have efs backup, the first time you select "mount /efs" in cwm it mounts, then if you unmount and mount again, it wont, it says "Error mounting /efs!" (works only for efs folder, but cache system data etc always unable to mount) so i restarted cwm and mount efs folder then using aroma fm copied to external sd cool!
also have some backup that i made with cwm, 3 files "system.ext4.dup" "boot.img" "recovery.img"

vladeco said:
See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??

This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
ok great tools, i have the toolkit but haven't tried all options, going to check more on that and also dr ketans tool
really appreciate all your help, tell you if a have any advance

mrshdw said:
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??
Click to expand...
Click to collapse
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100

vladeco said:
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
ok i get it, if i find the same rom that i had, ill be able to fully flash rom, including sboot.bin, but no -older- roms as "it doesn't support downgrading", well i need to find that rom, dont remember which one i had, but i can keep trying, stock rom is not in the phone anymore, but remember flashing one a few month ago, but dont remember which one i had (sad & sorry)
for now after some downloads ill try to flash again, with and without PIT + Reformat, and if everything fails then use the NAND Erase all option.... seems clear! ill keep you posted

[Q] Sph-L710 Hard brick.

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

Note 2 seems bricked after trying to go back to stock firmware. Help needed!

Hi all,
I was using my Galaxy Note 2 with the latest Resurrection Remix ROM, but wanted to revert back to the stock firmware .
I downloaded the latest stock firmware and tried to flash it directly with ODIN.
Unfortunately, the process stopped at about 3/4 of the progress bar. I tried several time, changing USB ports and slots; even computer. After one try, the messages changed and the process stopped event before trying to write with the message : "There is no PIT partition".
The download mode shows the usual warning and download screen. But if I try to go in recovery mode or just boot normally, I get the "Firmware upgrade encountered an issue...".
What I've tried so far:
. Flashing several stock firmwares via several version of ODIN.
. Kies upgrades (tried about everything there).
I also tried a PIT file, but got the message: "Re-Partition operation failed".
I really don't know what to try anymore
Any help would be greatly appreciated!!!
(edit -> oh, and I've also tried with firewall and antivirus out)

FixB said:
Hi all,
I was using my Galaxy Note 2 with the latest Resurrection Remix ROM, but wanted to revert back to the stock firmware .
I downloaded the latest stock firmware and tried to flash it directly with ODIN.
Unfortunately, the process stopped at about 3/4 of the progress bar. I tried several time, changing USB ports and slots; even computer. After one try, the messages changed and the process stopped event before trying to write with the message : "There is no PIT partition".
The download mode shows the usual warning and download screen. But if I try to go in recovery mode or just boot normally, I get the "Firmware upgrade encountered an issue...".
What I've tried so far:
. Flashing several stock firmwares via several version of ODIN.
. Kies upgrades (tried about everything there).
I also tried a PIT file, but got the message: "Re-Partition operation failed".
I really don't know what to try anymore
Any help would be greatly appreciated!!!
(edit -> oh, and I've also tried with firewall and antivirus out)
Click to expand...
Click to collapse
Hi,you did all wipe from custom recovery before reinstalling the stock firmware?

Unfortunately, no
I did not do anything before trying to flash the stock firmware :'

FixB said:
Unfortunately, no
I did not do anything before trying to flash the stock firmware :'
Click to expand...
Click to collapse
Try and see if it works!

Thanks: I would... but I can't access recovery mode. I can only go into Download mode (recovery go to the "Firmware upgrade encountered an issue..." screen )

FixB said:
Thanks: I would... but I can't access recovery mode. I can only go into Download mode (recovery go to the "Firmware upgrade encountered an issue..." screen )
Click to expand...
Click to collapse
Now, I've got this message when trying to flash:
"<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)"

FixB said:
Now, I've got this message when trying to flash:
"<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
What you're trying to flash firmware 4.4.2 i hope, because if you're trying to flash a 4.3 is impossible the downgrade to do so because of Knox!

I was trying 4.4.2.... Does it matter if I was on a 5.x ROM?

FixB said:
I was trying 4.4.2.... Does it matter if I was on a 5.x ROM?
Click to expand...
Click to collapse
Did you try a different USB cable or different Odin version?

Yes, I tried several USB cables and USB ports and PCs and about 10 different Oding version
I'm starting to think it's hopeless

I flashed CWP recovery from here : http://forum.xda-developers.com/showthread.php?t=2000138
And it worked (at least Odin finished saying it was flashed ok). But if I try to go into recovery, I now get a 'Downloading' screen. When going to download mode, I have the normal screen, with a number of custom binary download increased by 1.
Anyone could advise on next steps I should try?
Thanks!

I managed to get back TWRP v2.8.7.0.
What would be the next steps to try and revert to the stock firmware?? Thanks!!

I used TWRP to reset and wipe everything, then ODIN to flash stock firmware.... And everything is now fine I've got the phone working perfectly with stock firmware!
Thanks!

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