Related
Hi,
I was flashing a new CM7 theme on my 2 weeks old DZ (with CM7 RC 2 running fine) but the phone got stuck at the CM bootscreen. I tried rebooting multiple times by repeatedly pushing the power button and holding it. After a few failed attempts I pulled out the battery, and after putting the battery back in and trying to power it on the phone did nothing. No matter which buttons I pushed or held in.
I tried plugging it in to the power adapter, but the Power LED's don't even go on (neither the orange or the green one). The battery was at approx. 60% when I rebooted into recovery to install the theme zip, so there should be enough power left in the battery.
When I plug the DZ onto my PC (Windows 7 OS, with eclipse and Android SDK installed and working), the PC looks for a QHSUSB_DLOAD driver. I tried looking for the device through ADB but it doesn't see it.
Please help me guys, I've had the device for only two weeks now.
PS: I'm a noob
Oh dear, that doesn't sound promising. Good luck!! We feel for you.
Anyone knows what steps to undertake to maybe revive the phone. I don't think it's totally dead since it's somehow still being detected by my PC. I just can't find that so called QHSUSB_DLOAD driver.
If I can just somehow get it to connect to ADB then I might be able to get into Hboot or recovery.
Have you checked http://developer.android.com/sdk/win-usb.html ?
Perhaps, donno for sure, it could help you
HLeenders said:
Have you checked ***** ?
Perhaps, donno for sure, it could help you
Click to expand...
Click to collapse
I hadn't, but already had these drivers on my PC. And before it got bricked my DZ connected fine with the PC (I flashed it using ADB and had setup Hboot and recovery). My PC just can't seem to find any drivers for this so called QHSUSB_DLOAD. It doesn't matter wich folders I choose to look for drivers. Nothing is available through internet either.
im having the same problem ... i tried several times but no luck... no LED... but u shud try pulling off the battery then put it in then press volumeUP+power button ..it will vibrate and red LED will start blinking .. i dont knw wat is it .. i connected it to PC ....windows asked for qualcom MSM driver .... i dont knw wat to do ..nd how to get bootload loader bak :S
if it does this, send it back to HTC.
the eMMC chip has failed (an unfortunately reasonably common situation, happened to me twice so far)
They'll fix it regardless of what roms you had on it etc. (unless you've done some hardware mods) i sent it in with cyanogen mod and s-off, they fixed it anyway
hope this helps!
Lol, I thought my topic died.
Since you guys revived it, might as well tell you what happened. I contacted T-Mobile and sent the Desire Z in for repair and it got repaired for free since I'd only had for two weeks back then .
After I got it back I rooted it and restored a NAND backup and everything 's been working fine since then.
they repaired it or they replaced it ?
desirezbilal said:
they repaired it or they replaced it ?
Click to expand...
Click to collapse
They repaired it.
ok thats great
i have 1 stupid question, can you tell me did they open your phone or not
noboby solved this problem?
So i just created this thread to alert you all of a possible TOUCH brick situation !
*#*#2663#*#* (don't dial) is a Samsung secret code that brings a touch screen firmware info window . Now a days most custom Roms come pre installed with an app called Samsung secret codes and unfortunately i was on one such Rom and i tried this code - on the window that appeared there was an update button and not knowing what it does i clicked it and a pop up showing updating alongwith the usual busy circle came up ! I waited for the process to finish but even after waiting 10-15 minutes the circle was still there and a when i pressed the back key i was shocked to realize that doesn't respond nor was the menu key responding ! i pressed the home button and voila ! - i came back to the home screen btw again to my awe i touched the screen only to realize that my touch isn't working - the phone responds to all hardware buttons but touch ain't working
i rebooted and still no luck ! i thought no big deal and flashed stock Rom via Odin - but this time i was really shocked to death to find that even though stock Rom got flashed without errors and my phone booted fine my touch was still screwed up !
after hours of Googling and tensions a friend of mine finally found a method and solved the issue using this thread :
http://forum.xda-developers.com/showpost.php?p=22709246&postcount=1
morale : Enough of long boring story - all i wanted to tell is that NEVER EVER dial *#*#2663#*#* and do update - it won't give you any benefit and chances of screwing up are very high ! and if at all you accidentally get into this then wait for the updating process to complete no matter how long it takes !
thanx bro,its good to know!!!!!!:good:
CALIBAN666 said:
thanx bro,its good to know!!!!!!:good:
Click to expand...
Click to collapse
Welcome bro ! I thought i would share this since Odin flashing can't revive the phone it seems to be a serious issue !
I Tried it one time,and when i press the back button its back to homescreen and nothing happened on brazilian firmware,but its really dangerous
EliTSamsunG said:
I Tried it one time,and when i press the back button its back to homescreen and nothing happened on brazilian firmware,but its really dangerous
Click to expand...
Click to collapse
The update might have been successful then - in my case it failed or i rebooted before it completed !
One time, my brain plays N00B and my finger pressed on update.
And my touchscreen is not bricked (but dont try this option)
thanks for this..i wont take a risk to update my Touch FW haha
I tried that earlier on creed 3.5 screwed up the touch. I had to reflash the rom
Sent from a Super Saiyan's Phone
nikufellow said:
So i just created this thread to alert you all of a possible TOUCH brick situation !
*#*#2663#*#* (don't dial) is a Samsung secret code that brings a touch screen firmware info window . Now a days most custom Roms come pre installed with an app called Samsung secret codes and unfortunately i was on one such Rom and i tried this code - on the window that appeared there was an update button and not knowing what it does i clicked it and a pop up showing updating alongwith the usual busy circle came up ! I waited for the process to finish but even after waiting 10-15 minutes the circle was still there and a when i pressed the back key i was shocked to realize that doesn't respond nor was the menu key responding ! i pressed the home button and voila ! - i came back to the home screen btw again to my awe i touched the screen only to realize that my touch isn't working - the phone responds to all hardware buttons but touch ain't working
i rebooted and still no luck ! i thought no big deal and flashed stock Rom via Odin - but this time i was really shocked to death to find that even though stock Rom got flashed without errors and my phone booted fine my touch was still screwed up !
after hours of Googling and tensions a friend of mine finally found a method and solved the issue using this thread :
http://forum.xda-developers.com/showpost.php?p=22709246&postcount=1
morale : Enough of long boring story - all i wanted to tell is that NEVER EVER dial *#*#2663#*#* and do update - it won't give you any benefit and chances of screwing up are very high ! and if at all you accidentally get into this then wait for the updating process to complete no matter how long it takes !
Click to expand...
Click to collapse
Try to take out the battery and put it back in. I ignored ur warning and went ahead. took out the battery put it back in and it works.
Sent from my GT-S5360 using xda premium
4D1L said:
Try to take out the battery and put it back in. I ignored ur warning and went ahead. took out the battery put it back in and it works.
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Lol no i fixed mine i just warned you against possible problem ! And nothing will happen if the update completes but why take risk when there is no benefit !
nikufellow said:
Lol no i fixed mine i just warned you against possible problem ! And nothing will happen if the update completes but why take risk when there is no benefit !
Click to expand...
Click to collapse
thanks for sharing bro.i will now never enter into that kind of thing
tried that code and nothing happend,
im on ussr v7,
yes,you are reading my post...
dont be amazed...
switchblade00 said:
tried that code and nothing happend,
im on ussr v7,
yes,you are reading my post...
dont be amazed...
Click to expand...
Click to collapse
Okay !
Its updating something it means it must be some improvements
Sent from a Super Saiyan's Phone
I think it must be because ur phone must have entered deep sleep mode..
And when u tried to wake it up..
It needed some time ...
But u just started to mess with screen so the update was in the middle way...
Nd this has what screwed ur screen...
rooting is new for me...and i am noob to root...
Filip98 said:
Its updating something it means it must be some improvements
Sent from a Super Saiyan's Phone
Click to expand...
Click to collapse
Not in this case i have done my bit of research and every single person who have done this says its not beneficial ! See for yourself if you need proof but be careful !
menewtoroot said:
I think it must be because ur phone must have entered deep sleep mode..
And when u tried to wake it up..
It needed some time ...
But u just started to mess with screen so the update was in the middle way...
Nd this has what screwed ur screen...
rooting is new for me...and i am noob to root...
Click to expand...
Click to collapse
Probably - i was also thinking the same if only i had given it more time ! Anyhow thank god all is fine now !
nikufellow said:
Probably - i was also thinking the same if only i had given it more time ! Anyhow thank god all is fine now !
Click to expand...
Click to collapse
good....
btw still thanx for creating thread like this...
its helpful...
rooting is new for me...and i am noob to root...
hey thanks for the warning !
i will sty away from samsung secret codes now
Frikid said:
hey thanks for the warning !
i will sty away from samsung secret codes now
Click to expand...
Click to collapse
Just be careful don't stay away - it has its uses you know !
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:
Well i've been doing a lot of flashing since i bought my nokia x....
I've flashed lewa...Vanilla aosp and cm 10 by dhacker29...
But i was facing the incall mic issue in vanilla aosp....i switched to cm 10....
then i began to face reboot issues.... :/
I Used lewa for the very first time...it is the most stable rom...
Now the silly part...
The superSu couldn't grant permissions....it needed to update binaries and always failed !
My recovery also stopped working (TWRP) And when i pressed the volume up and power button it just gets stuck on nokia logo...
then i used the adb method....same result ! waiting for device and stuck on nokia logo !
MY Laptop prompted to format the disk...which i ACCIDENTALLY did !
Now my phone wont even vibrate after pressing power button,,,
i tried charging it...Removing battery and all....but nothing !
Adb...nokia x flasher does not recognize my phone....
Please Guys i need help regarding this or i won't be getting any phone for 2 years (until i'm in college)
I Believe in XDA And i know u guys can help me!
Thanks in advance !
Anyone? Guys i really need your help...
And one more thing,,,
When i connect my dead nokia x with pc....my pc detects it as Qualcom device :/
Atleast it shows some sort of life !
i think the whole phone is empty bcoz of the formattion....
My PC CAn detect it so something can be done for it,,,
basit21 said:
Atleast it shows some sort of life !
i think the whole phone is empty bcoz of the formattion....
My PC CAn detect it so something can be done for it,,,
Click to expand...
Click to collapse
First charge your phone for about an hour.
Refer to my post here. Let's see if I can fix you up.
http://forum.xda-developers.com/showthread.php?t=2757878&page=2
Dom3616 said:
First charge your phone for about an hour.
Refer to my post here. Let's see if I can fix you up.
http://forum.xda-developers.com/showthread.php?t=2757878&page=2
Click to expand...
Click to collapse
he already formatted the bootloader, so the only solution is go to Nokia Care
thanks for the help I had successfully rooted my device and it was working fine but I've formatted sys/boot and then my device got bricked. I ve installed quallcom driver but its not detecting fastboot [vol- and without battery]
Please help me out? What should I do now to recover it??
n33l_ray said:
thanks for the help I had successfully rooted my device and it was working fine but I've formatted sys/boot and then my device got bricked. I ve installed quallcom driver but its not detecting fastboot [vol- and without battery]
Please help me out? What should I do now to recover it??
Click to expand...
Click to collapse
if you press volume down and power button, "nokia" word still come up?
Noh nothing just a vibration
n33l_ray said:
Noh nothing just a vibration
Click to expand...
Click to collapse
same as mine, there is no other method or guide to revive our bricked Nokia X yet except Nokia Service Center.
n33l_ray said:
Noh nothing just a vibration
Click to expand...
Click to collapse
I dont think bootloader can be restored using only usb connection.
Probably some other devices are available to service center like JTAG..doplhinclip...which can be used to re-write the boot partition
Lol, Im not alone in this.
Did same thing by accident. googled for how-to restore the phone. But it did not seem possible to be done. So I sent it to Nokia Care.
Those guys at the Nokia office laughed for a long time, when I told them a story " how I got a new shiny green brick ".
Told me the repairs would take 2 weeks and cost arond $30
_________ UPDATE____________
Called to Nokia Care. They fixed the phone by changing the celluar module ( maybe with the whole motherboard ).
That means that bootloader can not be fixed, at least for now.
BE CAREFUL
Well Nokia has just replaced my device with a new one after 3 weeks
I got my device back frm care center..
They replaced the motherboard...as the phone was dead they didn't knew i rooted my phone...n i claimed my warranty
Sent from my Nokia_X using XDA Premium 4 mobile app
my Nokia XL
plz i need your help bro. i mistakinly installed "insecure kernel" on my rooted Nokia XL device using NokiaX mgr. sinced then my fone homescreen button not workin and we press power button to wake up. it displays ink whc covers d screen frm seein the menu. how can i remove this insecure kernel so my device can work properly.,
superbod said:
plz i need your help bro. i mistakinly installed "insecure kernel" on my rooted Nokia XL device using NokiaX mgr. sinced then my fone homescreen button not workin and we press power button to wake up. it displays ink whc covers d screen frm seein the menu. how can i remove this insecure kernel so my device can work properly.,
Click to expand...
Click to collapse
Just flash back the original kernel...
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.