Hello, this is a sad history but i got my first s4 mini the last year, it worked arround 2 years but one day i was just using it an on my hands my phone freezes a few seconds and just power off. Then, never power on again!
No recovery, no download, no samsung logo, no vibration, nothing. it just is showed as qshusb_dload on windows 7.
As i read it died completely. but i read that some people are getting sucess with a file named debrick.img, that is obtained doing a backup of the first 128mb of the rom.
well ive tried maybe 3 different debrick.img that i found on web but i get the same, nothing.
the problem is that my phone was working with pacman rom before die, and the debrick.img`s that i ve found on the web are from stock roms on some different versions.
someone can do a debrick.img from a pacman rom and upload it to me? i will aprecciate too much
you can get the debrick img flashing this
forum.xda-developers.com/attachment.php?attachmentid=2500001&d=1389091779 <-direct link.
its completely safe i do a backup with this tool on my s4 mini before but as an idiot i just deleted from my pc and now i need that...
this is the link to the post of the tool if you want to read more, is from another model but im telling you its safe, works on s4 mini with no problems, i used before!
http://forum.xda-developers.com/showthread.php?t=2600976
:crying:
migueldvp said:
No recovery, no download, no samsung logo, no vibration, nothing. it just is showed as qshusb_dload on windows 7.
Click to expand...
Click to collapse
My phone was dead like yours, too, black and no life sign when pressing buttons. However i had success to "revive" it by removing battery and cables and putting them back (I don't remember if battery first and cable second or vice versa) while holding power button pressed (and maybe VOL.UP / VOL.DOWN / HOME or both/three) all the time. It needed some tries and I do not know the exact combination which worked, but it worked in multiple situations in the past too, when my phone was dead black and did not want to start. If your battery charger screen shows up finally you got it. Let it recharge at least a bit (better: full recharge) before you try to start the android system finally.
sumeruter said:
My phone was dead like yours, too, black and no life sign when pressing buttons. However i had success to "revive" it by removing battery and cables and putting them back (I don't remember if battery first and cable second or vice versa) while holding power button pressed (and maybe VOL.UP / VOL.DOWN / HOME or both/three) all the time. It needed some tries and I do not know the exact combination which worked, but it worked in multiple situations in the past too, when my phone was dead black and did not want to start. If your battery charger screen shows up finally you got it. Let it recharge at least a bit (better: full recharge) before you try to start the android system finally.
Click to expand...
Click to collapse
Thanks but this is not working for me, i tried everything! pressing all buttons on differents ways, with battery pulls usb cable, etc, etc nothing works.
That's sad.
As far as I've understood the cpu tries to boot from second partition if booting from first partitions fails. The debrick.img contains the first X partitions from booting process and even if those are the very first booting partitions of another rom for the same phone and are conflicting to your installed android system (and thus won't boot into full system), your phone should give at least a life sign.
Have you tried different sdcard sizes?
I think there is still hope. I don't know how it works, but you might try a JIG. And since your phone shows up as qshusb_dload you might try to connect to your phone while it is offline (my phone has even adb shell while in charge screen - which doesn't show up for your phone). I remember there was a special qshusb_dload driver for Samsung phones, different to the "usual" Samsung USB drivers (maybe look here)...
sumeruter said:
That's sad.
As far as I've understood the cpu tries to boot from second partition if booting from first partitions fails. The debrick.img contains the first X partitions from booting process and even if those are the very first booting partitions of another rom for the same phone and are conflicting to your installed android system (and thus won't boot into full system), your phone should give at least a life sign.
Have you tried different sdcard sizes?
I think there is still hope. I don't know how it works, but you might try a JIG. And since your phone shows up as qshusb_dload you might try to connect to your phone while it is offline (my phone has even adb shell while in charge screen - which doesn't show up for your phone). I remember there was a special qshusb_dload driver for Samsung phones, different to the "usual" Samsung USB drivers (maybe look here)...
Click to expand...
Click to collapse
Hmm i understand, i was thinking that the debrick.img should be from the same rom exactly... and i have two phones with the same problem, both fails by the same way, i was using it and just frezees and never woke up again. I buyed the second when the first died, but after a months the second died too.. Both have installed unofficial roms and dindt show any signal of life dont matter what i do, the JIG doenst works too i tied too.
Definitivelly S4 mini is not great choise for a phone that will be used with hard work.
migueldvp said:
Definitivelly S4 mini is not great choise for a phone that will be used with hard work.
Click to expand...
Click to collapse
As many cases of died S4 minis I've heard of the last two weeks here at XDA or from friends I got the impression Samsung built those phones with an expiration date.
sumeruter said:
As many cases of died S4 minis I've heard of the last two weeks here at XDA or from friends I got the impression Samsung built those phones with an expiration date.
Click to expand...
Click to collapse
i'm agree with this. And looks like the expiration time for the s4mini is one year and a half or two years till the EMMC die. The sandisk EMMC included on the s4 mini is not of a great quality.
well ****. exact same problem here, does this emmc has anything to do with hardware? and have you folks fixed it yet? how do you even get a phone with good emmc things?? sorry if iam late but it really sucks how that 1 year 9 months later it just dies. any help? thanks!
migueldvp said:
i'm agree with this. And looks like the expiration time for the s4mini is one year and a half or two years till the EMMC die. The sandisk EMMC included on the s4 mini is not of a great quality.
Click to expand...
Click to collapse
Interesting theory. My S4 mini died overnight for no particular reason and I am in the same situation now. Cannot get to download mode, JIG doesnt work either. Tried searching for debrick images, but all the older links are invalid. Would appreciate if anyone can provide one.
Thanks.
abhishek55 said:
Interesting theory. My S4 mini died overnight for no particular reason and I am in the same situation now. Cannot get to download mode, JIG doesnt work either. Tried searching for debrick images, but all the older links are invalid. Would appreciate if anyone can provide one.
Thanks.
Click to expand...
Click to collapse
Nah, Samsung wouldn't do that, however there definitely seems to be a problem with the S4 Mini if you look at the number of bricked S4 Mini's here on XDA and compare to say the S4 which sold more (I believe) and yet it has nothing like the number of failures. One poster on another thread said most of these were from a bad batch manufactured in Vietnam, but I have not been able to find definite proof of this.
As for a debrick image it should not matter what ROM the debrick image is made from as it only consists of a small block of data that is not changed by custom ROM's (according to what I read on another Samsung phone thread last year, where a debrick image was made from a phone running a Cyanogenmod rom that worked successfully on another phone. But again I have not found another ref to confirm this)
I would make you a debrick file but I have a I9195 LTE
IronRoo said:
Nah, Samsung wouldn't do that, however there definitely seems to be a problem with the S4 Mini if you look at the number of bricked S4 Mini's here on XDA and compare to say the S4 which sold more (I believe) and yet it has nothing like the number of failures. One poster on another thread said most of these were from a bad batch manufactured in Vietnam, but I have not been able to find definite proof of this.
As for a debrick image it should not matter what ROM the debrick image is made from as it only consists of a small block of data that is not changed by custom ROM's (according to what I read on another Samsung phone thread last year, where a debrick image was made from a phone running a Cyanogenmod rom that worked successfully on another phone. But again I have not found another ref to confirm this)
I would make you a debrick file but I have a I9195 LTE
Click to expand...
Click to collapse
Hi
Can you please make me the debrick file?
I have the I9195 and I have the exact problem. The thing is that I can't even go to Download Mode... What can I do?
PedroBarbosa said:
Hi
Can you please make me the debrick file?
I have the I9195 and I have the exact problem. The thing is that I can't even go to Download Mode... What can I do?
Click to expand...
Click to collapse
Did you try the I9195 debrick files from the @ValenteL thread here
https://forum.xda-developers.com/showthread.php?t=2625628&page=7
see my mega link or the other one
(note: they are NOT for I9192 phones)
Related
Somehow i Think my /boot partition has become corrupted. Yesterday i was switching batteries to put in an externally charged secondary battery and when i rebooted i couldnt even get to the samsung splash screen.SO i switched back thinking maybe the battery had gone bad but it gave the same error after the phone was just working phone. No matter how long it charges its like i have nothing to boot too so it stays on the battery screen rather im charging the phone or not. I can enter recovery mode and download mode. Ive factory reset from recovery, Ive reflashed stock from odin and still no luck. Ive been searching for answers all morning and night with no luck. People have reported the same exact problem with no answer as of yet.
i found a thread for the NOTE 1 discussing a similiar problem where the solution was flashing a custom PIT and sacrificing 2gb of internal storage to get the phones back , im willing to do that i just need some help as im leaving for basic training tuesday and i dont want to leave without a phone.
has anyone had this grey battery screen problems and found a solution?
raptor9819 said:
Somehow i Think my /boot partition has become corrupted. Yesterday i was switching batteries to put in an externally charged secondary battery and when i rebooted i couldnt even get to the samsung splash screen.SO i switched back thinking maybe the battery had gone bad but it gave the same error after the phone was just working phone. No matter how long it charges its like i have nothing to boot too so it stays on the battery screen rather im charging the phone or not. I can enter recovery mode and download mode. Ive factory reset from recovery, Ive reflashed stock from odin and still no luck. Ive been searching for answers all morning and night with no luck. People have reported the same exact problem with no answer as of yet.
i found a thread for the NOTE 1 discussing a similiar problem where the solution was flashing a custom PIT and sacrificing 2gb of internal storage to get the phones back , im willing to do that i just need some help as im leaving for basic training tuesday and i dont want to leave without a phone.
has anyone had this grey battery screen problems and found a solution?
Click to expand...
Click to collapse
I think the thread you found was in relation to the emmc brickbug. I think your soulution is similar to that one though. When you odin'd it did you use a pit? If not then you should try that first.
billard412 said:
I think the thread you found was in relation to the emmc brickbug. I think your soulution is similar to that one though. When you odin'd it did you use a pit? If not then you should try that first.
Click to expand...
Click to collapse
where can i find a custom PIT for the Note 2?
raptor9819 said:
where can i find a custom PIT for the Note 2?
Click to expand...
Click to collapse
Im looking around and at&t's is the only one I can't find
billard412 said:
Im looking around and at&t's is the only one I can't find
Click to expand...
Click to collapse
same here i even treid the N7100 and i wouldnt even re-partitiion it .. smh
Note II wont boot - grey battery
Raptor9819
Did you ever get a resolution to this problem?
Brian
raptor9819 said:
Somehow i Think my /boot partition has become corrupted. Yesterday i was switching batteries to put in an externally charged secondary battery and when i rebooted i couldnt even get to the samsung splash screen.SO i switched back thinking maybe the battery had gone bad but it gave the same error after the phone was just working phone. No matter how long it charges its like i have nothing to boot too so it stays on the battery screen rather im charging the phone or not. I can enter recovery mode and download mode. Ive factory reset from recovery, Ive reflashed stock from odin and still no luck. Ive been searching for answers all morning and night with no luck. People have reported the same exact problem with no answer as of yet.
i found a thread for the NOTE 1 discussing a similiar problem where the solution was flashing a custom PIT and sacrificing 2gb of internal storage to get the phones back , im willing to do that i just need some help as im leaving for basic training tuesday and i dont want to leave without a phone.
has anyone had this grey battery screen problems and found a solution?
Click to expand...
Click to collapse
billard412 said:
Im looking around and at&t's is the only one I can't find
Click to expand...
Click to collapse
You can find PIT file for i317 at&t here - http://forum.xda-developers.com/showthread.php?t=2609871
Right now, Zen has removed files and still doing some more testing but soon he will re-upload them.
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
I installed Cyanogenmod 12.1 on my sprint s3 with CWM about a month ago; everything was working fine until last night when my phone died on me and after leaving it on the charger over night I woke to find my phone Hard Bricked. Now I know it's not the battery since I have two (both of which I've fully charged via battery charger) and I can't get into download mode or recovery mode; plus given the fact that there is no battery charger light on when phone is plugged into charger; except when the battery is not in the phone then it's only lit up for around 30 seconds: I am absolutely sure that my phone is Hard Bricked (Still not sure as to why my phone Hard Bricked in the first place though), and given the fact that I've lost my old img back up I made when I installed a new linux OS on my PC a few days ago foolishly not backing up all my phone files. Given all that I can say without a doubt that my phone is screwed without any help from someone else, but sadly out of everyone I know personally not one of them seams to have a Sph-L710 S3.
Now I've searched all day now to find a dumped sph-l710 5.1.1 cyanogenmod 12.1 image to no avail (not sure if the recovery software is a factory but I use CLOCKWORKMOD). Now I know that a SD card debrick loader has a chance to not work but I really would like to at least find out whether or not it will help me in my situation, or if I should just finally decide to upgrade to a new device (the latter option is not exactly appealing to me; oh how I love my S3 with its perfect size), If there is anyone that could possible help me out I would greatly appreciate it. So, that is my issue; I hope that you can help if not thanks for the effort of reading this post anyways.
Have you looked at any of the threads on this forum talking of unbricking a hard bricked s3?
Powered_By_Linux said:
Have you looked at any of the threads on this forum talking of unbricking a hard bricked s3?
Click to expand...
Click to collapse
good call. thats where i got debrick image that i keep on internal storage, just in case!
You don't need an image from the rom you were running, you need an image for the firmware you were on.
What was the last touchwiz version that you were running/last update that you took? That's the version of the debrick image that you need to find.
Yes thats what we were trying to tell him. The thread we are referring to is this one...
http://forum.xda-developers.com/showthread.php?t=2369125
which has the firmware images in link there. i got the one for my ND8 there :good:
Nice stats!
Hello,
i have a huge problem with my s4 mini. The device wasn´t rooted, neither it has a custom recovery. It´s simple stock. But a few days ago, it turns off by itself and didn´t boot anymore. It stuck at the first Samsung logo, then it vibrate and reboots. I also don´t come in recovery anymore. Same here, it vibrate after 5 seconds an then reboots.
I read across the internet and found, that maybe the power button is damaged, but knocking on it etc. doesn´t help. I also successful flashed a new stock image with odin, but it didn´t help (so downloadmode is working fine). Any ideas what i can do? Maybe it´s the battery - the device is more than 2 years old, but battery isn´t blown up.
Edit: Charging isn´t possbile, same problem as recovery - battery icon appears, then reboot.
Thanks in advance
Is it the same as these guys?
http://forum.xda-developers.com/galaxy-s4-mini/help/galaxy-s4-mini-gt-l9192-hard-bricked-t3341351
IronRoo said:
Is it the same as these guys?
http://forum.xda-developers.com/galaxy-s4-mini/help/galaxy-s4-mini-gt-l9192-hard-bricked-t3341351
Click to expand...
Click to collapse
Not really. I can put the phone in download mode with no problem, my PC recognize the phone as a "Sasmugn Galaxy S4 Mini ......". As i mentioned, flashing via odin also workes, but doesn´t solve the problem.
Thanks anyway.
kaspakind said:
Not really. I can put the phone in download mode with no problem, my PC recognize the phone as a "Sasmugn Galaxy S4 Mini ......". As i mentioned, flashing via odin also workes, but doesn´t solve the problem.
Thanks anyway.
Click to expand...
Click to collapse
Yes, maybe it is battery or hardware (assuming the software you flashed is good, md5 checked OK) Hope you find a solution
IronRoo said:
Yes, maybe it is battery or hardware (assuming the software you flashed is good, md5 checked OK) Hope you find a solution
Click to expand...
Click to collapse
I will get a old S4 mini from a friend, it´s also dead, but maybe i can use the motherboard or the batterie, if not i will buy a new batterie and report the results here.
Reading across the internet, dead S4´s are a common problem.
For anybdoy else with similar problems: I bought a new battery, so the phone starts booting and i can enter recovery, but now i get bootloop and in recovery there are some error messages like e: can´t mount/data.../cache etc. So i think the internal storage is damaged.
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.