Hard Brick, Help Please! - Galaxy Tab 7.7 General

Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!

have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...

edan1979 said:
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
Click to expand...
Click to collapse
its been charging for about half an hour. still not turning on so cant get to download mode!

I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you

slide200sx said:
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
Click to expand...
Click to collapse
Thanks for the advice! I'm not sure it's a battery problem though? Is there anyway I can tell?

To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....

slide200sx said:
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
Click to expand...
Click to collapse
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
and no luck, it doesnt auto power on
Im considering doing jtag... but hmmmmm
https://www.dropbox.com/sh/rqhhgs34vuzt4u4/fGwL0TiSYc
i pulled out the power/battery cable, plugged the tab into the computer and then plugged the power in. nothing.
it also didnt work when i plugged it into the wall

When plugged in my wifi chip gets warm... hmmm

@Scottyn...
Dude, you need to do the swopping of power from wall socket to computer then back again and again and again......all the time while doing this holding the power button in.....try it
Also, if you have puled the thing apart now you should be able to test the battery for power with a volt meter or something....
does the battery have power...
does the battery get power from the cable or pin running to the battery?
Can you turn the tablet on with a different power source to the battery terminal on the phone?
I would check these things first, then hold thumbs....I dont know, if it's not the battery then it may very well be a dead hardware issue and not a data issue or fried memory as they will normally boot the tablet to a point.....
May very well be the battery cooked

Im too scared to attach a an external powersource to replace the battery. I have the equipment, but it could easily fry the rest of the board
Ive closed the device back up, so ill have to reopen it before i chuck a voltmeter on the batteries
and ive swapped from computer to the wall about 10 times (swapping every 5 seconds). Nothing
Plus; if i diagnose the problem as a fried battery then cant really do anything about it

scottyn said:
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
Click to expand...
Click to collapse
We had a similar faith. It was when this wiping thingy messed up my Tab. My only consolation was that my Tab is under warranty and did some make up story at the service center. Had replaced the motherboard and now up and running. I'd promised myself that I'll limit my "genius" with rooting and flashing an official fw. Custom rom is a big no for me, no matter how great and stable it was. The wiping part is like kiss of brick. Yes, i know...there's a disclaimer.

sweet. Ive decided to send it all back over to australia. annoying, but ill get a guaranteed fix
I think ill stick to stock ICS from now on

scottyn said:
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
Do you mean you opened up the tabs case?
how did you do this?
any pics?
I ve read you have to lift the screen from the back cover..
It scares me to think about levering it and cracking the screen or something..
Click to expand...
Click to collapse

Related

Phone thinks its connected to USB

I put DL09 on and then added stupidfast v1.54. Worked fine at first but now it thinks its plugged in all the time and if i turn it off it wont boot unless plugged in. Is this a hardware issue or an issue with the kernel? Thanks for your help.
Had the same thing too. Started from scratch with Odin. Good as new now.
So i plugged my phone in and the notification for the USB went away. I havent tried to reboot yet, but the battery meter keeps going from 68% which the phone is at to 100%. Its very odd.
Is there a way to reset the battery? That might be way off but i dont know enough about it really.
see this thread
http://forum.xda-developers.com/showthread.php?t=919770
My computer sees my phone. The battery stopped jumping too. Im gonna try to clean the port when i get home from work. I still need to plug it in to get it to boot. I was gonna try reverting to stupidfast 1.98 to see if the kernel is the issue. If it makes a difference i had flashed the circle battery and it started about 12 hours after i did so. I reverted to a backup i had saved. As this didnt completely fix the problem i assumed it was the kernel. Battery life is good with the kernel as expected but the phone just seems a little testy, some things are just a little laggy like its struggling. Any additional help would be greatly appreciated. If i cant find a solution im just gonna have to re-odin everything.
Well, seems it was a dirty port. Throughout the night things got better. Got home didnt have any rubbing alcohol so i stuck some heavy paper in there to try to rub off the port. When i tried to reboot it was hit or miss, when i held the power button the battery charging screen would come up as if i was plugging the phone in while it was off to charge. Could be due to weather here maybe i had salt on my fingers from the snow and i touched the cable before i plugged it in. However GPS isnt locking in any better than it did with DI01. Ill take it for now, vast improvement over this afternoon.

Not recognizing battery

So after a long fiasco of installing an old GB leak before installing the latest version, to running into force close loops and freezing at the M logo. So finally i reflashed everything and rebooted and bam! i finally got 596 to work. But i noticed that my battery logo had a question mark and that it basically wasn't recognizing my battery. I thought maybe a simple reboot will fix it, went in cwm and flashed the 596 deodexer and rebooted. Got into the lock screen when i noticed it immediately said Connect Charger. When i unlocked the screen after about 10 seconds it went black and my phone wouldn't turn on. If i connect it to pc the led flashes blue for a second meaning the battery is dead but with the battery not being recognized it cannot charge. If i connect it to a wall charger it loads up the M logo and goes to the battery charging screen, when you completely drain your phone and need to wait til its 5% to turn on, but again has a question mark in it. I don't have any external chargers either. Whats my best course of action? Do i have to go out and buy a new battery...? All helps appreciated.
im very sorry about bumping my thread.., but my phones just sitting here useless and its very aggravating and extremely inconvenient so once again, any and all help is appreciated please gentlemen(ladies).
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
djsupersoak said:
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thank you for the reply, ill try wiping the batter stats asap might have to end up ghetto rigging a charge into it. Ive heard that car chargers/external chargers will still charge it, is this correct? I would love to try your second idea except for again i don't even have a charge anymore. i tap the lock button and the led flickers blue for half a second, which if im not mistaken means the battery is completely dead. While i guess its always possible, never really expected my phone to just randomly stop realizing there's a motorola batter inside of there.
Edit: also if im not mistaken i believe that i had tried to plug the charger into after/during boot up and it still says its not a certified battery or whatever the message is and refuses to charge.
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Tone_Capone said:
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Click to expand...
Click to collapse
I have actually seen the app before, at the time didnt really notice what it did but i understand a bit more now. If any of the actual charging methods work ill definitely try that. Might just have to hook it up to a split usb for a while to get a decent charge.
djsupersoak said:
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it. Ill try the car charger i suppose, wont hurt. Worst case I do actually have a friend with a DX so i can see whats up with that. Ive been meaning to pick up the extended for a while now just never really got around to it, guess this might give me an excuse. thanks for the offer to send out a battery though
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
djsupersoak said:
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Great news gentlemen! so after trying the usb split usb method to charge my phone, the first time it didnt work. i just figured i didnt have the wires pushing on the battery poles enough so i retried it. Ended up forgetting it was plugged in and about 30-45 minutes later took it off. plug her in and my phone started up, good signs so far. Finally my os loaded and lo and behold, there's my battery showing green! So i quickly throw it on my wall charger and its charging too. Wiped my battery stats just in case anyways and reflashed everything. Got 596 loaded up and running and deodoxed. After trying to install a battery mod i got a few boot loops but after a wipe didn't work luckily i made a 596 nandroid before trying it. Flashed back to that and everything loaded up fine. Cant thank you guys enough for the help you've been. making a nandroid once my full set up is back to normal haha

Guys read this and give thoughts please!!!!

Ok this will be a bit lengthy but please bare with me and read...
Ive been running Darkyy 10.1 EE for months now and every has been fine.
Easily a couple of days battery, no force close issues of any sorts... Everything has been perfect.
Then the other day i noticed my battery started dropping fast. NO THIS IS NOT A BATTERY DRAIN THREAD SO PLEASE READ ON.
I took my phone off charge the other night within seconds of hearing the beep for battery full and the fully charged icon in the top right of the bar stayed there for a few seconds ( like maybe 10 ) and then the battery level dropped to 80%.
I thought hhmmm thats not right but left it and went to bed.
6 hours later i woke up to 31% battery.
I thought something must be running killing my battery so i did a reboot...
Now this is where it gets weird. Read on my friends...
after i rebooted the phone it kept rebooting itself every 2 minutes or so.
I pulled the battery of for 30 minutes and put it back but i had the same problem.
When i got home i did a factory rest and wipe cache partition and decided to flash Darkyy 10.2...
I had the same problems as above only now when my phone rebooted the battery lvl would drop by 20% then next time raise by 5% etc etc
NOW THIS BIT IS SCARY BUT READ ON!!!
I decided to flash back to froyo with ezbase using repartition to see if that would help.
I plugged my phone into the computer and nothing happened!!!! My computer wouldnt recognise my phone at all neither would my phone start charging whilst plugged into the computer.
I managed to get my computer to see my phone by booting into recovery and and then download mode and flashed ezbase.
Again same problems. So i thought OK this might be an insurance job so i flashed it back to stock JPY from samfirmware.com. I plugged it back into my computer and my PC says "the USB device you have connected has malfunctioned and windows cannot recognise..."
I have had my phone unplugged over night but the icon on the bar is still there showing USB connected, and in the pull down shade there is still the option to connect USB to copy files.
I have plugged it in this morning and it started charging but windows didnt even recognise that there was anything attached at all! No beep no fault deviced attached message... Nothing!
Oh i would also like to mention that when i flashed ezbase and tryied to do a reboot i would get the battery icon for a second like if you charged while the phone was off and then it would power down again... The only way i could get the phone to boot back up was to flash EZbase again with auto reboot ticked!
Yes that was very long sorry and thankyou to those who took the time to read it.
If anyone has any thoughts on why this would have happened please post.
Do you think this is something caused by the custom rom or is this a hardware issue completely out of my hands?
Thank you again for reading!
Have you tried another battery?
Sent using geek power
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
gsw5700 said:
Have you tried another battery?
Sent using geek power
Click to expand...
Click to collapse
I dont think its a battery issue because the battery wouldnt prevent the computer from seeing the device would it?
mammenj said:
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
Click to expand...
Click to collapse
Im running stock JPY right now and have the same problem
Could it be a damaged usb port, so that it doesn't always charge properly, and doesn't always detect the phone correctly when connected to the computer? That might explain the problems... Especially if that port is getting worse all the time.
Can you get it to detect on the computer if you wiggle the usb plug to the phone? Have you tried a replacement usb lead?
It does sound weird. Hope you manage to sort it out.
Mike
Garbled meaning induced by swype!
don wadte time if ur phone dosnt work on stock then its the port tht got damaged and the hardware,,,,something wrong .....better go to a service center..don expirement ,cause it might damage it more
I have just dropped it off at the shop i bought it from and they are sending it away for repair.
2 weeks of nokia 3210 magic for me!
Thanks for replies guys.

My g900F is Hard Bricked - Help me please

Hello.
I've flashed my s5 with popwizh and everything went well. But after a full battery discharge the phone won't turn back on.
Battery is good and charger.
volUp+home+power doesn't do anything
volDown+home+power doesn't start download recovery
tried to boot from sdcard with a debrick img but no luck.
What more can I do? I don't want a paperweight please.
Charge it?
Battery is good and charged
If you can't get it to even turn on or enter download mode, there's not a lot you can do
Try removing everything like SIM and SDCard, remove the battery too and only connect the charger, see if you can get any signs of life at all
If not, it sounds like a hardware problem
Its to much of a coincidence to be a hardware problem, I refuse to give up just yet.
So far all the posts that resemble to my situation go on an on about flashing a debrick.img to the sdcard and boot from there. Dead boots and stuff.
I did this: http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626 but without success
You said it won't even power on ?
How you going to flash anything without power?
I'm not saying 100% this is the problem, but most devices die when they are powered on, as that is when they are put under the highest stress
For example, I put away my treadmill in the corner of the room about 6 months ago, working - came to use it a few weeks ago, dead
Looks like pixies killed it, but actually it was when it was powered up again, just looks like it died when it was off
--
Is the phones power button working?
If you at least had a sign of life, we could go from there, but without any power at all, I have no clue
Battery connection contacts not bent or snapped?
From what I understand the phone won't turn on because the boot partition is gone, so if I manage to boot from the sd card to the download recovery, I can then use odin to flash it back to stock android.
Am i wrong?
Are you even getting the logo on screen when you turn it on?
Does the screen even light up?
You said there is no power at all, that's not a boot partition problem
Man if it's not turning on and there's no reaction when you press the power button then there's two things I can suggest : the power button is not working; or when the battery went completely dead its safety system thing could have turned on, which means you have to put it to charge as long as it takes for it to turn on again. Plus if your phone was exposed to water which I doubt its power controller could have gotten burnt
Have you plugged it into a pc? See if it registers with that and if it dies but still doesn't boot just try to leave it on the charger for a few hours even if it's fully charged. Then battery out for 10 secs wait... wait... wait... and turn it on plugged into the wall. Or at least try. If that still won't work samsung repair Centre for you
Still no life, I've tried everything said so far. My only hope is a debrick.img to boot from the sd card, which I don't have.
maskioice said:
Still no life, I've tried everything said so far. My only hope is a debrick.img to boot from the sd card, which I don't have.
Click to expand...
Click to collapse
Try to plug the phone to adb and see if it recognize it , if it's not i don't know maybe try another battery to see if its battery related or other hardware composant

HELP !!! S7 Edge doesn't turn on (neither on download mode, nor on recovery mode)

So my phone was OK, when suddenly having 42% of battery it turned off and didn't turn on again. I can't access to download or recovery modes to flash it and change the ROM. The phone doesn't react even on charging (0 V, 0 A on the USB cable). Don't know what to do.
Did anybody have this problem too ? I really need to bring back this phone
Do you happen to have a blue led light and a completely black screen ?
xTweeBy said:
Do you happen to have a blue led light and a completely black screen ?
Click to expand...
Click to collapse
No, there is nothing. Just bricked phone without any sign of life.
Unfortunately, if that is the case, this may be a hardware problem related to the motherboard which needs to be replaced. Make sure to leave it for a few days then try to charge it to see if it would respond, otherwise, make also sure that this is not a display problem by checking if the device is working ( try phonecalls or so ... )
xTweeBy said:
Unfortunately, if that is the case, this may be a hardware problem related to the motherboard which needs to be replaced. Make sure to leave it for a few days then try to charge it to see if it would respond, otherwise, make also sure that this is not a display problem by checking if the device is working ( try phonecalls or so ... )
Click to expand...
Click to collapse
It is definitely the case. The battery itself gives 3.6 V but the phone is not getting it. I've seen a topic where a guy was advising to perform a JTAG flashing (can be a bootloader error) connecting the phone immediately to a power source (without battery). But not sure if I can perform it too. Any ideas ?
Bootloader errors are mainly due to motherboard malfunctions on the galaxy S7 edge, this is a very common issue where the only fix is to completely replace the motherboard, some cases can be repaired due to a reset or a stock rom flash ( which cannot be your cases because you cannot access to download more nor recovery) while others are fixed with a custom flash. Some very rare cases are also fixed with that JTAG flashing you heard of, this forces the battery to work and deliver its power to the rest of the parts, but this is a very risky operation which can damage your entire phone. If you wanna try it, I advice you to get some professional help as you can hurt yourself too in this process ! Good luck
It looks like you a main board issue. You might need to have that part replaced.
xTweeBy said:
Bootloader errors are mainly due to motherboard malfunctions on the galaxy S7 edge, this is a very common issue where the only fix is to completely replace the motherboard, some cases can be repaired due to a reset or a stock rom flash ( which cannot be your cases because you cannot access to download more nor recovery) while others are fixed with a custom flash. Some very rare cases are also fixed with that JTAG flashing you heard of, this forces the battery to work and deliver its power to the rest of the parts, but this is a very risky operation which can damage your entire phone. If you wanna try it, I advice you to get some professional help as you can hurt yourself too in this process ! Good luck
Click to expand...
Click to collapse
Thanks for the info. Is it possible to replace it with another board from another used phone ? Won't it cause any conflicts with other phone parts ?
Dude i had the same problem before 2 days and what i did was i ejected the sim tray and put usb cabel in it and hold every key and it booted up
Sorry for my bad english
AveHakob said:
Thanks for the info. Is it possible to replace it with another board from another used phone ? Won't it cause any conflicts with other phone parts ?
Click to expand...
Click to collapse
Yeah, you just have to make sure that it is completely working. But my experience shows that it doesnt end up really well, because the phone will just suffer from other malfunctions due to imcompatibility and all. So I dont recommend you doing it, if you really want to repair it, send it to the customer services !
Good luck
xTweeBy said:
Yeah, you just have to make sure that it is completely working. But my experience shows that it doesnt end up really well, because the phone will just suffer from other malfunctions due to imcompatibility and all. So I dont recommend you doing it, if you really want to repair it, send it to the customer services !
Good luck
Click to expand...
Click to collapse
Thanks. Their only recommendation is to throw away the phone because it's not going to work. Will try the official service too but not sure if they'll help me.
Creative one said:
Dude i had the same problem before 2 days and what i did was i ejected the sim tray and put usb cabel in it and hold every key and it booted up
Sorry for my bad english
Click to expand...
Click to collapse
Not quite sure how it can help, but will try it tomorrow maybe it'll work. Thanks
Same issue here, were you able to resolve it?
xTweeBy said:
Unfortunately, if that is the case, this may be a hardware problem related to the motherboard which needs to be replaced. Make sure to leave it for a few days then try to charge it to see if it would respond, otherwise, make also sure that this is not a display problem by checking if the device is working ( try phonecalls or so ... )
Click to expand...
Click to collapse
I had the same issue. As suggested that the phone may switch on once the battery is completely drained, I waited till last night and plugged it in and it started charging.
It was fine till this morning. I inserted the SIM cards and then connected to the laptop. I thought I would backup the data using smart switch before doing a factory reset. The backup went fine till 75% and then boom again turned off. This time there's a lot of battery left, and I might have to wait 4-5 days before it can be drained completely. But I'm now hopeful that it'll eventually turn on and when it does I'll immediately do a factory reset before doing anything else. I'm suspecting that a rogue app might be causing it. This time it might have happened while that app is being backed up. The LED is constant Red this time indicating the state it was connected to the laptop at the time of incident.
Is there anyway to drain battery quickly at this stage?
It turned on again last night when I connected the charger. It was showing the charging symbol. After 5-6 minutes of charge I tried to hold Vol - + Power buttons briefly to reset the device and it went off again. It's lying like a brick currently.
ilikered said:
I had the same issue. As suggested that the phone may switch on once the battery is completely drained, I waited till last night and plugged it in and it started charging.
It was fine till this morning. I inserted the SIM cards and then connected to the laptop. I thought I would backup the data using smart switch before doing a factory reset. The backup went fine till 75% and then boom again turned off. This time there's a lot of battery left, and I might have to wait 4-5 days before it can be drained completely. But I'm now hopeful that it'll eventually turn on and when it does I'll immediately do a factory reset before doing anything else. I'm suspecting that a rogue app might be causing it. This time it might have happened while that app is being backed up. The LED is constant Red this time indicating the state it was connected to the laptop at the time of incident.
Is there anyway to drain battery quickly at this stage?
Click to expand...
Click to collapse
had the same thing happen to me.
Initially crashed.
could be turned on after draining the battery(phone was still warm at times with screen off/phone off)
charged and could turn on again.
But the time it could stay on would decrease and decrease.
It then just bootlooped and with that would only accept charge turned off.
In the end I couldnt turn it on at all and it wouldnt charge.
Looking to replace my mainboard now. seems that the Flashmemory damaged itself.

Categories

Resources