Hello,
Let me give some information on fore hand.
A few months back my phone suddenly decided that it was funny to give me an error about "Settings has stopped working". This wouldnt go away. So i just downloaded this rom: 0PKVIMG.zip.
This way i was able to revive my phone whenever it decided to show that message again. So i kept it on my external SD Card. In case it would happen again.
Today, it decided to show the encrypted screen for no reason(Phone was in my pocket.). After i entered my Decryption key (It did accept my Screen lock pin) It showed me the error that the data was corrupted.
I went into recovery(Had 80% of battery left) reflashed that rom. After it said it was finished it was stuck on the bootloader for almost 2 hours.(Sometimes it took it an hour to show the begin screen.)
So i decided to reset it with the Power and Volume up keys. My screen went black and it didn't turn on anymore. So i came home and connected my charger just in case.
Then the battery charging light indicator started to blink. Then i knew there was something wrong. So i took out my ExSDCard just incase. Connected my phone to my PC.
My PC recognized it as: RELINK HS-USB QDLOADER 9008 (COM5)
After a long time spending on google i found out that this is the "Download Mode" for the Qualcomm chipset/processor.
I downloaded QFIL with some package i found on here in an other Thread for an other Device. It was for an other phone so i thought well, it's broken anyway lets try it. Ofcourse it said SaharaFail because the files didn't match with my phone.
I tried going into fastboot mode. Won't go in there. Bootloader/Recovery won't go in there either.
I was hoping before i send it in that i could fix it myself with a bit of help from you guys.
Thanks in advance, i hope i provided enough information and i am sorry for my English.
I am from The Netherlands and my English isn't that great.
Kind Regards,
FastE
Fast-E said:
Hello,
Let me give some information on fore hand.
A few months back my phone suddenly decided that it was funny to give me an error about "Settings has stopped working". This wouldnt go away. So i just downloaded this rom: 0PKVIMG.zip.
This way i was able to revive my phone whenever it decided to show that message again. So i kept it on my external SD Card. In case it would happen again.
Today, it decided to show the encrypted screen for no reason(Phone was in my pocket.). After i entered my Decryption key (It did accept my Screen lock pin) It showed me the error that the data was corrupted.
I went into recovery(Had 80% of battery left) reflashed that rom. After it said it was finished it was stuck on the bootloader for almost 2 hours.(Sometimes it took it an hour to show the begin screen.)
So i decided to reset it with the Power and Volume up keys. My screen went black and it didn't turn on anymore. So i came home and connected my charger just in case.
Then the battery charging light indicator started to blink. Then i knew there was something wrong. So i took out my ExSDCard just incase. Connected my phone to my PC.
My PC recognized it as: RELINK HS-USB QDLOADER 9008 (COM5)
After a long time spending on google i found out that this is the "Download Mode" for the Qualcomm chipset/processor.
I downloaded QFIL with some package i found on here in an other Thread for an other Device. It was for an other phone so i thought well, it's broken anyway lets try it. Ofcourse it said SaharaFail because the files didn't match with my phone.
I tried going into fastboot mode. Won't go in there. Bootloader/Recovery won't go in there either.
I was hoping before i send it in that i could fix it myself with a bit of help from you guys.
Thanks in advance, i hope i provided enough information and i am sorry for my English.
I am from The Netherlands and my English isn't that great.
Kind Regards,
FastE
Click to expand...
Click to collapse
Well Quallcom HSUSB mode is the mode where you can send direc commands to the cpu in hex speak... i remember that from another phone... so you will only be able to revive it if you find the correct msm8939.hex that can start the download of a partition table and partitions.... i will be honest to you... this whole process is only for very high experienced onces and you will need help from other m8s owners ( you need dumps of most partitions )
so if you find that mprg8939.hex anywhere we can try to revive it.... BUT in 90% of cases your IMEI can not be restored so you cant do calls.... in 40% your emmc is so hard damaged that you cant use it....
there is a second posibility wich is not possible on every phone.... on i9300 (sgs3) you can revive such a phone by creating a microsd card with a partitiontable like the phone and all coresponding partitions so you can boot straight from sdcard... but this case is really rare
SdtBarbarossa said:
Well Quallcom HSUSB mode is the mode where you can send direc commands to the cpu in hex speak... i remember that from another phone... so you will only be able to revive it if you find the correct msm8939.hex that can start the download of a partition table and partitions.... i will be honest to you... this whole process is only for very high experienced onces and you will need help from other m8s owners ( you need dumps of most partitions )
so if you find that mprg8939.hex anywhere we can try to revive it.... BUT in 90% of cases your IMEI can not be restored so you cant do calls.... in 40% your emmc is so hard damaged that you cant use it....
there is a second posibility wich is not possible on every phone.... on i9300 (sgs3) you can revive such a phone by creating a microsd card with a partitiontable like the phone and all coresponding partitions so you can boot straight from sdcard... but this case is really rare
Click to expand...
Click to collapse
Thanks for your quickreply. I hope someone can provide me these files. The first phone i own that i didn't root or mess about with fails on me. Lucky me!
I was hoping i could find something in a RUU but my internet speed is very slow. (600kb old telephone line..) I was afraid it was pretty bad. Still can't figure out why these "problems" happend. It just suddenly appeared. And the zip on the SD card was a good solution but i think the EMMC was already corrupted when the first error occurred months back. Will this fall under warranty? The device has some scratches on the back. A few dents on the sides. But the screen did never crack luckily.
Again thank you and i hope i can get it sort off working again because my subscription will end in April next year...
With kind regards,
Erwin
Fast-E said:
Thanks for your quickreply. I hope someone can provide me these files. The first phone i own that i didn't root or mess about with fails on me. Lucky me!
I was hoping i could find something in a RUU but my internet speed is very slow. (600kb old telephone line..) I was afraid it was pretty bad. Still can't figure out why these "problems" happend. It just suddenly appeared. And the zip on the SD card was a good solution but i think the EMMC was already corrupted when the first error occurred months back. Will this fall under warranty? The device has some scratches on the back. A few dents on the sides. But the screen did never crack luckily.
Again thank you and i hope i can get it sort off working again because my subscription will end in April next year...
With kind regards,
Erwin
Click to expand...
Click to collapse
if you never unlocked your bootloader and you are still in warranty send it in... i had a "sudden dead" emmc myself 2 weeks ago (never unlocked never rooted ) and send it in aswell ... they replaced it... but if you ever unlocked the bootloader the warranty is void
SdtBarbarossa said:
if you never unlocked your bootloader and you are still in warranty send it in... i had a "sudden dead" emmc myself 2 weeks ago (never unlocked never rooted ) and send it in aswell ... they replaced it... but if you ever unlocked the bootloader the warranty is void
Click to expand...
Click to collapse
Did it take long? I didn't even try like i said this the first phone i didn't temper with. It is fully stock expect those scratches then.
Fast-E said:
Did it take long? I didn't even try like i said this the first phone i didn't temper with. It is fully stock expect those scratches then.
Click to expand...
Click to collapse
im a german...my device repair needed 10 days (with sending) first time... but atm i resend it in because the cpu is not ok ( nothing they did wrong... just a bad replace mainboard i bet... can happen rare times )
Related
Please post here if your i780 was bricked.
1)Symptoms before brick
2)Name of firmware (PDA/Phone)
3)Kind of repair after.
Thank you for helping community to figure out how to avoid this future
28/01/2010 SOLUTION:
If you have suddenly (or) after flashing of new ROM strange things:
read this post.
i have one bricked i780
hi heniken78,my bricked i780 as follow
1.when flash your 28008 rom dated 13.12.09,it cann't get into desktop suceesefully,and system goes very slow
2.firmware is PDXIB1
3.noway,because i cann't get in bootloader.even plug in charge cable,the led couldn't light on.
sunnyjiang said:
hi heniken78,my bricked i780 as follow
1.when flash your 28008 rom dated 13.12.09,it cann't get into desktop suceesefully,and system goes very slow
2.firmware is PDXIB1
3.noway,because i cann't get in bootloader.even plug in charge cable,the led couldn't light on.
Click to expand...
Click to collapse
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
hashtowent said:
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
Click to expand...
Click to collapse
No when led is not on anymore- you cant get in bootloader.
heineken78 said:
Please post here if your i780 was bricked.
1)Symptoms before brick
2)Name of firmware (PDA/Phone)
3)Kind of repair after.
Thank you for helping community to figure out this BLACK future.
Click to expand...
Click to collapse
My phone was bricked two times
1) The phone rest stuck to Samsung screen when I open it
2) PDXIB1
3) Samsung Center changed the motherboard of the phone
Symptoms:
Every application will respond with message: Application is not signed or missing components (or something else). Only soft reset worked - but phone did a hard reset every time. Sometimes after hard reset contacts stayed as it was (everything else was deleted). These troubles last for 3 days for me until my phone died. Board is damaged and repair will cost 310,- €.
ROM version:
28205 @96 DPI made by ironeagle
Repair:
To buy a new board and a new battery (cause the old one has been damaged too - or just use a second battery instead).
how to execute emergency mode
hashtowent said:
have you tried hardreset(red+green+power) or emergency(b/w+enter)mode?
might you can solve this way =)
Click to expand...
Click to collapse
i donn't know how to getin emergency mode,can you explain what i should to do
emergency mode is the mode u use when u flash a new rom
fn+enter+power(5 seconds).
Anyway, when my device bricked...it was almost 6 months back.
I used quite a bit of wifi, and left my device on the charger with wifi on accidentally. When i woke up a couple hrs later...the device seemed like it was in standby charging. Pulled off the charger, but the charging LED was still glowing! Device didnt respond to anything, pulled the battery out and put it back in....and boom! went totally dead...tried different batteries, tried soft reset, format mode, emergency mode...nothing. no sign of life!
mobo had to be replaced....got it done free as it was just abt 15 days old when this happened
I think its more of a hardware fault....some units being faulty waiting to blow in your face!
Just spoke to Samsung service about bricked phones: From their experience they have changed mobo only once, when 780 wasnt charging, but was working.
But they told that in case of fault of bootloader - thay DONT restore it, just replacing motherboard!
So there is chance to repair you phone by JTAG tool.
I hope trizzio that helps.
heineken78 said:
Just spoke to Samsung service about bricked phones: From their experience they have changed mobo only once, when 780 wasnt charging, but was working.
But they told that in case of fault of bootloader - thay DONT restore it, just replacing motherboard!
So there is chance to repair you phone by JTAG tool.
I hope trizzio that helps.
Click to expand...
Click to collapse
hey dude - where could I get that JTAG tool?
trizzo said:
hey dude - where could I get that JTAG tool?
Click to expand...
Click to collapse
Dude I advise you to visit http://www.omnia-repair.com/ and ask on forum if someone can do this for you. Tool is about 300 EUR and Omnia is top brick phone, so you should find services that already have it, it does support i780.
tip: use google search for more options.
Hey guys,
my phone was bricked: I'd flashed heineken's "i780 WM 6.5.3 ver.28205 DPI 96" rom. After two days some errors appeared and I flashed (&hardreset) the rom again. While connecting to ActiveSync the connection was broken after some minutes. Then I have disconnected the USB-Cable and the phone was frozen. No reaction. No hard-reset keys, no LED reaction while power-connector.
So... I'm not shure whether this problem is because of heineken's rom. But the good news are: Samsung support switched the motherboard because of 24month guarantee
SAM-123 said:
Hey guys,
my phone was bricked: I'd flashed heineken's "i780 WM 6.5.3 ver.28205 DPI 96" rom. After two days some errors appeared and I flashed (&hardreset) the rom again. While connecting to ActiveSync the connection was broken after some minutes. Then I have disconnected the USB-Cable and the phone was frozen. No reaction. No hard-reset keys, no LED reaction while power-connector.
So... I'm not shure whether this problem is because of heineken's rom. But the good news are: Samsung support switched the motherboard because of 24month guarantee
Click to expand...
Click to collapse
Im sorry SAM.
This first version was really weird, I have changed algorythms of compile again in version 2.
But there is always way when you get starnge glitches before you get brick - to flash offical rom to avoid a brick.
As for me I never had any of symptoms..flashed 1001 time.
About bricks...
I have experienced described situations (sudden out of memory, unable to run any app becouse of errors, dissapearing data and so on) around ten times during my cooking/flashing adventures, with different ROMs from different developers. Sometimes at the begining, when weird behaviors of my i780 started, I tried flashing device with other unoficial images, but problems remained. I think I even posted about my problem somewhere...
And I could always recover my device doing one simple thing.
Flashing official PDXIB1.
But important thing is that YOU SHOULD USE OFFICIAL UPDATER from Samsung site (in my case Vista version), not a .bin under Mirage!!
I know it is stupid, but it works better (and if something looks stupid and works better, then it is not stupid any more; Murphy`s law)
In my case Mirage not always proved to be a sollution.
SO every time when that situation emerge, thats what I would do very quick:
1. Hard reset.
2. Flashing oficial Samsung Updater (tutorial on Samsung site)
About reasons bricks happens; I have found no pattern. It happens with WM6, WM6.1 and WM6.5 or WM6.5.x. Sometimes one and the same ROM works perfect two weeks and flashed next time generates bricks.
As someone noticed previously, it is probobly a hardware-software problem, some kind of memory /filesystem/ FAT? damage and it is possible to revert that by flashing official ROM..
I am not a computer scientist, but thats only pattern/mark I can see..
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?
Well, my GF's G4 started bootlooping a few days ago, the local store she bought it from doesn't honor the warrenty and says it may be something we did. I didn't like hearing that and decided to take legal action.
In the meanwhile, she asked if the data can be restored, I started playing with it and reading online. The phone bootlooped anytime I took the battery out and reinserted it, then go off. I decided to put it in the freezer after reading about many successful attempts to boot the device. The first time I put it in a plastic bag for 5-10 minutes (when I took it out it had humidity on it which I wiped), it turned on! and went into Android app optimization and we were thrilled, It went off after 2 minutes so I decided to put it in again for 30-40 minutes in a sealed plastic bag (as many recommended), when I took it out it didn't turn on at all no matter how many tries I tried switching batteries, connecting to the charger etc. (it had humidity on it again when taken out of the freezer).
From then on, the phone won't turn on at all, I put it in a bag of rice in get rid of humidity/water but that didn't help and the device won't bootloop at all.
Now, I have no case as it doesn't bootloop and the store can claim there's damage not governed by warrenty, I can't claim it bootloops as it is a brick.
I'm worried the water caused corrosion which totally cancels her warrenty.
Hope someone can help me fix this out, cant believe I hope it will bootloop again.
Thanks.
What version of G4 have you ? H815 ? or other ?
you can try to flash official firmware with LG UP with .kdz file or if you have another G4 with .tot file
You must have computer with drivers installed and LG UP installed
Watch tutorial
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
1. volume up and connect to pc
2. flash the "core disable" kdz/tot (whatever it is)
3. it should boot but it won´t be as fast as i has been
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
To be honest with you pal i very much doubt you'll get it back working as the serial is a 505 which means it's included in the bad batch of faulty motherboards on the phone and its that which is causing the bootlooping , you need to tell the place where you got it that the hardware has failed out of your control if they don't help try contacting LG directly you could be lucky....
YSAndroid said:
Now, I have no case as it doesn't bootl
Thanks.
Click to expand...
Click to collapse
When I did the following steps, I was able to get back into the phone with all my apps and internal data right where it was. It only fixed the corrupt system files. It seemed to work like startup recovery on Windows. But as a warning, I've only done this once so cannot guarantee you the same.
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGM..._4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product...reinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
I was lucky and this didn't remove any of my data.
If you have problems with LG Bridge detecting your device:
i) Make sure you have the drivers installed and are using a reliable cable and USB port.
ii) Open up device manager and look for your phone. It should be named [...... COM#].
iii) Right click and go to the ports tab and click advanced. Select COM41. This seemed to work for me.
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Saad6459 said:
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Click to expand...
Click to collapse
same happens to me bro my android one is also dead same problem as yours when i tried with sp flash tool its end up with this error..... scr shot attached
☹
Bro,I flashed it thrice after but it didn't give any errors,but sadly it just wont turn on
If it were permanently bricked then it wouldn't have detected the phone...and bro lemme give you a suggestion,try changing it to firmware upgrade instead of download only.
Thanks for the reply
simmilar issue
same problem pls help in my case when i charge not charging the battery indicator just pops up and out i think its a battery error put in a new battery try to boot up nothing try to go in recovery nothing i have nothing to boot up from i think ill still try using fastboot and/or flashing and reporting back(ima try dead usb flash using spflash tool)
okay flashing works perfectly now i just need for figure out if the problem is with the charging/battery or the phone is dead
Same Problem
Bro, i have run into exact same problem. I even went to gallery and gave them the phone, they said they will charge 1500 as motherboard is dead but after one month they returned to me the phone saying that motherboard is not available. They are taking almost 14 days to return money so i have to visit again on 3rd june. But coming back to problem i have tried flasing with and without battery for 3-4 times. every times it shows success but the phone wont start. Even memory test was all fine. cant figure out what's the problem. i have tried both download only and format+download mode but nothing seems to work, If anyone finds a way to fix the phone please tell ASAP.
Same problem as the OP, mine's bricked as well after it began showing random FCs. Flashed KK and LP firmwares using SP Flash Tool but to no avail. The flash was successful tho but the phone never booted up
I'm kinda stuck in a similar situation. Let's start from the beginning -
When I got my Redmi Note 3 I stopped using my Canvas A1 and vaguely i remember that it was having software issues, rather than fixing it I just kept it away for a lot of months, and vaguely I remember that it just needed some flashing of rom and it would've gotten fixed.
And after all these months i'm need of this phone again. I don't remember much in depth details of the processes involved with it like flashing stuff etc. But I gathered as much knowledge as I could from the docs I had stored as backup & from the internet.
And IMO I think the flashing process was successful, but the screen is not turning on. Only once when I connected it to PC, the charging battery sign appeared(flashing thrice) but that was it. Nothing after that. And whenever I connect it to PC it detects the phone.
For now I've given it to a repair guy but I don't have much hope. He was saying that it could be just software problem, but I don't agree. If a smart person could comment on this thread so that we all could get some benefit out of it, in order to solve the situation or at least in my case I could research on something specific in the meantime.
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.