Note 10+ SM-N975W Boot Loop After Update - Samsung Galaxy Note 10+ Questions & Answers

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

A quick update. I attempted to put the previous firmware onto the phone via Odin and soft bricked it. It failed to boot and gave me the option to wipe the device or try again. I managed to get it back into download mode and used Odin to flash the latest firmware onto it and it boots into the OS now but the bootloop still occurs.
Edit: tried to restart the phone in safe mode but it hangs on the Samsung logo for a minute and then reboots and loads the full OS instead.

Try Smart Switch for PC, emergency recovery as I remember. Based on SN# maybe it'll be able to flash the latest firmware for it.

Turn phone off. Take out SD card. Hold side key (side key must be set to power off mode)and volume up key in at the same time until you see Samsung logo. From here you should be able to flash what you need to.

Related

[Q] Major issues flashing new ROM, help needed badly!

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

Using ODIN to install stock rom = soft bricked phone

I wanted to install (some other rom) since I had battery drain issues with Stock 4.3 so I decided to root the phone with the MrRobinson method.
1 - I installed the Samsung drivers
2 -Set the phone to USB debugging
3 - Used volume down+menu button to go into download mode.
Then plugged the phone in and waited for the drivers to load.
Then loaded Odin, went to PDA and loaded the file for Fido (my carrier).
Fido Image
Current I747MVLDMF1 (JB 4.1.2)
Mirror 1: Download root66_FMC_I747MVLDMF1.7z
Click to expand...
Click to collapse
The check sum came back okay.
I clicked start and then this is the message log from ODIN:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried the process a dozen times with the exact same result.
On regular boot the phone goes to a screen with "Firmware upgrade encountered issue - please select recovery mode in Kies & try again"
Kies says it can't communicate with the phone.
If I press Volume up + Menu I can't get into recovery mode, I get the same error screen as regular boot.
Help?
You have the i747 from AT&T? If you do, you cannot downgrade the 4.3 bootloader. Any attempts to flash an older bootloader will brick the phone and this seems to have happened to you.
.
Sorry wasn't clear, I have tried to root following the MrRobinson method
http://forum.xda-developers.com/showthread.php?t=1739426
Uninstalled Kies
Restarted the PC
Pulled out the phone battery for 24h.
Installed the latest drivers from Samsung
Ran ODIN 3.0.7 as Administrator
Same error on ODIN as before.
Phone says:
SV REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Do you have an i747 or i747m?
i747
Update: I went and downloaded the custom ClockWork Recovery CWM-Recovery-LTE-SGS3-V5.Tar.Md5 (http://d-h.st/am8)
Flashing this file with ODIN did work
I am able to enter recovery now by pressing volume up + menu
I put TeamEpic-Root-From-Recovery-V5.Zip (http://d-h.st/Gax) on my SD card
Booted to recovery.
In recovery>choose zip from sd card> install zip> I ran the TeamEpic-Root-From-Recovery-V5.Zip
The root worked.
I then did a factory wipe from recovery. The wipe worked and my phone has rebooted.
My phone has started working again.
I am getting a message "An attempt to access a secure area on your phone has been blocked."
Everything else is working again.
You have the 4.3 bootloader with Knox? This may explain why you got errors using Odin. The fido firmware is for the i747m, not the i747.

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

Tab Pro 8.4 stuck in bootloop after rooting and an interesting past history

Around a year ago:
My memory on this is hazy. I didn't mind the stock rom but wanted to root the device for a couple of apps. I used Odin3 as suggested by a tutorial at that time and ran into an issue where I had problems booting the device. Holding the power button in for many seconds didn't seem to do much until a couple hours later where I was able to shutdown the device. An hour or two later and I was able to boot the device again but it was stuck in a boot loop. A couple days after that, I suspected the battery was dead and charged it without turning the device on. An hour or so after that I was able to boot without issue and was able to verify I'd been rooted.
My links are removed due to XDA forum rules
Today:
I want to go with CM13 and after having this official CM tutorial for the Tab Pro 8.4
I was able to install TWRP without issues and reboot into the system fine. At around the point where I needed to use heimdall, I had an error similar to this:
Code:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I decided to go to the video suggested in the XDA Developers forums for the faster way:
[VIDEOS] Galaxy Tab Pro 8.4 How to Root Install Recovery & Rom on your device
I manually copied the CM zip and Google Apps zip to the external sdcard (brand new by the way), did the install, booted to CM13 and had no issues until I noticed I could not use oandbackup because it couldn't get root. From there I decided to use the tutorial where I am not stuck in a boot loop:
[VIDEOS] Galaxy Tab Pro 8.4 How to Root Install Recovery & Rom on your device
All is well until the system reboots where I get the blue alien head with radio-like signals pulsing at me. This animation never ends even after waiting many minutes.
Odin3 messages:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I suspect something went wrong a year ago and it may be possible I need to clean this further. What do you guys suggest I do? I have backups on the SD so I don't care if I need to go back to clean system. I am able to get into recovery (now stock vs TWRP) and download mode.
Thanks!
I was searching threads because I have a very similar issue. I rooted my Pro 8.4 months ago and installed cm12. The tablet has had a hard time staying rooted. When I tried to install nightlies updates to cm12 I usually had to re-root. Ugh.
Fast forward to last night - I re-rooted the device, installed CM13, and when the tablet tries to reboot, all I get is the CM boot screen with the blue face guy. It never gets out of that phase of boot. It also doesn't charge when plugged in. Basically it is now bricked. I've got backups on my sd card.
Not sure what to do now. i'm not trying to take over the therad, just want you to know you aren't alone!
I ended up fixing the issue and then forgot to report back here. Although this isn't as detailed as the problems, here are the steps I took:
Downloaded Samsung Kies, Kies3 and Smart Switch because I wasn't sure which program was compatible with my device
Found that Kies3 was potentially the correct program but watched a youtube video on using the extra menus of Kies3 to restore to factory default. You need to provide the exact model and serial number (located on rear of tablet). You need to connect the device in download/fastboot mode (Volume Down + Power button). Volume Up + Power button is recovery mode.
After restoring to factory default, I re-rooted using Chainfire's method (located in one of the links for the main thread for this device at the XDA forums)
Once this was done I installed the TWRP Manager (ROOT) from the Google Play Store
From here I installed CM13 Nightly (modrianwifi) and Open GApps (Google Apps). Success, but the problem is that I'm still not rooted.
Attempted to install the zip of Chainfire's SuperSU via TWRP but iirc, this was 2.45. I'm again in the same position where I have the infinite radio beacon alien head, but at least I still have TWRP for the recovery rather than stock.
Determined after research that it's highly likely that Chainfire's SuperSU at 2.45 and below is NOT meant for CM13 because it's using Android 6.0.1 (Marshmallow).
Found Chainfire's newest beta SuperSU-v2.62-3-20151211162651.zip
From TWRP, wiped Dalvik cache, cache and formatted storage. I then installed CM13, Open GApps and SuperSU at one time but this time making sure it was the new beta zip (TWRP expects zip files for install)
Success! CM13 and fully rooted. Installed F-Droid for superior open source software and less intrusive programs. Installed various utilities to determine root status. Some of which are: F-Droid, Root Checker Basic, Terminal Emulator, FTP Server (Demo) and Wifi Privacy Police among others
Not yet tried:
Installing new CM13 Nightlies and rebooting (going to avoid this for now)
AustinTech, if you are eventually able to get to download mode, I think you have a good chance of success. When I had first rooted around a year ago, I also thought I may have bricked the device and don't recall the charging LED being lit when the device was plugged in. You might try plugging it in overnight, unplugging the next day and hold the Power Button + Volume Down in for at least 20 seconds. I've found most hard shutdowns and boots to be around 10 seconds but it may be longer when the device is in your state.
I also liked using Kies3 because the various firmware download sites attempt to extract money and are generally slow since you aren't a premium member. Outside of that I don't yet know of a way to verify the firmware files are what they seem to be since I can't find official hashes (MD5, SHA1, etc). Using the official software, it would seem much less likely to have corrupt or manipulated data.

Possibly Bricked I9192! Can it be fixed?

Last status
Code:
Device: S4 Mini I9192
ROM: CM13 by k2wl
KERNEL: REMIX
RECOVERY: TWRP 3
So, let me tell you a sad story!
Yesterday I was talking a nap while my phone was charging. There was load-shedding, but my phone charged on IPS. But later I saw that it was showing the boot-up animation. I let it happen, but when I returned the phone was showing the "Samsung Galaxy S4 mini GT-I9192" splash screen and it was stuck there. I removed the battery, and reinserted and it was the same. I tried to boot up to my recovery, but after the splash screen, it was stuck on TWRP splash screen.
After a few try, I thought maybe I should wait for TWRP, maybe its doing something in background. Guess what, TWRP booted. When I checked log it was full of "unable to mount" error with various partitions. I was happy for a moment. So after that I tried to reboot to system. Now, there wasn't even any splash screen either. Tried to boot into recovery but even recovery isn’t booting. So I entered the download mode.
Code:
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
Then I tried to flash the TWRP with Odin 3 v3.09 but it was stuck on:
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
When I unplugged the phone while stuck, two more lines appeared:
Code:
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
At this point I lost any hope of recovering data and so I’m ready to flash a PIT file too. So I did some research and found the PIT file and tried flashing it. Odin was stuck at “Initialzation” again. After a few Google search, somebody suggested to use an old Odin, so I downloaded Odin3 v1.85 and retried. No luck but the Odin log was different
Code:
<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> Complete(Write) operation failed.
Now I’m totally hopeless as I think the built-in storage is somehow corrupted so that even Odin can’t write it.
Few interesting things:
ADB cannot properly run while the phone is plugged in. ADB shows "server out-of-date" error. Then kills and return nothing. If repeated, same thing. Although all Odin recognizes the phone.
I tried a method of debricking with an img file on a sd card, but it fails on "parted" for some reason.
Kies keeps on showing "Connecting".
If nothing can be done, I'll just have to take my home to the repair shops. But will they be able to fix it? Any thing I'm missing?
I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.
komor555 said:
I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.
Click to expand...
Click to collapse
What exactly should I do using the Android Toolkit?
Run the software, let it download all the stuff. Next in the main menu, there are a few input options. First of all, try "I" with your phone connected and in download mode, to see what kind of device info the phone will return. If nothing shows up, try "DR", which will install drivers to work with adb, fastboot and recovery, on your local machine. You should do that even if you get the device info in the first place, just to try getting it again after driver installation for comparison.
Next, input 24 to run galaxy s4 mini module. Let the utility download and install all the module updates. After that, select DUAL SIM GSM MODEL [GT-I9192] by writing "02". It will ask for the android build, select the newest one (option 22). If you have a custom build, then you will have to unlock the Pro version by donating, but there might be no need for that, if option 22 works. Again, let it download.
Then you get access to a variety of options. First, unplug your phone, and run option 1 to install device drivers to your PC. Then, if you are lucky and ADB works, you can Install a .zip file using sideload (option 16) to your phone. Or you can just play around with other options. Maybe something will work. If the download mode works on the phone - that's usually a soft-brick, which is fixable.

Categories

Resources