My phone cannot turn on and charge.
Also it cannot connect with usb.
Before brick, its 4.04 CM9. One day its shut down but it can still go to recovery mode.
When I use CWM to wipe data and flash ROM. Its shut down and cannot turn on again.
I have the same problem like you
seinch said:
I have the same problem like you
Click to expand...
Click to collapse
Do u solve the problem?
I don' solve the problem... May be i will go to Samsung SAT
anyone can help me
This also happened to me, I was never able to fix it though. Couldn't restore through CWM and the gnex tool kit wouldn't flash to stock. ODIN flash failed on me too and now my phone sits at the yellow triangle screen. I ended up ordering a new Nexus and am going to try to sell the other one.
Sent from my Galaxy Nexus using xda premium
Have you tried manually flashing the stock images through fastboot? If you have the i9250 (GSM Maguro) Please follow this guide on restoring to stock using the fastboot method. It has helped me before. http://forum.xda-developers.com/showthread.php?t=1366806
racerklm said:
Have you tried manually flashing the stock images through fastboot? If you have the i9250 (GSM Maguro) Please follow this guide on restoring to stock using the fastboot method. It has helped me before. http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
fOR the step 4) Boot your phone into the Bootloader mode
my phone cannot turn on , so how can i boot my phone into Boorloader mods?
same problem here bro. sucks. wont turn on. BS
I once had a similar problem. Thought my phone was bricked and was trying all day to recover. Eventually the battery died and it wouldn't turn on or charge even when plugged in with a wall charger. I had to find a different (charged) battery to put into the phone, then was able to boot and recover.
mayhem32 said:
I once had a similar problem. Thought my phone was bricked and was trying all day to recover. Eventually the battery died and it wouldn't turn on or charge even when plugged in with a wall charger. I had to find a different (charged) battery to put into the phone, then was able to boot and recover.
Click to expand...
Click to collapse
i had tried it before, but still not working. I had used three different (charged) battery. But also cannot turn on.
I find Unbrickable for nexus S, Is there any software like that for Glaxy Nexus?
Rguys I have the answer to this. I had problems and fixed my phone with ease (ish =p)
Not required (if you can turn your phone on do these steps)
1. Your gonna need dropbox(decent amount of space I needed 2.5 GB)
Stuff you need (if your phone can't turn on, do this anyways)
2. Wug's Galaxy Nexus Toolkit
3. Experience. =p
Who wants and still need to fix their nexus device from an annoying bug???
Me , please
Well since a toolkit (and not understanding how to use it) was what originally fuxored you guys....
Why not try to recovering by using one again hahahahaha.....right ?
You do not need a toolkit of any sort.
And what exactly is dropbox supposed to do for you if your phone won't get online ?
Common sense should dictate not to use something that screwed you over (the first time it's a mistake, the second time it's not a mistake anymore).
Common sense should also tell you that a person that just joined the site last month and has 28 posts with a donate button might not have your best interests in mind.
But hey, it's the intarwebz.....toss logic to the wind.
If you are unable to go into recovery or fastboot mode, then I'm afraid you are hard bricked and there really isn't anything you can do apart from return it to Samsung (hoping they will actually fix it or replace it). At the moment, there is no Unbrickable mod for the Galaxy Nexus.
I can go in Bootloader, but can't load or install Recovery
Error: FAILED (data transfer failure (too many links))
The battery won't charge either in Bootloader so I need to wait for an external battery charger from eBay, in the mean time I am showing some love to a NEXUS S bought on Craiglist yesterday.
;-(
why don't use Jig??
This is the one reason why I don't wanna root. I'm afraid of my device becoming a full brick. I know that Wugs will unbrick and restore a bootloop or a GNex that is stuck on the Google logo, but has anyone found out if you can UnBrick a GNex that won't turn on?
Related
So today I was minding my own business, riding the subway and listening to some music when my Galaxy Nexus decides to reboot itself. After this, it gets into a reboot loop (never getting past the Google logo).
I tried restarting the phone into fastboot mode and using the recovery option, but I end up getting the icon of the android on its back, chest plate open and a red exclamation triangle thing coming out of it. I assume this is bad
A little back story... this is the GSM/Euro Galaxy Nexus. I've been using it for close to 6 months most likely and have never rooted/unlocked it. In actuality, I don't think I've ever done anything with it out of the ordinary (like I have in the past with other android devices). In fact, I don't know if I ever even plugged it into my PC via USB before (thus no drivers, may have never set it to USB debugging enabled).
Is there anything I can do here? I tried looking at a few options (Such as the WugFresh Galaxy Nexus Root Toolkit, which has a Stock resetting option), but since I never enabled USB debugging and installed drivers before the phone decided to go and brick itself, I don't know if I'm actually stuck...
What do you think? Is there an option I have not yet considered? Or am I going to try and convince Samsung to honor my warranty or something?
Moved to Q&A, please pay attention next time where you are opening a new discussion
When you see the android on its back you have to hold vol. up + power to enter the options.
There you can wipe data and reboot to see if it will boot up again.
If that doesn't work you can try flashing the stock images. Those will require you setting up fastboot on your computer. There are many guides on how to do all of that.
Good luck.
If you can get into Fastboot mode just fine, then hook it up to your computer and flash the stock images. It'll revert you back to stock fresh and you can go from there.
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
i had the same happening to me under stock. after quite some time it went into a bootloop out of the blue.
this:
bk201doesntexist said:
Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
solved it. my data was gone, but at least the phone worked.
then i decided to root and use a custom rom and it never ever happened again.
bk201doesntexist said:
We also need to teach people how to debug at basic level at least. If we just teach them how to solve it without caring about what went wrong... they've got the phone might as well learn a few things more.
And yea, i know most couldn't care less. Also, this is no brick - this word very much starts to annoy me when it is incorrectly used and that seems to be getting typical around here. Most likely wiping data/factory reset from stock recovery will allow op to boot up again.
Click to expand...
Click to collapse
Sure we do but as long as :
1. people start threads that suggest they bricked their phone and
2. all they had to do is Google some around to discover that what they see is a stock recovery and
3. discover what they can do to solve their problems (like most of us do to solve our problems)
I think they couldn't care less about debugging... How sad as it may be.
If you discover problems with a device that is sold as much as the GN it is highly unlikely that you were the first to have that problem. If you are: just post away.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
machdown said:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
Click to expand...
Click to collapse
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
BCSC said:
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
Click to expand...
Click to collapse
I entered download mode and dont see flash counter anywhere. I got the warning screen were you have the option to restart or download.
Ya I entered recovery and did a factory reset but nothing. Really cant do anything with charging port broken.
I sent it in anyways for repairs. Hopefully they just replace it
I'm having the same problem with my Gs3 with CM10 4.2.2 running. Thought this would help.
Sent from my SPH-L710 using xda app-developers app
So I wanted to install a new custom ROM and I all ready had one. It wasn't the first time. So, like usual I download the files needed and put them on my phone, boot into recovery and flash them ( but I didn't factory reset or anything because with the ROM I had I didn't need to for it to work I could just fix the not responding errors) Then i go to reboot and I wait. Nothing, nothing at all. Now I try to remove the battery and try again and now none of my buttons do ANYTHING the only sign of life there is, is when I remove the battery and plug my phone to a usb cable and attempt to charge it, all that happens is a red LED comes up. It's probably due to one of the things i installed on my phone that flashes a red LED when battery is low. Please help me with this. My last resort is to give my phone to rogers for them to fix it because I still have a warranty.
Specs: S3 i1747M Rogers
I had aokp jellybean 4.3 as my ROM
I do have a nandroid but its on my phone's sd card
Thank you for your time and I hope we get this to work.
Can you get into recovery mode or download mode?
FoxTrotz said:
Can you get into recovery mode or download mode?
Click to expand...
Click to collapse
No there's litteraly nothing I can do. pressing all the buttons does absolutely nothing. Just stays black and no signs of life
bump. I need help fast with this.
Not sure exactly what you did but I hate to say its sounds hard bricked. Mine was exactly the same, with only the red light coming on for about a minute when cord was plugged in with no battery. I screwed mine up with a file I grabbed without reading properly what it was for and in my haste I installed it. After I rebooted it never came back until I got it back from warranty with a replaced control board. Im guessing they didnt even check the internal memory or they would haven known what a dumbass i was since i voided the warranty doing stuff i had done before that mistake. Glad I had made a nandroid before i pooched it so i didnt lose anything after i got it back.
Yeah after some research I found out I hardbricked it but this isn't the first time and I had a warranty for both( different phones btw )times so I guess I'll just send it out. :c
could just be out of juice, leave it on the charger for around an hour then try and go into download mode.
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.