Related
Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!
Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.
voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.
Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
delete. ......
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.
chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.
amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu
The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App
jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?
take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power
Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!
Hello, just picked up a used tab s t705w bell in good shape. Ive tried to flash the original 5.02 as well as autroot and another original image as well. All of them fail. Im using the latest version of Odin. The connection says its ok as per com port than when it gets to boot.img it stops and fails. Ive tried 2 USB cables as well as all my USB ports to no avail. Please help as to what I'm doing wrong, thanks.
Heres a pic
Update: tried with laptop still same thing, is there anybody that can offer a suggestion? I even unplugged the battery and plugged back in. I also tried several older versions of Odin.
Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.
cesandoid said:
Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.
Click to expand...
Click to collapse
Hi,
Did you end up fixing the issue? I think I have the same issue as yours on a SM T800. It came with 4.4.2 so when I tried to update to Marshmellow it failed and it restarted fine, and it told me to update via my pc using Kies or smarth switch. So I did so and guess what happened Smart Switch failed as well but now it bricked the tablet. So when Smart switch tries to install the recovery, same thing. So I now have a brick! So I am trying to find out if there was a solution or not. If not I will just have to wear it.
Thanks.
hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX
tex_kit said:
hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX
Click to expand...
Click to collapse
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.
wellersl said:
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.
Click to expand...
Click to collapse
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version
tex_kit said:
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version
Click to expand...
Click to collapse
In my limited experience with Odin, I find it to be a very stable, robust, and reliable application. Having said that, and not knowing what version you're using, the usual suggestions are:
Try another (older) version of Odin.
Try another USB cable.
Always use a USB 2 port.
Try a different firmware package making *certain* it's for your model tab. (<- This is what's most suspect - IMHO.)
As long as you can still invoke the Odin downloader on your tab, there's still hope.
Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX
tex_kit said:
Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX
Click to expand...
Click to collapse
PM SENT.
Yup. Been there. Done exactly that. I fixed it by subscribing to SamMobile, then paying for and downloading the OEM firmware. That's probably the best news, You can always get back to a box-stock condition. If you have the patience, you can download the firmware for free.
EDIT: Once I got back to stock, I looked for and found:
DAMMIT! I keep forgetting we have two different tabs. Obviously Klimtwifi is wrong for you.
lineage-14.1-20200321-UNOFFICIAL-klimtwifi, installed it with Odin3_v3.11.2 (Not sure it matters.)
Then rooted it using Odin: https://android.gadgethacks.com/how-to/android-basics-root-with-cf-auto-root-0167401/
And, once rooted, installed the Official TWRP app from Google Play. I always use the next older version of TWRP (twrp-3.3.0-0-klimtwifi) because TWRP doesn't like me much.
Then, rebooted into recovery and flashed GApps (open_gapps-arm-9.0-nano-20200417)
FWIW - This is from feeble memory, and I still have all the files - both those that worked and those that didn't - all in the same folder. So if something doesn't work for you, I've got what worked for me.
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX
tex_kit said:
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX
Click to expand...
Click to collapse
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.
wellersl said:
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.
Click to expand...
Click to collapse
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX
tex_kit said:
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX
Click to expand...
Click to collapse
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning,
Downloaded and installed the latest version SM-T805_t805xxu1cpl1_marshmallow(Android 6.0.1)_Xeh_factory Rom (4 File)_20170111.zip.enc4. (decrypted with an earlier version of samfirm (3.9 ).
the installation procedure of the 4 files, AP, BL, CP, CSC, does not involve problems.
Unfortunately at the end of the procedure the Tablet does not restart automatically, and after its hard wipe reset remains locked on the initial logo samsung always bright intermittently.
During the tests I noticed that holding down the power button tries to start. The second samsung logo stands out completely but does not pass the stage.
The feeling he can’t make it.
A new PIT file?
Tex
wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning, first of all
I want to thank you for your patience and time.
Performed yet another installation test with Odin this time with Android 5 (XEH-T805XXU1BOJ1-20151111094815) similar result, you have precedents.
But with a novelty
.At the end of the installation, the tablet remains off, as in the pretending tests, I try to start it normally but nothing, in addition to the ever-present Logo (Samsung Galaxy tab S) flashing intermittently.
I press the power button for several seconds with the result of making the second samsung logo appear (colored) with an Android loading start, release the button, the device turns off.
By re-activating the flashing logo (Samsung Galaxy tab S) normally.
Holding down the power button starts
Android update - optimization of the accompanying application (192 tot), a few minutes later always with the power pressed, the process ends and the installation of applications begins, after a few seconds, the first APP starts., the tablet turns off.
By turning it on again and the intermittent luminous logo (Samsung Galaxy tab S) reappears.
Repeating the procedure (power button pressed continuously) you get colored samsung logo and the writing (alkalmazàsok telepitèese) installation of applications and turns off.
I perform a wipe data / factory reset obtaining:
--wiping data—
Formatting / data ...
Formatting / cache ...
Formatting / sbfs ....
E: unknow volume for path [/ sbfs]
E: unknow volume "/ sbfs"
Complete data wipes.
I run reboot system now.
The tablet turns on with the intermittently lit Logo (Samsung Galaxy tab S).
By repeating the whole procedure previously described, no changes are obtained.
TEX
alkalmazàsok telepitèese?
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?
wellersl said:
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?
Click to expand...
Click to collapse
good morning,
the tablet was working, during a game session started to reboot, always and only with the logo (Samsung Galaxy tab S) bright intermittently, performed hard reset, I did not fix anything. The only news, these days, after Odin, is the complete installation of android 5 with the power key pressed all the time.releasing the tablet key turns off . At the next power on I get the logo (Samsung Galaxy tab S) bright intermittently.
thank you for your patience and professionalism
Tex
This is the screen you see *before* you invoke Odin and connect the tab to your PC?
View attachment 5009263