Develop Bugs

I bricked my Sprint Samsung Note II SPH-L900 and this is how I fixed it.

I figured I would post this as a basic how to for people who brick their phones because they are in a similar situation.
Sprint Samsung Galaxy Note II SPH L900
Used this root method because it was for Samsung Note II owners who already had Android 4.3.*,
http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-sprint-sph.html
Installed TWRP but it didn't stick to Download mode. I could boot into TWRP when my phone was up even after rebooting but could not boot the device directly into TWRP to access my custom recovery image.
Installed Perseus and Macks Rom AllStar V5.0 after saving them to my SD Card and did this after booting into TWRP from within my stock ROM.
Like an idiot I didn't read all the comments on ChainFire 3D when I was searching root 3d because I'm on a big kick right now of making it all 3d like.
Instead of flashing ChainFire 3d from recovery I used my in rom option since I had all my root programs running nicely and thought why not its just a button click instead of rebooting into TWRP. There was my mistake.
Alright so now I am bricked out of my phone in a boot loop. Nothing is happening but ChainFire said when you install not to freak out if your phone hangs for awhile, pull the battery after two minutes. Well I did and still bricked in a boot loop.
Scour the forums and Internet because I know I still have access to my phone through Odin. I don't have debug mode turned on so I can't even create an ADB shell to my device. That was my first through, run ADB shell, launch TWRP and restore my custom recovery. Would have worked except I had no way of getting to TWRP. Tried installing the Samsung ToolKit. Couldn't recognize my device.
Opened Odin back up and thought why not try to flash TWRP and have it reboot, maybe TWRP will launch. Well I don't know if that would have worked or not because every time I tried to reflash TWRP Odin encountered an error.
Alright, abandoned that idea and did some more research. I knew I could still flash to my phone but I didn't have anything to reset the caches to install another ROM and I didn't want to install something else where things could go potentially worse. I needed my damn phone back. Boom! Found some very helpful articles on restoring to stock and found the stock recovery one click solutions.
I am making this so lengthy in case you are going through something similar where you are stuck in a boot loop, locked out of TWRP but can still flash to your phone with Odin.
These two threads were massive help and they take you to the file locations:
http://forum.xda-developers.com/showthread.php?t=2116490
http://www.sxtpdevelopers.com/showthread.php?t=154
I restarted my phone in download mode which was a little tricky because when I put the battery in it would start booting. Had to make sure volume down, home and power were pressed while sliding the battery in. It's tricky but you can do it with one hand and use the other to insert the battery. Don't give up just because if you put the battery in your phone automatically boots!
I used this specific file. http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
I didn't know if my phone was MA5 or MA7. I was worried that something would be off if I downloaded the wrong one but I chose MA5 oneclick exe and it did the trick. I used the Rooted version that didn't delete my data so when the phone came back on all my changes were still there. Everything from the kernel was gone but my settings and etc were unaffected.
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
So anyways, there are some resources and an additional thread. I'm pretty tech savvy but when the damn thing bricked I wasn't for sure what to do. Hopefully this is semi helpful for someone.
*Cliff Notes:
If you brick yourself out of your Sprint Samsung Galaxy Note 2 (II) and you can't access recovery, go download one of these oneclick solutions from sextape or garwynn (big ups to you guys) and reflash it from download mode using their programs. If you rooted your phone using Odin you will feel right at home with their software and it is no big deal. Phone will be back up in no time.
Edit: So after I got back to my stock ROM and tried to reflash my previous roms they wouldn't stick. E Signature verification kept failing but I still had root. Used CWM Recovery straight out of the app store and rebooted in recovery. Wiped everything. Used the esignature toggle and disabled it. Bam was able to reinstall roms and I am back to tinkering

The title was misleading. I thought you meant a hard brick. What you encountered was a soft brick aka bootloop. Thanks for writing it up for the noobs though.
Sent from my SPH-L900 using Tapatalk 4

Yes title is misleading but great post for us thats need it
Thank u much for ur time to make this
SGN2

I bricked my sph l900 also..I had 4.3 rooted then went to jellybomb had a back up of my 4.3 rooted. Flashed back to it and it's now stuck in note 2 animation. Can't get into recovery or adb. Plz can anyone help ?
Sent from my SM-N900P using xda app-developers app

Is there a fix ?
Sent from my SM-N900P using xda app-developers app

odin oneclick failure
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)

kevo7000 said:
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use the original Samsung USB cable.:good:

new battery issue
gizmoscoop said:
You need to use the original Samsung USB cable.:good:
Click to expand...
Click to collapse
I used every cable I owned oven the original cable for my Note 2. I ended up taking it to sprint and replaced it. With this new note I've had two batteries completely fry. 100 % but will not power on without charger.smh

What is it that you did when the onclick kept failing?!!?
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
I keep running the NA5 Stock NoData exe and it keeps failing

stuck on boot screen with no recovery mode [SM-t320]

Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.

bmesta said:
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
Click to expand...
Click to collapse
Very strange.
Did you tried another firmware version using odin?

edlabh said:
Very strange.
Did you tried another firmware version using odin?
Click to expand...
Click to collapse
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?

bmesta said:
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
Click to expand...
Click to collapse
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device

bmesta said:
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
Click to expand...
Click to collapse
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?

edlabh said:
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
Click to expand...
Click to collapse
Im really happy to say that now i got a working tablet. I guess removing the battery did the trick.
'edlabh' thanks for all your help. I was able to charge the battery by plugging it directly to the wall. Please note that i had to take the entire tablet apart and disconnect the batteryfor 15 min before reconnecting it. Thank god im good with teardowns and i dont give up that easy

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
Hello, I was wondering if you would help with the kernel... Idk how to do it. I have done everything he did and even opened my tablet and took out the battery but it still did not work. :crying:
---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I already tried flashing TWRP, CWM, CF Autoroot (to be able to install a custom recovery). I opened it and removed the battery for 15 mins. unlike this guy, it didnt work for me. I also tried flashing CM12. The tablet wont turn on without being plugged in and I can only access "Downloading Mode"
Perhaps the kernel is broken, but how do I fix it?
This is Odin's message, after flashing stock firmware.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320XXU1BOC1_T320UVS1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it still wont boot past the splash screen nor can I access recovery mode.

Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key

otyg said:
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
Click to expand...
Click to collapse
Also, another thing is the when I plug it in and press the power button it lights up and shows the battery icon with no charge stuck in a loading icon that is not animated.
I will try your suggestion but I had already try (on Kies) Update and Recovery but it didnt work (perhaps because of the tablet being in Downloading mode?)
UPDATE: Kies 3 wont recognize tablet, even in Downloading mode (which is the only mode I can access).
Thanks!

This thread is very old. But I've the same problem, stuck at samsung logo and only get into download mode. Accessing the twrp recovery mode is not possible. I've not flashed the device and the battery had over 90% percent. I started the device suddenly it turned of and it was not possible to start it again. Has anyone solved this problem?

I didn't thought that the battery was the problem, because one time the devices started and showed about 90%, but it was the battery. The batteries are very bad for this device, this is my third one.

[Q] Stuck in bootloop, Odin keeps failing

Hey everyone, hoping someone can help me out here.
Recently I decided to set my S3 back to stock after running Cyanogenmod for quite some time. Somewhere along the way, I must have grabbed a wrong file, but one thing led to another and my phone got stuck on the Samsung logo while booting. I am able to get my phone into download mode and have tried to flash any rom I can through Odin, but it fails every time. I have even gone and got the official firmware from the Samsung site and it still fails. Here is the error:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> 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/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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Anybody have any ideas what I'm doing wrong? Thanks

Odin is failing because you are trying to downgrade the bootloader.
What bootloader is on your phone? You have an i747 or i747m?

I have the i747

With an i747 and the fact that Odin is giving an error when trying to flash a stock LK3 ROM, you must have at least a 4.3 bootloader. This means that you cannot use Odin to flash a stock ATT 4.3 or ATT 4.4 ROM unless the ROM has been specifically compiled for use in Odin.
Do not make anymore attempts to to flash the stock LK3 ROM as this may brick your phone.
If you still have a custom recovery on your phone, flash any custom ROM and let us know the baseband.
We're all here to help.

Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.

VctrEco12 said:
Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.
Click to expand...
Click to collapse
Do you have a ROM on your phone?

Do you mean a ROM in a zip folder that I could flash through recovery? Because I think the only one I have on my phone is the one that could this big mess up

Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Not sure if this helps but you may be able to use this to flash a ROM and recovery: http://wiki.cyanogenmod.org/w/Insta..._custom_recovery_on_Galaxy_S_III_.28AT.26T.29
Do you have a USB jig?

audit13 said:
Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Click to expand...
Click to collapse
That I don't really know about. Is there a way to figure that out? Right now if I just boot the phone, it gets to the Samsung logo and just stays there, never goes any farther. Never makes it to the home screen.
Also, thank you for all your help so far, apparently I don't know as much as I thought I did..

Your phone could have a ROM installed but you probably need to get into recovery to wipe the cache, Dalvik, and data.
I suggest putting a custom rom such as CM10.2 onto an external SD card and try to get into recovery to flash the new ROM. Make sure you wipe cache, dalvik, and data before installing CM10.2.

Ok I will try that and hopefully something will happen. Do you know of a way to get into recovery other than the button combo since I don't have a functioning volume up button and also can't get to the home screen to boot to recovery from there.

Not sure but fastboot commands could work in download mode.

Those commands are given through ADB, correct? I installed ADB and it doesn't show up in the list of devices. I think that since the phone is stuck in a bootloop, it never gets to a point where it can be recognized and receive commands. It also doesn't get recognized in download mode.

When you connect it in download mode, are the drivers installing? Or were they installed from when you first used Odin?
You may have to try and get into recovery using the recovery keys. You have a USB jig?

I uninstalled the original drivers and let it reinstall once I plugged it in, but it still is not recognized. And no, I don't have a jig, I found a program that acts like one that puts it in download mode once I plug it in.

Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?

audit13 said:
Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?
Click to expand...
Click to collapse
Correct, I cannot get to recovery by using the volume up, home, and power buttons. I was hoping there could be some other program or commands to help me get to it since ADB won't recognize my phone.
And here is the link to the forum with the program that forces it into download mode. It even picks up my phone in a boot loop
http://forum.gsmhosting.com/vbb/f777/samsung-300k-tool-force-enter-download-mode-via-usb-1718796/

Interesting. I don't have a s3 to try it with but I will definitely keep it around

Do you have any hidden tricks to get into recovery mode without using the volume buttons? It seems like all my problems could be solved if I can get to recovery and flash a ROM, but that broken volume button is preventing me...

Sorry, I just know the button combination or from a booted ROM.
Too bad Samsung doesn't readily support fastboot commands.

[Q] Need Help Unbricking AT&T I747

Unlike the other threads I've read here so far, I wasn't upgrading or downgrading anything on my phone. Last night, I was playing Scrabble (lol) and the phone blacked out and now won't power on. I've tried booting to Download mode and can't even do that. The battery was running low at the time, but that's normal for late at night. I believe I had about 9% battery.
The symptoms of my phone are now:
When I have the battery installed, plugging in the charger doesn't seem to do anything (no charging light).
When I remove the battery, plugging in the charger lights the LED as red for 90 seconds.
Plugging the phone into my computer via USB (without battery), the phone connects (as a device for which I do not have drivers) for 90 seconds (same duration as the red light) and then disconnects.
If I hold the power button in for 12-13 seconds (without battery with charger connected), the red light will go out. As soon as I release the power button, the red light comes back on and the 90-second timer restarts. If I have the phone connected to my computer while trying this, the phone disconnects when the red light goes out and reconnects to the computer (as the same device from above) when I release the power button.
Overnight, I left the phone (with battery) plugged in hoping to fully charge the battery and that would somehow miraculously bring my phone back to life this morning -- it did not. Unknown if the battery is fully charged now or not.
Any suggestions on what I might try next?

See if this helps:
http://forum.xda-developers.com/showthread.php?t=2549068

Lithium ion batteries are at their least stable when they're low on charge like you indicated yours was. How old is your battery? Does it have any bulges you can see or feel? If you put in on a table and flick it on the corner does it spin around? The spin test is by no means conclusive that a battery won't function, but it is indicative of some damage. My original Samsung battery spins like a top, but it still holds a charge and makes an ok backup in a pinch. If you know someone else with a working S3 try their battery in your phone. Otherwise, if there is a Batteries Plus or somewhere like that convenient, pop in and try a replacement. Most replacement batteries I've bought for phones or cameras usually come partially charged so you can probably test it right in store; the guys in the stores might know a thing or two as well as a lot of battery shops have started replacing phone screens and batteries that aren't as readily removable like that other variety of smartphone.
The debrick threads suggested above are a good idea too, but like you pointed out, those are usually for people who tried to downgrade our wonderful secure bootloaders.
If none of that pans out, a repair shop might be able to jtag it back to life.
Good luck.

Update
I was reading this unbrick thread and downloaded this debrick img for I747U. I applied the debrick img to a 32GB microSD card and I got the phone to at least do something. What I see is:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
WRITE 159488 SECTORS..
[COLOR="Red"]FLASH WRITE FAILURE
ODIN MODE[/COLOR]
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE[/COLOR]
[COLOR="Red"]Warranty Bit: 1[/COLOR]
[COLOR="Silver"]BOOTLOADER RP SWREV: 2[/COLOR]
I can now see the phone in ODIN when I connect with USB.
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.

Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.

audit13 said:
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
Click to expand...
Click to collapse
I'm hoping to reflash the stock rooted MJB so I don't lose everything that I had on the phone.

Hossy923 said:
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Click to expand...
Click to collapse
When I try and flash with the file above with ODIN v3.07, I get:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.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>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
At the same time, I get two additional lines on the screen of the phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Looking inside the .tar.md5, I do see a PIT file in there.
---
If I flash with ODIN v1.85, I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.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>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)[/COLOR]

Flashing via Odin is almost guaranteed to require a full wipe to boot.

audit13 said:
Flashing via Odin is almost guaranteed to require a full wipe to boot.
Click to expand...
Click to collapse
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?

Hossy923 said:
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Click to expand...
Click to collapse
Re-partition is unchecked?

I get the same error in Odin3 with Re-Partition checked and unchecked.

You used a debrick image for the i747u? Did you try an i747 de-brick image?

I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.

Hossy923 said:
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Click to expand...
Click to collapse
I've come to believe now that my internal SD card has died. All attempts I've made to flash, whether with ODIN or Miracle Thunder have failed. I get a bunch of errors on the screen talking about errors reading or writing firmware/flash. I even tried doing a nand erase with ODIN and that failed. Unless someone has a better idea, I believe the device has hardware damage.

no os w/ twrp

I had rooted folowing a youtube guide about a month ago. Then decided to unroot. Had trouble and eventually installed twrp. Then did a stupid thing and ended up wiping everything. Now says there's no os and can do nothing but load twrp recovery and go into odin download mode. Also, touch screen has been left/right reversed so that to tap on a button on the left i have to tap the right. Up/down is still correct.
Originally my problem was that odin failed with writing despite using several different usb cords and multiple usb ports. I just want to have the phone back to factory. I dont know what build i was using when i rooted either.

Try to flash this in ODIN: https://www.androidfilehost.com/?fid=24269982087002159
If that doesn't work, I don't know what to tell you.

generalmustard said:
I had rooted folowing a youtube guide about a month ago. Then decided to unroot. Had trouble and eventually installed twrp. Then did a stupid thing and ended up wiping everything. Now says there's no os and can do nothing but load twrp recovery and go into odin download mode. Also, touch screen has been left/right reversed so that to tap on a button on the left i have to tap the right. Up/down is still correct.
Originally my problem was that odin failed with writing despite using several different usb cords and multiple usb ports. I just want to have the phone back to factory. I dont know what build i was using when i rooted either.
Click to expand...
Click to collapse
Are you sure you are flashing the correct firmware (ie flashing S6 edge firmware on a flat S6). Reverse touch was a symptom of flashing the S6 edge rom on an S6 and then not flashing the S6 kernel.

HELP
OK GUYS LET ME START OUT WITH SAYING IM A COMPLETE IDIOT,
NOW WITH THAT OUT OF THE WAY, I USED THE UNIKERNEL FLASH VERSION ON MY BRAND NEW S6, WORKED GREAT, SO OVER THAT LAST MONTH i DID EXACTLY WHAT ANYONE WOULD DO WITH 32 GYGES, I SAVED OVER 600 APPS TO MY PHONE. I FINALLY CAME T MY SENSES AND REBOOTED INTO TWRP TO FACTORY RESET. I DONT KNOW WHAT HAPPENED BUT IT DELETED MY OPERATING SYSTEM. TO MAKE MATTERS WORSE, THIS IS THE ODIN ERROR I GET:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
I EITHER GET THIS AND IT STAYS THERE OR I GET A OUTRIGHT FAILURE. SOMEONE PLEASE HELP ME
[email protected]