I need an expert, my phone may be trashed - AT&T Samsung Galaxy Note 4

This is my first time posting here and I am at a complete loss.
My sister gave me her ATT SM-N910A Note 4. It had started this awful rebooting process. She thought that I would be able to fix it, so I gave it a try. It will still not go past optimizing apps. This is only sometimes. It just reboots, reboots, and reboots. She was running on Marshmallow when this happened. The battery has been replaced.
I took it to the ATT store today and they did not seem like they were very interested in helping me. They kind of blew me off. They told me that since I could not get to recovery booting there was nothing that they could do. So, I proved to them that I could, indeed, get to recovery mode by holding all of the buttons down and putting the battery in. He looked at it for a second, pressed a button and he was done with it. He told me that my system files are deleted. That I need to find someone to help me recover them or I could do it myself. SD updating is disabled. I have to do this from Odin.
So, I think I need Odin files.
Please help!

rabeccalynn92 said:
This is my first time posting here and I am at a complete loss.
My sister gave me her ATT SM-N910A Note 4. It had started this awful rebooting process. She thought that I would be able to fix it, so I gave it a try. It will still not go past optimizing apps. This is only sometimes. It just reboots, reboots, and reboots. She was running on Marshmallow when this happened. The battery has been replaced.
I took it to the ATT store today and they did not seem like they were very interested in helping me. They kind of blew me off. They told me that since I could not get to recovery booting there was nothing that they could do. So, I proved to them that I could, indeed, get to recovery mode by holding all of the buttons down and putting the battery in. He looked at it for a second, pressed a button and he was done with it. He told me that my system files are deleted. That I need to find someone to help me recover them or I could do it myself. SD updating is disabled. I have to do this from Odin.
So, I think I need Odin files.
Please help!
Click to expand...
Click to collapse
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
Things you will require.
1, windows pc
2, download samsung usb drivers or Samsung kies and install it on your windows pc.
3,download odin tool for pc.
4,download stock firmware for your device.
5,your device battery charged minimum 50%.
6,usb 2.0 cable.
7, winzip/winrar installed on pc to extract the firmware file.
How to flash.
1,extract the firmware file you will get a huge file around 4gb.
2,open odin tool and choose AP Tab And upload firmware file that you extracted (ODIN WILL HANG WHEN YOU UPLOAD THE FILE SO DONT WORRY JUST WAIT 4 TO 5 MINUTES UNTIL FILE WILL UPLOAD )
3,put your phone to download mode by pressing (volume down+home+power button all together) hit volume up when you see warning logo)
4,connect phone to pc via usb cable .
5,HIT START IN ODIN TOOL .
6,once odin shows PASS remove usb cable and battery from phone and insert battery again.
7,boot into recovery mode by pressing(volume up+home+power button )
8,navigate via volume keys to "wipe cache" and hit power button and wipe cache.
8,navigate to "wipe data factory reset" and press power button to factory reset.
9,now reboot and wait 10 to 15 minutes and you will boot into system successfully.
11,Let the phone rest for few minutes then complete setup.
Hope this will help.
Samsung usb drivers link
https://m.en.softonic.com/app/samsung-usb-driver-for-mobile-phones
Odin for windows pc.
http://odindownload.com/download/Odin3_v3.10.6.zip
N910A FIRMWARE LATEST.
https://www.androidfilehost.com/?fid=24651430732238073

Just to be sure, what will happen when it reboots? Will it have recovery booting in the top of the screen? Then reboot by itself? Do you mind if I come back here after I get my daughter from school and get everything downloaded for if something goes wrong?
I will be home in about 35 minutes tops.

Trex888 said:
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
It went to the Samsung Galaxy Note 4 Screen and stayed there for a minute. Now it is off. Is this correct?
Click to expand...
Click to collapse

I am still rebooting. What else can I try?

rabeccalynn92 said:
I am still rebooting. What else can I try?
Click to expand...
Click to collapse
I had stupid problem with my s5 long time ago. It was sticky power button. I turn off my phone, use drop of alcohol and drop on power button. Then press couple times and let dry for 1 hour or use hair dryer to do it faster. Then turn on. Works perfect after all of this. Not saying tjis is your problem and this will help in 100% but wort to try. Good luck.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app

So, Odin will recognize my phone, but not my computer. My computer says that the device is not working properly. What is really going on here?

It is not even going to optimizing apps any longer. It used to always at least go to the ATT logo.
Now, it is vibrating non stop while it is off.

rabeccalynn92 said:
Trex888 said:
You need to flash stock firmware through Odin.
Follow these steps exactly and hopefully you will recover your device.
It went to the Samsung Galaxy Note 4 Screen and stayed there for a minute. Now it is off. Is this correct?
Click to expand...
Click to collapse
Remove battery and insert again Do factory reset and wipe cache from recovery as i mentioned earlier.then reboot and wait 15 minutes.
If odin not recognise your device try restsrt pc and connect again.
Click to expand...
Click to collapse

Here is a little information from my phone:
ODIN MODE: (HIGH SPEED)
Product Name: SM-N910A
Current Binary: Samsung Official (This used to be custom when my sister was using it on Straight Talk)
System Status: Official
Reactivation Lock: On
Know Warranty Void: 0x0
QualComm Secureboot: Enable (CSB)
AP SWREV: S1 T2 A1 A2 P1
SECURE DOWNLAOD: ENABLE
UOC (?)

I can not get back into Recovery Mode

rabeccalynn92 said:
Here is a little information from my phone:
ODIN MODE: (HIGH SPEED)
Product Name: SM-N910A
Current Binary: Samsung Official (This used to be custom when my sister was using it on Straight Talk)
System Status: Official
Reactivation Lock: On
Know Warranty Void: 0x0
QualComm Secureboot: Enable (CSB)
AP SWREV: S1 T2 A1 A2 P1
SECURE DOWNLAOD: ENABLE
UOC (?)
Click to expand...
Click to collapse
Your reactivation lock is on so you cannot flash anything through odin.
Reactivation lock must be turned off to flash.
Only You can turn off from settings/security/reactivation lock and turn it off.
I suggest you take your device to repair center they will take care of it .you cannot flash or do anything because it requires someone who is expert in adb commands to turn off reactivation lock while your device cannot boot.
If your device boot up you can turn off reactivation lock then try odin method that i mentioned earlier.

No way! That is not what I wanted to hear. There is absolutely nothing that I can do for this phone?
Where do I find a repair center?

It said installing system update and got half way through and cut off.

rabeccalynn92 said:
It said installing system update and got half way through and cut off.
Click to expand...
Click to collapse
Keep trying to boot into recovery and do factory reset then reboot.

Trex888 said:
Keep trying to boot into recovery and do factory reset then reboot.
Click to expand...
Click to collapse
I am going to keep trying. When it does get there (see how I said when and not if, confident) I will come back here. There has to be a way inside of this phone!
The recovery mode looks a little different now. When I got it from my sister, I tried a hard reset. It was red and blue then. Now it is white and yellow and has the option of system/mount(?) I am no expert, but I do believe changes are being made here. I am staying hopeful. I really want to use this phone!

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910AUCU2EPH5_CL8932341_QB10663742_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<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)
This was what I got after flashing. So, I thought all was good.

rabeccalynn92 said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910AUCU2EPH5_CL8932341_QB10663742_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<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)
This was what I got after flashing. So, I thought all was good.
Click to expand...
Click to collapse
Looks Everything went well but you have to do factory reset from recovery straight after flashing then reboot and wait 15 to 20 minutes on first boot it will take long time.

Okay..
I feel like it is doing something different.
I was able to get into recovery after leaving the battery out while I took my dog to the vet. I got home and it went into recovery. My droid bot fell out dead with his triangle. I pressed the power button and it bought up the menu. I cleared cache and wiped data/factory reset. It turned off talking about verifying some kind of hash tree.. It passed.
Now I am stuck on the Samsung Galaxy Note 4 screen. Is this the screen I need to leave it on for first boot?

rabeccalynn92 said:
Okay..
I feel like it is doing something different.
I was able to get into recovery after leaving the battery out while I took my dog to the vet. I got home and it went into recovery. My droid bot fell out dead with his triangle. I pressed the power button and it bought up the menu. I cleared cache and wiped data/factory reset. It turned off talking about verifying some kind of hash tree.. It passed.
Now I am stuck on the Samsung Galaxy Note 4 screen. Is this the screen I need to leave it on for first boot?
Click to expand...
Click to collapse
Yes you have to leave atleast 20 minutes for first boot.

Related

Another Soft Brick...

Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home
bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.

[Q] Softbrick, bootloop, TWRP Password

My girlfriends S3 (Bell, I747M, d2can) is currently boot looping. It had a custom ROM on it, but I'll be damned if I could tell you which one. It was working, then it wasn't. No updates, no flash/wipe/etc.
Now I turn on her phone, and it gets to the ROM's boot screen, and just as it's about to complete, it restarts again. I can enter TWRP (2.6.3.1) but it requires a password (which is a bug, afaik). I can press "cancel" and try to reset/wipe, but it won't mount or reset the cache partition, so it fails.
I used Odin (3.07, 3.09) to try and flash TWRP 2.6.3.0 and 2.7.0.0, and both failed. The result was Odin would reboot the phone, then it would enter the same bootloop, and the recovery would still be TWRP 2.6.3.1.
I tried downloading a stock S3 firmware and flashing it with Odin. Same problem.
I've tried new drivers. New cable. New USB port. I've tried using a different computer. Always the same result.
So a summary of what I can/can't do:
Can't use TWRP to reset/wipe
Can't use ADB Sideload
Can't modify device via ADB
CAN see the device via ADB
CAN enter download mode
Any help?
I pulled DMESG at some point during all this. Maybe it can help shed some light: http://pastebin.com/4c2uL3Qq
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
theramsey3 said:
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
Click to expand...
Click to collapse
Appreciate all the help! I've tried pretty much every combination.
I've turned off auto-reboot, flashed, but Odin stops at:
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
I assume that's where it's supposed to be. Then I enter recovery and it's still the same TWRP 2.6.3.1. Very strange.
I don't think her phone is using 4.3 bootloaders, as I don't remember them being available when I flashed this phone. I'm a Nexus guy, so maybe I'm doing something wrong this time.
EDIT: I also seem to recall on my phones that when I flashed something in Download/Fastboot mode, there was a progress bar of sorts on the phone itself indicating it was receiving something. On this phone it doesn't display anything to imply something's happening.
Boot into download and let us know what it says on the download screen. If you have the 4.3 bootloader, try flashing a pre-rooted 4.3 Bell ROM using Odin 3.07. If you have a lower version bootloader, try flashing a pre-rooted 4.1.1 or 4.1.2 ROM.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139036464
In Odin, don't check auto reboot. When you see reset in the status windows, disconnect the USB cable and pull the battery. Boot into recovery and wipe cache, data, and reboot.
Thanks for the reply! I'm 99% sure it's a pre-4.3 bootloader. Here's what it shows in DL mode:
ODIN MODE
PRODUCT NAME: SHG-I747M
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
DUALCOMM SECUREBOOT: ENABLE
If I recall correctly, a 4.3 bootloader would show two more lines at the bottom.
Tried installing a 4.1.1 ROM (root66_BMC_I747MVLDLK4)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDLK4.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
4.1.2 (root66_BMC_I747MVLDMF1.7z)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDMF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I feel it's worth mentioning again: At no point, while using Odin, does the phone display a transfer bar of any sort.
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
audit13 said:
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
Click to expand...
Click to collapse
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
X04D said:
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
Click to expand...
Click to collapse
Try this: when you flash with Odin, uncheck auto reboot, start the flash process. When you see the word reset in the status window, remove the USB cable, pull the battery, and boot into recovery.

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.

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

Categories

Resources