Related
Hello, I wanted to ask if anyone knows how to resolve a SEMI-BRICK. There is no way to enter recovery mode or fastboot.
Was installing a ROM when I got an error and never could turn on the phone. Only I get the screen with the mobile and pc with an exclamation mark in the middle.
Appreciate your help.
PS: sorry for my English
Javier
If you can't get to download mode you might be screwed. Can you get into download mode? If you can then you can just use odin or fastboot to push the factory rom to the phone and it will work again. Obviously you lose root but you can re-root afterwards. Good luck.
I find no way to enter download mode. in any way that I only try to turn the screen appears to indicate in the query.
There is no way to fix it?
thanks
Hey, in all the time on here I have never heard of a bricked Nexus.
Ok so just to be sure when the phone is off and you hold volume down and the power button it does nothing? Sorry just want to be sure this is the case...
probe all possible combinations and all leading me to the same, the screen with the exclamation mark. and on volume +, volume - and power and volume + and - and on
Ah no dude. That sounds bad. I might be wrong but you may need to go back to your provider and tell them it just switched off and wont work anymore.
Do you see the Google logo and the lock symbol when you turn it on or just this exclamation mark?
Obviously if you go back to your provider don't mention anything about roms or rooting as that voids your warranty but if they can't see the Google logo with the lock then they wont know you were rooting and romming it.
That would drive me crazy so I hope you get sorted soon.
The issue is that here in Argentina is not this phone. I bought online and sent me the U.S.. I have therefore not who wear it.
have you tried the usb jigs? i tried it on my nexus and it boots it into download mode
IINexusII said:
have you tried the usb jigs? i tried it on my nexus and it boots it into download mode
Click to expand...
Click to collapse
That might be worth a shot!
That I'll see if I can prove it today night. It is the only hope left for me.
Yeah, good luck man.
Well folks, with all the pain of the soul I confirm that I have is a full-BRICK. Last night at the JIG probe, and the only thing it does is turn on the phone and see the same screen BRICK. Since I can not think what else to do, only use it as a paperweight as they say
Any chance you try leaving battery out for a while, give it at least a good 10 minutes
Neither. I've left it up all night without battery and nothing.
javiiperez said:
Neither. I've left it up all night without battery and nothing.
Click to expand...
Click to collapse
Bad news Javii! So what are you going to do next?
Today I will try to recognize me either linux, so maybe you can do a fastboot to install the original rom. Because I said if you see the exclamation point is because it is a semi-brick
I used to get that screen with my Galaxy Tab when flashing the wrong ROM.
If the ODIN and original files are available for you to use, just use that and it should fix your phone.
CDMA GALAXY NEXUS> Hey guys, I was running Romanbb's 4.0.4 build earlier today. I clicked on a video (which may or may not have been on a porn site) all of a sudden my screen went all wacky. Where it was kind of fuzzy and running diagnal across the screen. I could only see part of it. I thought I might have gotten a virus or something because i have never had one of my devices do this before. So I immideatly rebooted the phone into recovery and wiped eveything including formatting system. I went to flash a nandroid I had of black ice and in the middle of flashing that my phone rebooted itself and stayed there (bootlooping at the google logo) I can get into fastboot and I can get into recovery about one out of every ten times but I cant do anything in recovery because the phone turns itself off insted of booting recovery most of the time (I have clockwork touch) When I do get into recovery without it turning off it reboots if I try to flash anything. It seems to be stable in fastboot (thank god!) but When I get it connected in Wugs Root tool kit and try to flash the stock image it goes through the motions and says FAILED on every step exept the first (which I believe is checking radio). It says ( error too many links) on the first two) and I cant remember the error on the last four but I have tried it a couple times so I can replicate it if needed. Can anyone tell me what to do from here? I really appreciate in advance!!! If this is a hardware error then I would like to get it back to stock to get it replaced. It is weird that it happened while running a rom. Its not like I messed up while flashing or anything.
ADB will recognize it in Fastboot. I already set all of that up when I rooted. when I try to flash the stock+unroot option on wugfresh's toolbox it errors out on every step like there is something wrong with my internal sd on my phone? Im wondering if I should try odin. IDK? Im hoping somebody who has seen this or had this happen before will save the day and tell me what to do.
lol why did you rush into CWM and start wiping things? you should have let it reboot and it probably could have been a one off..
you can try this http://rootzwiki.com/topic/14145-od...actory-odin-restore-402-with-radios-unrooted/
It is stable in fastboot but in cwr it is still geeking out
It still is glitching in cwr. most of the time it either turns off or reboots when I try to go into cwr. i can wipe but if I flash anything it freezes at the point where it starts writing to storage. I have never seen anything like this before.
I have now tried oden as well
It looks like it is a problem with the hardware. The phone is only a couple months old if that. So I really wish I could flash the stock image or at least get rid of cwm. but that is not looking likely. Here are a couple pics of odin showing the problem. Any guidace would be much appreciated. This SUCKS
Why in the heck are you trying to use Odin?
I can only get into fastboot and odin.
CWM wont let me do anything. it crashes and reboots into a bootloop if I try to flash anything. The poster above suggested odin. I dont know what else to do. Please help if you can!
Can you get a screencap of when it fails fastbooting the stock images?
yes
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
drumdestroyer said:
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
Click to expand...
Click to collapse
How are you attempting to access fastboot?
Vol + and Vol - and power all at the same time
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
That screen says you (now) have a corrupt partition.
At this point, you must use Odin, which is unfortunate. What URL did you use to download the image? The current image in that thread was on multiupload.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
I downloaded the one later in the thread
Here's the Modem: http://dl.dropbox.co...15.EK02_LTE.tar
Here's the System: http://dl.dropbox.co...L53F_signed.tar
from this thread on page 3 housry23 posted them from his dropbox:
http://rootzwiki.com/topic/14145-od...restore-402-with-radios-unrooted/page__st__30
there were a couple other posts right around the same time with it but they all were the same file name
I thought I saw the same files in the xda thread i found also
I used that thread because it is the one that the second post linked for me.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
loveubuntu said:
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
Click to expand...
Click to collapse
no luck with that. it seems to only open to the "corupted partision" screen. Thanks for the suggestion.
ljwnow said:
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I pm'd you to ask how you could fix it. Just wondering if I could do it. I can follow instructions well. I have never had a problem and have been flashing stuff for a year or so. IDK what happened here.
I can't help but I wanted to share that I had a similar experience. I was bonne stock and clicked on a you tube video and my phone immediately shut down and tried to reboot itself, but only would boot loop. I had to manually reformat my partitions to recover. Sounds like your case might be even worse. Still don't know what my problem was.
Sent from my Galaxy Nexus using XDA
Thanks. Any feedback is appreciated.
so you can't get into bootloader or odin screen any more? if so try using a Jig it works to get the phone into odin mode for me. i used the same usb jig i made for the captivate.
I got the same suggestion from someone else. I have to wait until radio shack opens in the morning and I will give it a shot. Otherwise, I went by verizon and they are having samsung send me a replacment. I would much rather keep this one if I can though
I tried flashing the stock image from fastboot and it failed though when I could get there, and I also tried flashing the stock image through oden when I could get there and both failed multiple times so I don't have much hope. I think something broke.
I am headed to radio shack now. Be back soon with a answer as to wheather I can save my baby or not.
I saw a couple people had the same issue that im now having but none of there solutions solved my problem
i wiped my GS3 for ATT tried to go back to a stock with root rom and when it rebooted it now just hangs at the samsung logo at boot tried re-flashing via odin with no luck also tried flashing a CWM.tar since i cant get into stock or CWM recovery to flash from there is there something im missing i know its late and maybe my brain isnt working like it should
Solved the problem myself.....and rather then just say i figured it out ill share how i did this since i watched countless videos and read endless amounts of threads and since none of them helped mem
First also try t put your phone into stock recovery mode and wipe your phone then flash this should take care of things if it doesnt try what i tried below
and i hope this can help someone else out there who has the same problem that i had all you have to do is the following i did this with obviously an AT&T model should work with others but as always try at your own risk.....
First make sure your battery has a charge even if its stuck on the boot screen its still charging....
then download KIES from samsung update it and make sure you have the latest version.
Next plug in your phone if your stuck at the samsung screen your computer will recognize your phone still at least it did with mine.
Once your done with the above open up KIES goto the top and then TOOLS and Firmware upgrade click on that enter your phone model (ATT SGH-I747) i dont get this part but next it will ask you for your SN and for some reason it doesnt recognize the SN use your IMEI
Now it should ask you a couple questions tell you its wiping your device and you will lose everything etc.....but then it will download the latest FW and begin to install everything and in about 20-25 mins everything will be back to stock
Nvm.. misread.
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
dbdynsty25 said:
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
Click to expand...
Click to collapse
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
yearziro said:
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
Click to expand...
Click to collapse
Yes, all drivers are installed because that's how I ODIN flashed it in the first place! Just stuck on the damn Samsung screen and I can't get Kies to connect to the phone. Not in Download Mode or when it's just stuck on that screen.
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
whit3gh0szt said:
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
Click to expand...
Click to collapse
Worked, thanks! I appreciate it.
it doesnt work on mine
dbdynsty25 said:
Worked, thanks! I appreciate it.
Click to expand...
Click to collapse
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
me neither
mkstf said:
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
Click to expand...
Click to collapse
Yeah I can't get into recovery either, and its getting really annoying.
indieslap said:
Yeah I can't get into recovery either, and its getting really annoying.
Click to expand...
Click to collapse
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
xBeerdroiDx said:
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
Click to expand...
Click to collapse
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
cabato said:
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
Click to expand...
Click to collapse
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
xBeerdroiDx said:
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
Click to expand...
Click to collapse
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
cabato said:
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
Click to expand...
Click to collapse
Sounds like you need to clear your cache partition and clear your dalvik cache. There are several guides on this site to help you. Choose the one that is most appropriate to what you are trying to do and follow it EXACTLY. There is one to start. Follow it from the beginning.
http://forum.xda-developers.com/showthread.php?t=2042775
When nothing else works start over from search. You cab use download mode? First make sure you got right drivers as that can mess up Odin. Use one in my Sig if you want. Then flag stock recovery with root someone nice will part a link to it I'm on my phone can't do it. Well fix your phone
Sent from my SGH-I747 using xda premium
allow rldcess
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Bump
Sorry, I really need help for this. I can't install the MTP drivers even through using some of the tips on this site. That seems to be the problem with me accessing the phones storage from my computer. Does anyone have an ideas for what else I could do? Should I just take it to the store and hope they can fix it?
cabato said:
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Click to expand...
Click to collapse
go to your device manager on your computer, locate samsung drivers for your device, uninstall them
restart your computer
then plug in the phone and lets it reinstall by itself
Use my drivers in my signature
They are last good damaging drivers. Don't update them but install them and plug phone in with no internet. after install plug internet in. There good stable drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
Hello XDA.. my first time rooting and I think i bricked my new Galaxy Tab S 8.4
I followed the guide here: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
I booted my tab S into download mode, clicked volume up, then clicked AP on Odin 3.09 and chose the "CF_AutoRoot_Port_T700_BeansTown106.tar" file. The tab then went into ODIN MODE and says "Downloading... Do not turn off target !!"
I then clicked Start on Odin and it said something along the lines All threads complete.
But after 15 minutes my Tab is still in the exact same screen as described after clicking volume up. Now I have deplugged the USB cable and the Tab is frozen in this screen. I've tried a lot of combinations to try and restart my Tab but nothing works...
combinations I tried: volume up + power + home / volume up + power / power / volume down + power + home / volume down + power (all for around 15~30 seconds)
I'm quite sad, I don't know what I did wrong, the steps were quite unclear in the guide since it assumes everyone to be an expert in rooting, and if rooting is supposed to be this difficult, then I will stay away from rooting if I can ever fix my Tab.
Does anyone know how to save my Tab?
edit: here's a pic of my tab: http://imgur.com/fZtvUXV
Mjaaay said:
Hello XDA.. my first time rooting and I think i bricked my new Galaxy Tab S 8.4
I followed the guide here: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
I booted my tab S into download mode, clicked volume up, then clicked AP on Odin 3.09 and chose the "CF_AutoRoot_Port_T700_BeansTown106.tar" file. The tab then went into ODIN MODE and says "Downloading... Do not turn off target !!"
I then clicked Start on Odin and it said something along the lines All threads complete.
But after 15 minutes my Tab is still in the exact same screen as described after clicking volume up. Now I have deplugged the USB cable and the Tab is frozen in this screen. I've tried a lot of combinations to try and restart my Tab but nothing works...
combinations I tried: volume up + power + home / volume up + power / power / volume down + power + home / volume down + power (all for around 15~30 seconds)
I'm quite sad, I don't know what I did wrong, the steps were quite unclear in the guide since it assumes everyone to be an expert in rooting, and if rooting is supposed to be this difficult, then I will stay away from rooting if I can ever fix my Tab.
Does anyone know how to save my Tab?
edit: here's a pic of my tab: http://imgur.com/fZtvUXV
Click to expand...
Click to collapse
edit2: nevermind, i fixed it. i also rooted it. the guide is super unfriendly to newbies, just fyi to those who's thinking rooting, be careful if ur not experienced.
I'm glad you got your tablet fixed! ?
What do you think went wrong?
LadyAngler said:
I'm glad you got your tablet fixed! ?
What do you think went wrong?
Click to expand...
Click to collapse
There are perhaps 2-3 hidden steps in that guide that the author doesn't tell you about.
1: Don't have you device plugged until Odin is loaded with the file
2: Confirm that Odin has detected your Tab after plugging it in
3: ONLY click start on Odin after it has detected your Tab with that light-blue/yellow box
Those 3 steps are already "assumed" that users know, and in my case, I clicked start before Odin detected my Tab. My PC didn't detect my Tab because the driver that detects Galaxy Tab S wasn't installed (yet I could access my Galaxy Tab S with that same PC). Perhaps when rooting, the PC uses a driver different from the default USB driver that lets you explore files.
So my device was frozen for nearly an hour and when I tried pressed the power + volume down button TOGETHER (not power + volume down, but TOGETHER at the SAME time), it rebooted.
Nothing was wrong with my device, just lack of understanding of how rooting is supposed to go. The guides here are too advanced and I understand why a lot of my colleagues refuses to root... there's a lot of "you should already know how to do this" etc when i read over this thread for the 10.5 root guide: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t800-t2802916
That's why I asked for a video tutorial for us newbs. So we can see exactly how it should be done. ?
xRevilatioNx said:
That's why I asked for a video tutorial for us newbs. So we can see exactly how it should be done. ?
Click to expand...
Click to collapse
i searched google after i thought i had bricked my tab, and here is a guide that the author should had included:
http://forum.xda-developers.com/showthread.php?t=2661198
the steps for rooting the tab S is the same as the full guide in the link, but just click AP instead of PDA. That's how I managed to root it.
Mjaaay said:
i searched google after i thought i had bricked my tab, and here is a guide that the author should had included.
Click to expand...
Click to collapse
Should? How? Perhaps you missed thatBeantown106 says in both of root his threads that he/she doesn't own the device.
qngds said:
Should? How? Perhaps you missed thatBeantown106 says in both of root his threads that he/she doesn't own the device.
Click to expand...
Click to collapse
those steps appears to be universal for rooting.
and in Beantown's guide, the title of it says ROOT INSTRUCTIONS. Let me paste it for you.
Rooting Instructions
1.Boot into Download mode (see methods above)
2.Flash CF_AutoRoot_Port_T800_BeansTown106.tar.md5 with Odin v3.09 (put in AP slot, don't change any other settings, click start)
3.Let it do its trick! Confirm root!
4.Reboot into recovery mode and confirm stock recoverys presence
That's all! Enjoy Root!
Do you see the part where it says "That's all!"? That tells every reader of that thread, that his rooting instructions is "all there is to know".
Bean is awesome at what he does with root & roms. But giving instructions is absolutely not his forte... Lol.
My point was he/she could've hardly done a video on a device he didn't own. Generally videos include both the boot into recovery (which you need the device to demonstrate), and walking thru odin.
No doubt the underlying assumption to the flashing posts were, if you got to this device, you've rooted at least one device prior to this. Prior experience is taken for granted.
Glad you got your device going The next will be easier!
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.