Develop Bugs

[Q] flashing with heimdall ?

hi,
i have a Gio S5660 that i bricked trying to sim unlocking it before putting it on sale.
the device can get into Download mode (no recovery mode though) but Odin 4 doesn't flash anything anymore, tried different roms (stock, moded, froyo, GB) nothing works, Odin 4 says PASS but after rebooting the screen keeps on blinking the ugly Samsung logo.
i tried to make a Heimdall flashing package but when i try to load a rom into the packager i get an error that says no Firmware.xml found.
is it even possible to use Heimdall or other Odin versions to flash a Gio, if so how do u make a package for that ?

supermario00 said:
hi,
i have a Gio S5660 that i bricked trying to sim unlocking it before putting it on sale.
the device can get into Download mode (no recovery mode though) but Odin 4 doesn't flash anything anymore, tried different roms (stock, moded, froyo, GB) nothing works, Odin 4 says PASS but after rebooting the screen keeps on blinking the ugly Samsung logo.
i tried to make a Heimdall flashing package but when i try to load a rom into the packager i get an error that says no Firmware.xml found.
is it even possible to use Heimdall or other Odin versions to flash a Gio, if so how do u make a package for that ?
Click to expand...
Click to collapse
After flashing with odin and get in bootloop, press the power button for 10 seconds, after restart press home and power until get in to recovery, there should factory reset and the most important - fix rfs or something, can't remember now exactly, the phone will reboot automaticaly and you have to wait some time to boot.

Which method did you try to unlock it with?

HEllo,
Same problem, keep blinking trying to boot with Samsung white letters.
FR

What, and how EXACTLY did you tried to flash with odin? (Which rom, Onepackage/multipackage, tar/md5...?)

Hello,
Still fighting to bring it into life.
Well the problem began when unlocking with the thread instructions:
http://forum.xda-developers.com/showthread.php?t=1204705
Everything seemed to go as expected but...
After that it never rebooted well, still in cycle on www.samsung letters firs screen.
Even so i tried to flash it with ODIN into Stock Rom 2.3.5 and the same problem.
Sometimes i still can have the "Recovery Mode" and flash other versions, i have the PASS message ok, but when reboot... same problem.
And with the Oneclick Unbrick recovery it fails...
Really worried abou this... nice brick!
Thanks to all that are trying to help!
At the beginning of the process it hads the 2.3.3 version locked to Vodafone.

Maybe you just misspoke, but you can't use Odin if your phone is in recovery mode. It has to be in downloading mode.
In my opinion:
1. Boot into recovery (are you using cwm?)
2. Do a factory reset+wipe everything (incl. dalvik cache)
3. Turn off the phone
4. Download the latest ROM from here: http://forum.xda-developers.com/showpost.php?p=16979769&postcount=547
(S5660XXKS2)
5. Boot your phone into downloading mode
6. Flash with Odin (this is NOT "One package", you have to put everything in the right spot /boot, phone, etc/)

Hello again,
Yes i mean Download mode, i', flashing with ODIN but "one package Versions" i'm goin to try next your link already downloading.
Even if i can not unbrick it (wich is strange because i still can flash it) i must thans you very much for great cooperation!
Working...

You're welcome. When I bricked my phone, this is how I got it working again. I hope it works for you too.
Keep my posted...

Hello again,
Well just flashed again with ODIN (not One Package) and last firmware (2.3.5) and the report is that at the end i have the PASS confirmation but phone keeps flashing and does not reboot alone as supposed (waited 15 mn).
Unplug USB cable, battery out, battery in, power on and it returns to its "preference": alternates between dark scredn and those White letters saying SAMSUNG... infinite loop.
This is strange, i'm tired of seaching everything and this is not a normal beahaviour for this procediure.
I can follow all the steps... and at the final... same result.
Don't really know what to do next.
Once more, thanks for all!
Fernando

I'm sorry it didn't work. I have one last suggestion. The firmware you just tried to flash has a few md5 files. Rename them to tar, an extract them. The files you will find inside are the ones you can flash with Heimdall (data.rfs, system.rfs, etc).
I can't tell you much more, because I never used it (just googled a bit right now), but you can probably find a few tutorials about the subject.

Hello,
The fight continues and for all that i've read so far i almost sure that someting happend with the EFS partition.
I think that, case possible, the way is trying to flash an EFS new partition.
Someone knoes ho to do that?
Thanks!

descobrindo said:
Hello,
The fight continues and for all that i've read so far i almost sure that someting happend with the EFS partition.
I think that, case possible, the way is trying to flash an EFS new partition.
Someone knoes ho to do that?
Thanks!
Click to expand...
Click to collapse
please give more information about stuck on logo (ex: logcat)
and dont play with EFS partition. its very dangerious.
it can really bricked your phone

When you can go to recovery mode with your gio you should flash ext4-formatter.zip(download,put on sdcard,go to recovery find `installzip from sdcard` and flash it.
the internal phone memory has to be in ext4 format ,if not you have the above problems.
after flashing you can install a rom.
By the way,i tryed flashing with heimdall-frontend ,i think it can ,but you have to rename it to a .tar gz file it wil be compiled automatic adding it to heimdall,but...than it says
`firmware.xml is missing from the package` , so...you have to ad(make or edit an existing one,and insert it in the package) that file... which contains name rom ed , than it probably works...

What is heimdall?

sort of odin but odin doesnt run on linux,for flashing

SOLUTION!!
Hey , I figured out a while back how to sort this out... Odin works,The reason though it bootloops is just that the \Data and \Cache Partitions are still in Ext4 Format... Stock Rom uses RFS... So The Solution is - After you Flash Your Stock Rom Via Odin, after it says "PASS" , Unplug USB then Reboot into the stock recovery mode by Holding HOME and POWER Button , Then format Cache and Then Wipe Data/Factory Reset (By doing this it formats back to RFS and then it can operate) ... then reboot to system ... And Voila , It works!!!! (Always works for me)... Hope this Helps Just Remember to USE ODIN (Heimdall apparently not Gio Supported)

[Q] galaxy s3 I747 wont boot past Samsung Galaxy s3 Logo, Did i brick my phone???

I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.

KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.

[Q] TWRP brick

OK, I did search and found nothing. So, I need to ask this somewhere, hopefully this is the place. The similar threads search did not seem to help much.
I have a Tab S 8.4 WiFi. I rooted it and was running Cyanogen 12. I noticed the TWRP 2.8.3.0 update, so I went to install it. TWRP manager kept crashing, so I went to the TWRP site and downloaded the SM-T 700 klimti wifi img file. I used Flashify to flash this, as I have done numerous times. I wish I'd extracted and flashed the zip in TWRP, but I did not. Everything acted normal but when the tab went to boot up it got to the Black screen that announces Samsung Galaxy S, SM-T700, Powered by android. This was it. It flashed this screen constantly every second or so. Non stop. There was nothing any button combination would do. Except it will go into download mode. Nothing else. No hard reset, nothing. Download mode is it. I spent lots of time looking at various tutorials to see what I'd missed, nothing but download mode. So, I had Odin on the computer and the latest firmware from SamMobile, so I figured I could start over and get the tablet functioning. I've used Odin a fair amount before, including the original Galaxy, S III, S4, so I'm not unfamiliar with the process. I've yet (until now) had the privilege of having a wreck like this one.
So, Odin acts like it is doing its thing, runs through all the steps, says at the end Pass and all threads succeeded, none failed. At the end of the Odin process the tablet acts like it is booting. Up comes the Samsung name with the Bluish sparkly oval along with the standard Samsung tones we hear heading into the boot. That is as far as it goes. The blue and pink colors fade out and I am left with a black screen with SAMSUNG in the middle. Again, no button combination except download mode works at all. It just stays there. Pass showing proudly on the Odin screen (EDIT: I left it there for an hour or so to see if boot would finish before disconnection). I downloaded and tried flashing all of the various firmwares, same result. I even let the battery drain to zero hoping that would shut it off. It seemed to, but the results were the same, only the download mode combination will do anything. The power button starts up the phone in an initially normal manner, but it goes right to SAMSUNG in a black screen.
EDIT 2: I used the Cellular South firmware, saw nothing else US and thought I remembered reading this was what worked here.
There is likely user error here (and realize I might kick myself in the end...Oh wait, I already have), but I've run in circles enough to realize I'm probably doing the same sequence with the same error and I not able to see what it is.
Does anyone have any idea what is wrong or how to fix this? I hope it is fixable. I had hope since download and Odin at least go through the motions. I would greatly appreciate any advice, suggestions, or help. Thanks in advance.

Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?

DUHAsianSKILLZ said:
Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?
Click to expand...
Click to collapse
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.

SteveC485 said:
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.
Click to expand...
Click to collapse
What I mean is to flash twrp with odin then flash zips with twrp. If you cant reboot into recovery, if you installed adb then yoi can do adb reboot recovery.

I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.

senel said:
I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.
Click to expand...
Click to collapse
Thanks. When Christmas stuff winds down, I will give Odin a go. Thanks to both of you who answered. Merry Christmas.

OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.

SteveC485 said:
OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.
Click to expand...
Click to collapse
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.

DUHAsianSKILLZ said:
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.
Click to expand...
Click to collapse
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.

SteveC485 said:
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.
Click to expand...
Click to collapse
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.

DUHAsianSKILLZ said:
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
Click to expand...
Click to collapse
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.

SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.

DUHAsianSKILLZ said:
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
Click to expand...
Click to collapse
Thanks, that's what I thought.

For whatever reason, this time the power, home, and volume up combination booted me into TWRP. Restored a backup and everything is up and running normally (at least so far).
I'm perfectly willing to admit error,but don't quite know where my error came in. I would swear I used the power, volume up, and home combination when I hit the download mode. But maybe not. I don't know why it worked now, except that I was inadvertently hitting the wrong combination, thinking I was doing it right. I remember thinking the first time it went to download mode, that I just did it wrong and used the wrong volume key. Thought I was more careful the succeeding tries.
At any rate thanks for the help. I will remember this particular lesson for a while .

hard brick
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...

faztecnyk said:
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2838473

DUHAsianSKILLZ said:
Try this http://forum.xda-developers.com/showthread.php?t=2838473
Click to expand...
Click to collapse
Thanks.. but I said hard brick and not soft brick..

SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
A lot of Tab S owners have had issue with TWRP 2.8.3. There is another thread on it. I installed 2.8.3 with Odin and it was pretty wonky. Went right back to 2.8.1.

If none of the methods worked for anyone try this. If your tablet keeps trying to boot into twrp or stuck at the galaxy tab s screen try this if you cant boot into download mode.
Let completely die. Then put it in the charger and quickly press the combination of buttons to get into download mode. That should over ride booting into twrp. another way is to plug it into your computer and try different combinations of buttons.

I have the samsung galaxy tab s 8.4 and I rooted it a few days ago and I thought to myself lets install a custom recovery, but before I did that I backed up my stock kernal and my stock recovery through flashify, also im on stock firmware, after I backed those things up I installed twrp 2.8.3.0 and I booted into recovery to back up my rom and data just in case I soft bricked my tablet like I used to do on my nexus 7, when trying to boot into twrp it went in to boot loop I have tried all button combination I know and have seen in this thread but none works except for going into download mode. I dont know if I should flash an older version of twrp and see if it works or should I install stock firmware on my device and im not sure what version of odin I should use if I flash a older version of twrp. The version I used to root my tablet is 3.07 of odin.

[Q] Broken screen - how to factory reset?

I have a Sprint Note 4 that supposedly had a custom ROM installed on but I believe the digitizer is broken. Nothing shows up on the display. I booted into DOWNLOAD MODE using Home Power and volume down and flashedN910PVPU1ANK2_N910PSPT1ANK2_SPR then N910PVPU1ANIE_N910PSPT1ANIE_SPR via ODIN It sounds like its stuck in a boot loop after both flashes, but ODIN says PASSED when it finishes. Since I can't access the screen, how can i get this flashed back to a stock rom? Any help would be greatly appreciated.

I'm confused; why flash two stock tars? Did you let the phone boot after flashing the first stock tar?
I'd suggest a factory reset in recovery, power down, Odin the factory tar of your choice and let it auto boot. You should see the phone boot into into recovery briefly on the auto boot when flashing stock tar in Odin, then fully boot. If not seeing the brief recovery, start over and try again.
I recall a YouTube video on a digitizer issue that may have been resolved. The guy had a dead spot on the digitizer. I think it only suggests a possible fix in a follow-up video the user posted. But maybe the stock tar will fix it.

why flash two stock tars?
After flashing the the first one, it just kept rebooting. That was last night. Today I flashed the older one. I'm trying install ADB on my Windows 7 desktop to enter recovery.

So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.

samep said:
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
Click to expand...
Click to collapse
I tried without SD card and I didn't check repartition in ODIN. The md5 matched on both.

Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.

samep said:
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
Click to expand...
Click to collapse
How can I use TWRP without the screen?
thanks

Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.

samep said:
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
Click to expand...
Click to collapse
I went by feel....and the fact that Odin said COM connected. and PASSED

kevg77 said:
I went by feel....and the fact that Odin said COM connected. and PASSED
Click to expand...
Click to collapse
So you pulled the battery, pressed and held volume down, home and power buttons until it vibrated, waited to make sure it wasn't just booting, when satisfied, you pressed volume up; right?
I'd say that is a sufficient feel.
If the Odin or kies update won't take and screen is dead; with no adb access, who would know what's on the phone unless it's just not playing the right boot tone when it keeps rebooting? Problem?
I think that may be enough to take your phone back to point of sale and ask for replacement without worrying about root voiding warranty?
Did you try the Kies update?

I am familiar with the Note 3, thats how I was able to get it into Download mode by feel. I tried KIES and it said that my device is not supported. Im using the latest version of KIES. I know I'm running into an issue with the usb driver recognizing...Im on Windows 10 technical preview. thinking about trying it on an old Win7 laptop.. thanks for the advice

[Samsung] Galaxy Tab 3 SM-T210 / "Firmware upgrade encountered an issue"

Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie

Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?

xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.

Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!

You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!

Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.

Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?