yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
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?
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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. :)
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] senel:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
Thanks. When Christmas stuff winds down, I will give Odin a go. Thanks to both of you who answered. Merry Christmas.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
? 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.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
Thanks, that's what I thought.
[Galaxy Tab S Q&A, Help & Troubleshooting] SteveC485:
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. :o 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 :).
[Galaxy Tab S Q&A, Help & Troubleshooting] faztecnyk:
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...
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
Try this http://xdaforums.com/showthread.php?t=2838473
[Galaxy Tab S Q&A, Help & Troubleshooting] faztecnyk:
Thanks.. but I said hard brick and not soft brick..
[Galaxy Tab S Q&A, Help & Troubleshooting] nozeit:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] TMG WHITE DRAGO:
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.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
I put a warning about using twrp 2.8.3.0.! There's a problem with that version of twrp which gives bootloops. Do not install stock firmware yet! Install twrp 2.8.1.0 or some sort and it should boot.
[Galaxy Tab S Q&A, Help & Troubleshooting] TMG WHITE DRAGO:
I have read your post but I think the worst of things and wanted to make sure that I should flash an older version of twrp first before doing it. And does it matter what version of odin I use
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
Nope. You can use any Odin. Just flash twrp 2.8.1.0 and it should fix your problem
[Galaxy Tab S Q&A, Help & Troubleshooting] OutOrpheous848:
Works Great

Had the exact same issue. No need to look any further for a solution. This works great. This took about 10 seconds to fix by flashing twrp 2.8.1.0. Back up and running with no issues.

Thanks.
[Galaxy Tab S Q&A, Help & Troubleshooting] b3aucb:
TWRP v2.8.3.0 -- Steer Clear

Before I realized there was something wrong with the 2.8.3.0 version, I tried to getting it to install via TWRP Manager (failed with errors) and then via Terminal Emulator (different errors). By luck alone, I decided to try the 2.8.1.0 ver the same time I decided to try Flashify and I had NO Problems. Based on this thread, tho, the 2.8.3.0 ver probably ought to be pulled down for now.
[Galaxy Tab S Q&A, Help & Troubleshooting] BlackStorm:
Hi everybody,

I tryed to install twrp on my rooted Galaxy TabS 10.5 LTE, SM-T805. I installed TWRP from the playstore.

This works fine. But when I try to install the recovery image the app crashes, always.

In every version: Chagallwifi , 2.7.1.1, 2.8.1.0, 2.8.3.0.

Download works fine and after downloading, in the flashing process, the app crashes. Does somebody know, what to do?

Thanks in advance.

Best regards

Black
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
This is a known problem in the app. I belive you can use flashify as an alternative. But using odin is recommed and please flash only 2.8.1.0 and below. Do not flash 2.8.3.0! Go check out the twrp thread for a how to on how to flash with odin.
[Galaxy Tab S Q&A, Help & Troubleshooting] Eliminater74:
After reading though this thread, I decided I would add a few things to the subject at hand.

First. let me tell you what I have in devices so you can get an understanding to what im saying:

LG G3 T-Mobile (Unlocked)

LG Optimus F6

LG Optimus L9

Samsung Galaxy Express (SGH-i4735z)

Samsung Galaxy S Tab 10.5 Wifi (T800)

Samsung Galaxy S Tab 10.5 Wifi/LTE (T805) Unlocked International Edition

I had TWRP on all devices Listed 2.8.30 only on G3 and both samsungs. I had no problems with the flashing and somewhat the operation of recovery.

But I noticed that TWRP wasnt working like it should. Then after enough reading up on PHILZ Touch Recovery.. I have moved over to that.. And have had no problems so far. In my Eyes

TWRP isnt up to par like it should compare to the others and PHILZ is just CWM on steroids.

As to flashing stock rom with ODIN , I always Check Nand Erase all. Which everyone here will say not too. but after you flash with that checked.. you will have to boot into recovery (stock) or flash a recovery, before it will boot all the way. Since it corrupts /data. Then when in recovery Wipe Data/cache.. then it will reboot fully with no problems..

This only answers the problem of it sitting at samsung screen after flashing with ODIN.. And my opinion on TWRP as well as PHILZ Recoverys..
[Nexus 4 Q&A, Help & Troubleshooting] SimonP2:
I wonder if anyone can help.

My Nexus 4 had updated itself happily to Lollipop 5.0 and it was working nicely, except that when the 5.0.1 update arrived it showed the android on its back with a red "!" so I assumed it was due to the phone being rooted and unlocked (although 5.0 had installed without any problem).

I have since upgraded to a OnePlus One so I decided to wipe the Nexus, unroot and re-lock it in preparation for selling it so I used Nexus Root Toolkit (my regular rooting tool) to do all of that. I tried loading 5.0.1 through it and it installed but couldn't see my Wi-Fi, although it did see someone else's. After trying a couple of times I tried 5.0 and that was the same so eventually I tried 4.4.4 and that was successful.

The plan was to leave it plugged in and charging so that it would automatically receive the Lollipop updates but it's been a week now with me regularly pressing the 'check for update' button but there is no sign of them.

I don't think there is any other way to force the updates but can you think of anything that might be stopping them? Nexus Root Toolkit downloaded the images from Google so presumably they're OK, the play store loaded and updated my apps, the time updates when I press 'check for update' yet no O/S updates appear. I can't sell it if it's not updating itself so any help would be much appreciated. It couldn't be because I have OEM locked it could it? I can't remember if it was unlocked when I got it but it made sense to do it.
[Nexus 4 Q&A, Help & Troubleshooting] jd1639:
I would flash the factory image using fastboot to 5.0.1. You'll have to unlock the device again. I'm not a fan of tool kits
[Nexus 4 Q&A, Help & Troubleshooting] WugFresh:
In the toolkit options enable "Force Flash Mode" and try again; this will fastboot flash the img files individually and overcome the issues with Google's new Lollipop factory packs, where the fastboot update cmd, is not working properly (as written in their own incldued flash-all.bat).

In the future.. rather than PM'ing me and making a thread.. just post in the NRT threads.

{{ WugFresh }}
[Nexus 4 Q&A, Help & Troubleshooting] SimonP2:
It took a lot of fiddling about and several boot loops but eventually I managed to install 5.0 (using NRT) and it updated to 5.0.1 (which is what I wanted to see to be sure it was working alright before I sell it) so all is well at last. Thanks for the suggestions.
[Galaxy Note 4 Q&A, Help & Troubleshooting] CShart:
So i recently got the Samsung Galaxy Note 4 (SM-N910F). And i rooted it as i always do with my other phones they´ve worked fine every single time. But this time something happened to it when i rooted it. I used ChainFires Auto-Root. Worked perfectly fine untill reboot then my phone got stuck at the samsung logo and stayed there for ages and ages.

Then i let the phone be off for a while and i come back to something im not used to. And the error was That my firmware upgrade encountered an issue and that i should go into recovery and try again. I´ve tried flashing my note with the Stock Rom from sammobile but just at the end i got an error. Volume size is too big 12880 < 204800

odin : Invalid ext4 image

I have no clue what to do anymore so i came to this site and wondering if anyone does know what my problem is.
[Galaxy Note 4 Q&A, Help & Troubleshooting] CShart:
If someone could delete this post id be grateful found a way that worked for me.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Chefproll:
And why do you wish to keep the solution a secret ?
[Galaxy Note 4 Q&A, Help & Troubleshooting] AMKhatri:
Please share your solution...
[Galaxy Note 4 Q&A, Help & Troubleshooting] dondavis007:
Yes,please share.
[Galaxy Note 4 Q&A, Help & Troubleshooting] CShart:
Oh damn sorry for not posting it totaly forgot. But what i did was I downloaded a recovery that was said to work on all Samsung Mobiles (4shared. com/get/bIYubEevba/All_samsung_recovery.html) And then i just used Odin3 V3.09 and just waited a couple minutes and then the phone booted up just as normal. And working like a charm right now.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] DeniaL:
Is there an App that I could use to start cooking my own version of ROMs...besides that rom koch program because it doesn't work well. Thanks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Arktronic:
See ROM cooking section: http://xdaforums.com/showthread.php?t=295751 (it's a sticky in this forum, BTW)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] dutty:
what is the prob`?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] monx®:
koch is currently the best ever.

salute for u dutty !
[ONE Accessories] kolence:
Mod Edit read the Forum Rules
[ONE Accessories] Galactus:
To SELL? Good luck with that
[ONE Accessories] kolence:
yep, i bought phone and got those 3, already sold few
[ONE Accessories] Clark Joseph Kent:
Not here or via the PM system....
[T-Mobile, Samsung Galaxy SIII] chalky7880:
For some reason when I try to Odin the newest nf4 firmware, everything seems to go ok but my phone won't come on. Just stays stuck at the tmobile t999l screen. I've flashed the nf4 modem but I wanted to flash the bootloader to go along with it. If anyone has any input I would appreciate it. Thanks.
[T-Mobile, Samsung Galaxy SIII] serio22:
Did you factory reset?
[T-Mobile, Samsung Galaxy SIII] chalky7880:
No. Should I do that before Odin or after?
[T-Mobile, Samsung Galaxy SIII] serio22:
Either one
[T-Mobile, Samsung Galaxy SIII] chalky7880:
Thanks [MENTION=4715351]serio22[/MENTION] that did it. I don't think I've ever had to do that before.
[T-Mobile, Samsung Galaxy SIII] serio22:
It's always recommended, especially if going from aosp/cm otherwise you will get stuck at startup
[Galaxy S 5 Q&A, Help & Troubleshooting] thaskitz:
Hi all

I downloaded and updated the firmware, i got the boot logo, then the updating of android apps, then the boot logo again, the lockscreen loads up and then after 10 seconds, no matter what i do the phone automatically reboots and does the same thing over and over again,

Anyone have any ideas? i have re downloaded and reflashed the firmware, im a bit stuck

Many thanks in advance guys
[Galaxy S 5 Q&A, Help & Troubleshooting] AlwaysAndroid:
Try booting into stock recovery(volume up+home button+power button) and factory reset it. I had kinda the same problem and this helped.
[General Questions and Answers] CartoonmanPDC:
I need to see if I can reflash a different version of CWM recovery on my device. I can only get into recovery, not the regular OS, so I am limited to limited ADB access via CWM's adb . How can I do this?

The only thing that boots is recovery, and thats it. For some reason, logcat doesn't seem to work in recovery, so I can't delve into what the issue is.

I've tried flash_image to no success. It keeps giving me -1 error, no matter what I do. fastboot doesn't work because it needs the OS running. Doesn't work in recovery.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Gl2u81:
I have Verizon Galaxy Note 3, and my problem is that Wifi button is greyed out and simply wouldnt turn on.

I have done a lot of homework so far, and before, I had 4.3 Jelly Bean, and Wifi being greyed out started around 2 weeks ago (early Dec/2014 - until then, it worked fine).

So I updated to 4.4.2 Kitkat thinking software issue, but wifi is still not working.

I had already searched for hours, and did many things to try to isolate the problem.

*I tried Safe mode

*Reset Cache/Factory several times

*Battery in-n-out, SD card in-n-out, any external peripherals i had alrdy taken everything off and tried

*Tried Alliance/Jasmine/Eclipse ROMs, but still same

*Not router issue @ home since Phone Wifi simply wouldn' turn on

I thought of downgrading back to 4.3 Jelly Bean, but there were many articles saying I can not downgrade, so I think it's out of option.

I now think it's hardware issue, but can not confirm... went to Verizon store too, and the guy just feels it's more software by 51/49, but the ultimate problem is that I just can not 100% ID what the exact problem is - software or hardware.

I really don't want to spend $ for another phone... I also feel it is Kitkat since I also found many articles with Note 3 Kitkat wifi problem, and I read a lot of them, but couldn't really find any solution to my specific issue.

My understanding is that I have 2 options - wait for proper fix by Dev/Samsung for Kitkat firmware or get a new phone

I really did everything I can within my power, and making this post is my last resort...

Hope I can shed some light from experts or anyone who knows any more beneficial details so that @ least i can try to sort my options and situation more clearly...

Thanks much in advance!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] KennyG123:
Have you tried using Samsung Kies to return to complete stock? Why didn't the Verizon tech offer this choice and flash stock firmware?

My guess is you have a baseband/firmware mismatch somewhere. 4.4.2 firmware and baseband can be found in this thread.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] drewcam888:
Or flash nc4 in odin.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Gl2u81:
mmm no, and i got this phone from Amazon (not from Store), and the store workers really didnt know how to Root nor XDA forum, so it was talking to a wall...

Lemme check our your link and see
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Gl2u81:
ok, i did already check out your thread before, and when i had tried to download 4.3 (1st one), it had me download like .exe file, and these kind of files tend to be virus/spyware so i just didn't... i also read many posts about how i can NOT downgrade to 4.3 from 4.4 so software wise, my current understanding is that I am **** out of luck until someone fixes firmware... or am i wrong? I guess I am trying to be proven wrong, and hope someone can show me a solution to my weird unique problem...

Btw, already on NC4 (I had updated to NC2 firstly, and Jasmine got stuck on bootloop, so I got NC4 and used Odin, then it fixed the bootloop)

Merry Xmas, huh?

P.S. Thanks for replying on Xmas day, lol
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] drewcam888:
Correct you can not downgrade. Flash nc4 in odin.

https://www.androidfilehost.com/?fid=23487008491963309
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] KennyG123:
You specifically stated in the OP that you went to the Verizon store. They should have just flashed the most recent firmware/OS at that time.

You need to just Odin the latest stock tar or use Kies to do the same. Somewhere along the way the baseband, firmware and ROM OS have been mixed which causes the wifi problem.