[Q] Major issues flashing new ROM, help needed badly! - T-Mobile, Samsung Galaxy SIII

Hi.
First off, I've had my sgh-t999 since launch. I rooted it, and put TWRP recovery on it. I have used multiple roms over the past year with no problems at all.
I recently went to switch to a new rom. (new version of IOKP, upgrading from old infamous rom)
steps I took:
1. Placed rom on SD
2. Booted into Recovery
3. Wiped dalvik, and did full data wipe
4. flashed rom, success
5. Rom got stuck loading and wouldn't work.
Figured I needed to reinstall the rom, as this has happened to me before on previous phones.
6. Tried to reboot into recovery, Phone would not allow me to go into recovery, the blue text appeared at the top, but the phone would reboot itself after a second of the blue text leaving. (I tried adjusting the length of time I kept the buttons pressed down, both shorter and longer, to no avail.)
7. I looked up how to fix this. I used odin and the stock T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 to flash it back to stock.
8. The phone booted fine and I was back like normal. HOWEVER, I had no 4g, no wifi, my home button didn't work, and I had a lot of other errors.
9. I figured I should try to use a different stock rom, however ODIN began giving me error messages.
<ID:0/007> boot.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> recovery.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> system.img.ext4
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what USB port I use I get the same error. I even downloaded a .PIT file and tried to flash again. Same error message.
10. Now my phone is stuck. I cannot get into the phone, I cannot get into recovery, and when in download mode it reads "Firmware upgrade encountered an issue."
11. Kies doesn't even recognize my phone.
I am at a loss for what I need to do.
In case it helps my "download mode" screen says
sgh-t999
6 counts
binary:samsung official
status:custom
secureboot:enable
warranty bit:1
bootloader ap swerv: 1
Does anyone have any idea where I should go from here? I hate being stuck. I also use my phone for work, and am losing money the longer I go without it. If anyone can provide help, I would be forever grateful.

What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk

serio22 said:
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Stock 4.3: T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 was the file I had flashed. My phone booted up, but I had no 4g and no wifi. I hooked it up to odin again to reflash the same firmware, and my phone is now stuck at the black screen that says firmware update error.
Every time I use odin it returns an error no matter what stock firmware I try and use. I tried a .PIT file in combination with T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5, and it still returned an error.

Related

[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

Fix: semi bricked/bricked SPH-L710 Sprint S3

when I 1st rooted my s3 on 4.3, I messed it up lol I fixed it this way, which is installing a clean slate of 4.3 OTA via Odin...mine was a semi brick and keyboard was somehow gone as well, so this was my only choice:
1st download my bundle I made here
-once downloaded, extract the bundle preferably to your open desktop or wherever is easiest for you to guide through
your phone must have USB debugging mode enabled if you haven't done it already
-settings>more>developer options>enable usb debugging
-if you've never done this before, you'll have to go to: settings>more>about device>build number (tap on build number several times until the countdown states you're now a developer, once done press back once and developer options will now be present)
now once that's done, pull the battery, reinsert the battery and reboot into recovery by: holding volume up/home and power keys
once in recovery, do a factory data/cache wipe (fully wipe it out!)
now once that's done, pull your battery, reinsert your battery, hold: volume down/home and power keys and you'll be prompted with a warning and to press volume up to proceed, press volume up...this is "download mode"
on your computer, open the extracted bundle and run Odin 3.09 and make sure ONLY "auto reboot" and "f. reset time" boxes are checked
-connect your phone via usb cord and the ID: com will now light up and indicate it has detected your phone (if not, you'll need samsung drivers which can be found here)
-once recognized, load the necessary file by checking the box by the AP tab and then clicking the AP tab and load the .tar.md5 file in the bundled folder...this may take a few seconds, it's a large file so be patient
-once file is loaded, hit the "start" button and DO NOT INTERRUPT THIS PROCESS! once it's finished, again this is a large file and will take some time to finish, you'll see a "PASS" in Odin and also in the log box it will say "all threads completed (succeed 1/fail 0)
your phone will now reboot itself and restart with a freshly installed 4.3 OTA operating system! if it fails, try again and if it fails again, your phone may just be beyond repair...heard they can make a nice paper weight decoration lol GOOD LUCK!
To Reroot your phone: use my rooting guide
Nice post, I am sure that it will save someone.
Thanks OP!
I had a software brick and it worked out perfectly
phone_dude said:
Thanks OP!
I had a software brick and it worked out perfectly
Click to expand...
Click to collapse
thanks for the feedback and glad it worked! if you're looking to root it again, I have a guide up as well on doing that for 4.3, you won't brick by following that guide
Question, will doing this while on 4.3 and reinstalling 4.3 reset Knox counters? Or is there anyways yet to return to an unroofed stock with all Knox trips reset?
Sent from my SPH-L710 using Tapatalk
it should...this would be just like going to the sprint service techs and having them completely wipe and reinstall the 4.3 ota firmware like new
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
beejmeister said:
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
Click to expand...
Click to collapse
thanks for the compliments and glad it worked out for you, that's all that matters
Count my @$$ as saved
Well, looks like you saved my @$$. My phone noted that there was an update for cyanogenmod.... and bricked on reboot.
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
mister-crackers said:
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
Click to expand...
Click to collapse
just saw your post...glad it worked for you! let me know how you make out on your next tasks bro!
"Process com.android.phone has stopped"
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
neadams99 said:
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
Click to expand...
Click to collapse
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Followed your steps using ODIN -passed- stuck on s'sng logo
goku2778 said:
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Click to expand...
Click to collapse
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
neadams99 said:
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
Click to expand...
Click to collapse
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
2nd attempt failed.
goku2778 said:
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
Click to expand...
Click to collapse
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
neadams99 said:
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
Click to expand...
Click to collapse
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
can get into DL mode passed ODIN but then stuck w/logo
goku2778 said:
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
Click to expand...
Click to collapse
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
neadams99 said:
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
Click to expand...
Click to collapse
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Not getting past Samsung logo
goku2778 said:
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Click to expand...
Click to collapse
So so Sorry, if you were in CA, I'd come by so you could do it yourself. I;d even pay you good money. OK, sorry, I was freakin out, brah.
I did use ODIn and waited for a long time and the Samsung logo just hangs there. There is no progress, nothing. I can't get to the signing into Google or anything at all.
You said, " THEN you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu." But I cant get past the logo. I see the "Samsung" for two secs, then "Samsung Galaxy Slll" then the Sprint logo goes by with music, then back to the "Samsung" logo where it sits forever. This is killing me.

Samsng Tab 3 7.0 probably hard bricked

My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
untamed1 said:
My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
Click to expand...
Click to collapse
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
bierma32 said:
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
Click to expand...
Click to collapse
Thank you for your response.
First if with search function you mean by using google, I have done a lot of of that, but so far with no luck.
I am pretty good with this stuff but not good enough. I would like to find someone who has either a lot of knowledge or has resolved a situation like mine and is willing to help.
The link you suggested is probably good, but does not totally relate to my situation. They had a working device they were simply trying to root. I instead don't have a working device and not even access to recovery mode. I don't even know right now what files and folders are on my device.
Thank you for the pit file though; now I have to find out whether repartitioning with it would be good, or whether it would push me down deeper in the hole.
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
bierma32 said:
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
Click to expand...
Click to collapse
Bierma32,
first of all thank you for spending the time to assist me it is very much appreciated. I followed your procedure and unfortunately it went nowhere fast. This is the report from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COB1_T210RXAR0COB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what happened earlier with the only difference being the "Set PIT file" command.
Any idea?
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Rom's for Samsung Tab 3 7.0 SM-T210R
Doom1337 said:
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Click to expand...
Click to collapse
For non stock ROM's:
http://forum.xda-developers.com/galaxy-tab-3/development-7
For Stock ROM's:
http://www.sammobile.com/firmwares/
For stock there are faster download sources also, do some google searching. By the way my issue has nothing to do with rooting.
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
I had found another PIT file as well, that looked very promising but did not work. I will try these two. Thanks.
:fingers-crossed:
Continuation
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
untamed1 said:
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
Click to expand...
Click to collapse
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
No battery picture
vinay said:
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
untamed1 said:
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
Click to expand...
Click to collapse
you just hard bricked your device.
but download mode is working so still a hope.(untill power end)
which version of odin are you using.?
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
untamed1 said:
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
Click to expand...
Click to collapse
When this happen.
What was you doing.
Like
Your tab was running you turned off and it won't turn on. Or you flashed a rom/kernel and it won't turn on.
Sent from my D2212 using XDA Free mobile app
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
untamed1 said:
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
Click to expand...
Click to collapse
First of all update your odin to 3.09 or higher if there is. And try flashing again.
(btw is that rom was made for your variant)
Sent from my Xperia E3 using XDA Free mobile app
same issue
i also have an unresponsive sm-t210r that has the OP's issues of a broken looking download screen, no boot and no recovery
pit file problems in odin and timeouts and now not postitive if my device made it to the 4.4.2 locked bootloader. looking to get it back to stock.
will help with files, time etc.
-ty
SOLVED
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
kal swift said:
got my tab(SM-T210R) back up and running,,
been at it a few hours a day all this week,
kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,
so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
and then get PIT file errors and setup connection hangs.
please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.
(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)
to get your brick back to being a useful loaf
this is what you need.
factory usb cable
odin 3.07
LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails
and T210.TWRP.2.8.0.0.tar.md5
start with opening odin
set your pit file and load the twrp recovery_
you want repartition checked for this (loading pit file should automatically fill the check box)
also autoreboot and f.reset time , checkboxes are checked
get your bricked device into download mode and connect
confirm odin sees the device and flash
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.
restarts and power offs are safe at this point. just take 5 seconds longer than normal.
so now we have an operating tablet with recovery and a messed up but working download mode.
checked download mode screen STILL CORRUPTED with the same weird message
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
i checked for twrp to operate it did. just took longer to boot it
PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.
and not being able to odin the .md5 package stock firmwares
it put me back an hour to get back to where these instructions end.
if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.
FALLOW UP:
had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.
i had updated to the latest TWRP and rooted.
i then unrooted with the super su app
then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.
try it then go ahead and check for stock recovery and android man in download mode
-your welcome
b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?
if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?
be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.
> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE
Click to expand...
Click to collapse
I still cant get it working, i keep getting stuck with it saying it doesnt have a pit file even when i try to load it

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

Note 10+ SM-N975W Boot Loop After Update

Hello all,
So I recently updated my Note 10+ and while the OS will load and I can unlock my device, it reboots about 30 seconds after the OS loads. There is a notification showing that it is finishing up with the update each time the phone restarts. This will repeat over and over again and I really would like to avoid losing all of my data (both my internal and SD memory is encrypted). I've tried leaving the phone for a bit to see if it would stop, turning off bluetooth, wifi and location and plugging my phone into the charger. Nothing seems to work.
Full disclosure, about 6 months ago I followed a bloatware removal thread on these forums and uninstalled a handful of apps. I was careful to avoid any that I thought might cause issues and I've done OTA updates since then without issues but I figured I would mention it in case that's part of the issue.
Model: Note 10+ (SM-N975W)
Carrier: Telus (TLS)
Bootloader: Locked
Update: OTA via carrier
Appempting To Update Firmware Via ADB
1. I downloaded firmware matching my model and carrier from both Sammobile and using Frija as well as the ADB Platform Tools via Google.
2. After using apply update from ADB via Samsung recovery and trying the firmware files from the above sources my ADB progress never shows above 0% and my Note shows Verifying update package indefinitely.
3. Disconnecting my Note shows the following errors via recovery;
E:Failed to read 6 bytes data at offset 5983263248: I/O error
E:Failed to read footer
Update package verification took 90.3 s (result 1).
E:Signature verification failed
E:error:21
Install from ADB completed with status 2.
Installation aborted.
Attempting To Update Firmware Via Odin
1. I downloaded the 2 most recent version of Odin from XDA and chose Reboot to bootloader from the Samsung recovery menu
2. Opened Odin with admin privileges and loaded the BL, AP, CP and CSC (CSC_HOME) files. All MD5 checks done.
3. Hit Start and 2 seconds later I had Odin showing PASS! as well as the following;
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
4. Phone reboots and problem continues.
Any help you guys can offer would be appreciated. Let me know what other info you need from me.
A quick update. I attempted to put the previous firmware onto the phone via Odin and soft bricked it. It failed to boot and gave me the option to wipe the device or try again. I managed to get it back into download mode and used Odin to flash the latest firmware onto it and it boots into the OS now but the bootloop still occurs.
Edit: tried to restart the phone in safe mode but it hangs on the Samsung logo for a minute and then reboots and loads the full OS instead.
Try Smart Switch for PC, emergency recovery as I remember. Based on SN# maybe it'll be able to flash the latest firmware for it.
Turn phone off. Take out SD card. Hold side key (side key must be set to power off mode)and volume up key in at the same time until you see Samsung logo. From here you should be able to flash what you need to.

Categories

Resources