Database Info

Is my phone dead?

Hi All
Hoping someone can tell me if I've completely killed my phone. It was working absolutely fine with no problems whatsoever until earlier today when it froze. Without looking around at what to do I just held down Vol + & Vol - & power. This restarted the phone and it went through the T-Mobile logo and then just sat there. I then took out the battery, put it back in and held vol - and hit power, got into the clockworkmod menu and used the recovery option to wipe then restore an earlier backup, this all seemed to go fine and I used the power off option to restart the phone.
Nowwww though it just vibrates 7 times and stops, if I then pull the battery and replace it and hit power it vibrates 7 times again and then nothing unless I pull the battery again.
Am I screwed?
The phone is S-Off and had clockworkmod installed. Has the clockworkmod boot loader thingy some how been damaged? Anything I can do?
Appreciate any advice. Thanks

can you get into recovery? if so try wiping everything and then doing a fresh install of something
Sent from my Desire HD using XDA App

dont keep pulling the battery if you dont already have emmc failure you will soon if you continue to pull the battery!

Yea I didn't realise pulling the battery was that bad. I haven't done it since reading this forum. But no I can't get in to recovery any more since that time I wiped everything and restored a backup. Since then it just vibrates 7 times when I push the power button and that's all.

can it connext to adb? if so, id try flashing an ruu via fastboot. that will set everything back to stock. then you can reroot and flash a rom, and id get rid of that backup
Sent from my Desire HD using XDA App

Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?

rlzzzz said:
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
Click to expand...
Click to collapse
theres tons of guides but if you give me a few minutes ill upload a auto installer for you, so then you just have to add the path in
Sent from my Desire HD using XDA App

I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?

rlzzzz said:
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
Click to expand...
Click to collapse
it could of, and its worth a shot, it might be recognized. just get adb working, and install the drivers. plug the phone into your computer, and wait a minute or 2 and the screen should turn on but be black. then just boot into the bootloader and flash the ruu via fastboot
Sent from my Desire HD using XDA App

So I installed Java JDK, then Android SDK, then downloaded the HTC adb drivers but it says to install the drivers plug in your phone and wait for Windows to detect it... which is as far as I can go because Windows doesn't detect the phone.
I don't even seem to be able to reset the phone by holding Vol + & Vol - & power at the same time. It's not looking good.

In fact you say about the phone going to a black screen, it did do this after I initially restored the image. But it was just after that that I pulled the battery and now it doesn't do that anymore.
I assume basically what has happened then is first some thing froze and corrupted my normal install, so to fix this I tried the restore and the restore image somehow overwrote clockworkmod but at this point the phone was still recoverable via adb? but then I pulled the battery and now it's definately dead?
Seems like an unfortunate string of events but at least I know now to avoid pulling the battery next time! Thanks for all your help stumpyz9 and djisgod, I don't suppose you know why pulling the battery can so easily kill the phone?
Btw if anyone would like to jump in and make my day by saying nooo everything is fine here is a quick fix please feel free

my only guess of why pulling the battery killed it is when you where restoring it and then pulled the battery, it was restoring something very essential to even turning the phone on. i dont know why windows wouldnt detect your phone, it has derected my DHD even in the worst scenarios. and were you saying the drivers wanted you to hook the phone to the computer? if so dont and try to continue installation, because if you can get it hooked up to your computer and have adb recognize it, then tyere is a very good chance you can recover it. if not, then im sorry to say you have yourself a very pretty paper weight. if it is a paper weight, id say maybe check to see if a dev could use it or basically part it out on ebay and sell the lcd, digitizer, housing, camera and you can probably make some of your money back.
Sent from my Desire HD using XDA App

The ADB HTC drivers I downloaded are not an installer file, you need to plug in the phone so Windows will recognise a new device and ask you to select the location of the drivers but I can't because it doesn't detect the phone being plugged in at all.
I've also been reading around a bit more and found a thread about a fried eMMC chip. I was actually getting the same errors they mention in that thread when I did the restore from clockworkmod.
"E:Can't open /cache/recovery/log" etc etc

dont use that, install htc sync, then plug the phone in and tell me if that works
Sent from my Desire HD using XDA App

Yea I just gave that a go after reading someones adb guide and even with HTC sync installed when I run "adb devices" it lists nothing.
It's strange I thought once I had clockworkmod installed nothing could go wrong because I would always be able to restore from an old backup. I always assumed that clockworkmod would be sat on the boot partition and never touched even when restoring a backup. I can't understand how it went so wrong lol.
Although right now the phone seems so far gone maybe I could get away with a warranty repair as they won't be able to tell it was S-OFF.

yah if all of the chip has been fried and it wont power on, i think that would be your best bet, seeing as they probably wouldnt be able to tell.
Sent from my Desire HD using XDA App

Ok well thanks for your patience I appreciate your help.

rlzzzz said:
Ok well thanks for your patience I appreciate your help.
Click to expand...
Click to collapse
no prob, alwsys like to help out when i can
Sent from my Desire HD using XDA App

[Q] Device completely unusable :( PLZ HELP

I tried following cyanogen wiki on an Inspire 4G. It didn't work and gave "Incorrect Model ID" error.
So I switched to use Hack-Ace tool. Everything worked as expected and I guess I was going good. When Hack-Ace completed, the phone went into an infinite look showing HTC logo then blind to a black screen with background light ON.
I could ADB and reboot in bootloader where I clashed the CM7 ROM. Every step went through fine and it restarted. Now all I get is nothing.
The device shows the HTC Logo on white screen after leaving a while and the vibrator is ON constantly. It doesn't help really but keeps doing that. It will only stop if I remove battery.
Plugging the device into USB doesn't detect on PC.
When tried charging, it shows the error messages and nothing happens, no buttons interact.
I guess I have a full brickd phone now

Have you tried flashing stock ruu thru bootloader
Sent from my Inspire 4G using XDA App

Download and flash this thru bootloader.
http://www.megaupload.com/?d=Q6YYQFIM
Sent from my Inspire 4G using XDA App

Yah, try the ruu. Seeing how it at least turns on means it might be fixable. Can you get into recovery?
Sent from my MB860 using XDA App

I'm trying the link given by creglem
stumpyz9, no man i've not been able to boot into recovery.. the device is doing nothing

kishu_27 said:
I'm trying the link given by creglem
stumpyz9, no man i've not been able to boot into recovery.. the device is doing nothing
Click to expand...
Click to collapse
The ruu will probably be your best bet then
Sent from my MB860 using XDA App

only if i could get it to install... i dunno what'll happen cuz i cannot go to recovery mode. i'm just going to try once
worst part is that this is a friend's phone

not able to open recovery
any other idea guys?

kishu_27 said:
only if i could get it to install... i dunno what'll happen cuz i cannot go to recovery mode. i'm just going to try once
worst part is that this is a friend's phone
Click to expand...
Click to collapse
http://webchat.freenode.net/?channels=#aahkSupport <--- go there to save said friends phone.

kishu_27 said:
not able to open recovery
any other idea guys?
Click to expand...
Click to collapse
You font nerd recovery with that file. Just out it on the root if your sdcard. Meaning not in any folder and boot into bootloader...not recovery then it will recognize the file then just follow onscreen instructions
Sent from my Inspire 4G using XDA App

kishu_27 said:
I tried following cyanogen wiki on an Inspire 4G. It didn't work and gave "Incorrect Model ID" error.
So I switched to use Hack-Ace tool. Everything worked as expected and I guess I was going good. When Hack-Ace completed, the phone went into an infinite look showing HTC logo then blind to a black screen with background light ON.
I could ADB and reboot in bootloader where I clashed the CM7 ROM. Every step went through fine and it restarted. Now all I get is nothing.
The device shows the HTC Logo on white screen after leaving a while and the vibrator is ON constantly. It doesn't help really but keeps doing that. It will only stop if I remove battery.
Plugging the device into USB doesn't detect on PC.
When tried charging, it shows the error messages and nothing happens, no buttons interact.
I guess I have a full brickd phone now
Click to expand...
Click to collapse
Dude download the PD98 file above it is the rooted updated gingerbread ROM. Place it in the root of your SD card (you will have to remove SD card and use adapter to move zip file to root of SD card if PC does not recognize phone with USB cable) and power phone off then power back up holding down power button and volume down button at same time. Phone should go to bootloader then it will recognize the PD98 zip file and ask if you want to istall. Volume up for yes and it will do its thing. No need to try to get into recover phone will do it itself with the PD98 zip file. Zip is (ATT ROM 2.47.502.7 w/Radio - 26.10.04.03_M)
Credit to Football

[Q] Nexus S - can't mount anything! - stuck on Google Logo

Hello!
Okay, so the weirdest thing has happened with me. My Nexus S (i9023) was working absolutely fine till last evening when it ran out of battery. After I came back home, I put it for charging and switched it on.
For the first few time, nothing would show except the USB connected/ disconnected screen which appears everytime you plug your phone in. I thought maybe it was just being weird, so I took out the battery and booted it up again. This time I am just stuck at the Google Logo! It is not going ahead.
I can enter CWM Recovery. However, I cannot mount sd card or usb storage or anything for that matter. If I try and install through .zip it says 'e can't mount sd card'. I can't format my sd card either, same problem of can't mount. I thought if I tried pushing a ROM in by ADB that might work.. It did transfer the file it showed that in the cmd window. However, CWM refuses to mount my sd card or my usb storage.
So basically, in essence, I'm locked out of my Nexus! Please please help. I'm really lost and confused now.
Thanks so much.
Alex

Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I'm starting now. I have a doubt, how do I install stock? Since I can't seem to be able to mount anything..
"It can be fixed" - few words have given me this much hope in my life! Thanks a lot!
EDIT: I guess you mean flash through ADB right? Okay, let me try that. I really hope you are right. Some of those other problems lead to paying up! Ouch.

Hey! I just tried using WUGS.. for some reason it does not make the final boot and instead says: 'Fastboot Status - FAILWrite Fail' -- oh god.. I'm trying it again now..
Is there any other way out? :/

Okay, so now my recovery is also gone after using WUGS.. oh man. And the phone isn't starting up. Please please please help? I'm getting really desperate now.
EDIT: And it sucks that I can't post in the WUGS thread (http://forum.xda-developers.com/showthread.php?t=1766475) because I have less than 10 posts! fml.

can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into fastboot - i'm leaving the battery out now - do you think i should try
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and then flash everything again?
There is always a way to recover the nexus right? Even if it is hardbricked, right?
I really really appreciate your help.

I too have this problem but after a lot of battery pulls it does eventually start up. It just started happening all of a sudden. Ive heard that heating it up with a hair dryer or heatgun can help and also re-locking and un-locking the boot loader can help as it wipes the card. Could be worth a try.

Any luck Someone? I know it sux big time to feel like your phone is bricked. I am not a dev or expert but it sounds like the prob I had last week, when I posted no one replied so I ordered a GNex thinking all was lost. Before I activated my new phone I felt like I had to fix my nexus before getting started on my new phone and that's my situation. I don't want you to feel like the community has forgot you and thats why I'm trying to help. Were you able to get Wug's Toolkit to recognize your phone after leaving the batt out? I don't know why but I think that's the key. I had to leave mine overnight 'cause I don't have a PC and the next day at my friends house when I plugged the USB in I got that message at the bottom of fast boot "system normal" or something to that effect. Once recognized the stock boot IMG is what you need.
ANY ONE ELSE WHO HAS HAD THIS OR A SIMILAR ISSUE PLEASE GIVE SOME ADVICE. LET'S NOT LEAVE A COMMUNITY MEMBER WITH A LIFELESS PIECE IF PLASTIC. THANKS FORUM.
To set your mind at ease yes, I believe as long ad you have access to fastboot your nexus can be saved.
Sent from my Galaxy Nexus using Tapatalk 2

sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.

Blo0dyyy said:
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Click to expand...
Click to collapse
Hi, if I'm not wrong essentially what WUG does automatically is what you do by fastboot (erase bootloader, cache, system.. and then flash all of them back) in both system fails to wipe and refuses to be flashed again (flashwrite error).
I don't want to lock it and then unlock it again because I read in other threads that it might lead to a permanent lock with an error for subsequent unlocking - that would leave me completely out.
Anyway, let's see - I've given it to someone to check it up. I'll keep you guys posted. He said he wanted to repartition the sd card.
My intuition says: hardware problem!

So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.

Get it going someone?
Sent from my Galaxy Nexus using Tapatalk 2

I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot. No ADB commands will function. It was charging, rebooted itself into a bootloop, and I have been struggling with it ever since. It is currently a worthless piece of plastic, my favorite phone ever, gone.
I can wipe and re-write recovery all that I want, but it seems as if the sdcard partition that /system and some other stuff writes too is either corrupted or physically damaged. Every time I flash it all via fastboot it all goes as stated, but gives me a fail message on the last two partitions and never allows me to actually write a new ROM or boot image. I wanted to try ODIN but can't seem to get it to recognize my phone in download mode...
Let me know if you have any success or progress!

someone. said:
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Click to expand...
Click to collapse
I myself am experiencing the same problem.... Did your cell got fixed.....?? Did JTAG worked kindly keep us posted em really concerned about it... coz your solution might get me some where or else i hav completely lost my phone ;(

Get it going someone?
Click to expand...
Click to collapse
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot.
Click to expand...
Click to collapse
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.

someone. said:
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
Click to expand...
Click to collapse
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD

someone. said:
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
Click to expand...
Click to collapse
I am with the same problem here... I cant turn off my phone or it get stuck in pre-boot phase. Acess recovery and cant mout sd card. Using last stable cm 10.
I think my sdcar is dead.

Same problem here. Around 8 out of 10 times I get stuck on the Google logo, 8 out of 10 times in recovery I can't mount SD card as well. And if I successfully boot, Media wakelocks and my battery drains in sleep as fast as if the screen were on. Please help.

For me I first noticed that my apps weren't using the SD partition. Tried to mount normally (fully loaded ROM) (ROM is SlimBean Beta2), but it would not mount. Went into CWM and tried to mount in there, but it would not work. tried to "Format /sdcard" but "Error mounting /sdcard". My phone still boots and runs fine, but I just don't have access to the SD partition. I don't want to do anything because I need my phone for business. Is there any PROVEN way to fix this yet?

Mightve bricked my P5113

Hi, i tried updating my tab to the leaked 4.1 OTA and after following the instructions my tab wont boot. It will only play the boot animation then hang at the samsung logo for about ten minutes then go black. I cant get it into download or recovery mode, but when i plug it into the wall it shows the battery icon. Also odin recognises the tab while its hanging at the samsung logo.. i have heard talk of a usb jig but not for this tablet.. Can anyone offer any advice? thanks in advance

If Odin sees it a USB jig isn't needed.. Just flash the stock f/w tar and you're good
EDIT: fail... No download mode... Umm... Sounds like you're in a bootloop... No idea why recovery and download wouldnt work tho...
Sent from my XT907 using Tapatalk 2

HulianMango said:
Hi, i tried updating my tab to the leaked 4.1 OTA and after following the instructions my tab wont boot. It will only play the boot animation then hang at the samsung logo for about ten minutes then go black. I cant get it into download or recovery mode, but when i plug it into the wall it shows the battery icon. Also odin recognises the tab while its hanging at the samsung logo.. i have heard talk of a usb jig but not for this tablet.. Can anyone offer any advice? thanks in advance
Click to expand...
Click to collapse
The good news is that the device probably isn't bricked. If it was unfixably bricked you shouldn't even see the boot animation.
It's figuring out how to fix it that's the hard part.
What you've clearly done as far as the ROM though is installed the rom improperly somehow. Might have missed as step in the process, or the ROM could have just been a bad download and no fault of your own. These things happen to the best of us.
Assuming that clockworkmod recovery is still installed, and you just can't get into it, you might try to see if you can access it using adb from your computer.
If you have abd installed boot the device as far as it'll go then see if you can connect to it with adb and run this command...
abd reboot recovery
Also try
adb reboot boot loader
If you don't have adb installed read this...
http://forum.xda-developers.com/showthread.php?t=1853159
If that doesn't work (and I only give it a 50-50 shot at best as adb isn't always useful during the boot process, which is where you are stuck....then we'll think of something else.
Also please describe the steps you are using to try and get into recovery just to make sure you're trying it the right way.
And after it gets stuck at the Samsung screen are you turning it off completely by holding the power, volume up, and volume down all at once? That should shut the device off completely, which is where you need to be before trying to boot into recovery.

Thank you both! ! I managed to get it going
Sent from my GT-P5113 using xda app-developers app

HulianMango said:
Thank you both! ! I managed to get it going
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
Please share how you got it fixed and what ended up working.
That way when someone else Google's the same probelm a year from now and finds this thread, he'll have the answer waiting for him. (See my signature cartoon from XKDC.com for a comical represensation of why not explaining what the outcome was is annoying)
Glad it got working!

Well i asked in the thread for that rom and it was suggested that the battery needed charging, I didnt think this was the case cuz my tab had been plugged in to the wall for about an hour already but I let it sit for a couple hours and it finally booted although it said there was 15% power left... its still charging really slow but it boots now!
Sent from my GT-P5113 using xda app-developers app

PLEASE HELP! Tablet shows black screen at startup and then hangs, no boot BRICKED

Hi thanks for reading, I will tell you as quick as I can
Basically I got this Allwinner A31 Tablet Q102 and wanted to root it and flash it when I got it, so I got it only a week ago, week ago from tommorow.
I managed to root it with VRoot and then attempted to install CWM because ROM Manager would say that it isnt supported. So after tons of research I took the method of rooting an Onda tablet which was to use the ADB. I got the Recovery.tar extracted the files inside it and then did the
adb push /data/recovery.img
And stuff like that
After I did all that it told me to hold the VOL+/POWER to enter CWM, I held it for like 1 minute until CWM showed and it was working. CWM version was 6.0.2.7 I think. So I was like oh ok its working now. So then I rebooted the system using the first option CWM gave me. After it turned off it didnt turn back on. So I turned it on manually and all I see is a blank BLACK screen. Thats it. It hangs and does nothing. Cant enter Recovery, safe mode, the USB is not recognized. Infact it doesnt even connect anymore.
If I hold the power button, it turns off then once I let go it turns back on doing the same thing.
Please help me as I only just got the Tablet and can't afford to lose it. Theres too many files I need to keep, only some were moved to the SD card.
4.4.2 KitKat

addy187a said:
Hi thanks for reading, I will tell you as quick as I can
Basically I got this Allwinner A31 Tablet Q102 and wanted to root it and flash it when I got it, so I got it only a week ago, week ago from tommorow.
I managed to root it with VRoot and then attempted to install CWM because ROM Manager would say that it isnt supported. So after tons of research I took the method of rooting an Onda tablet which was to use the ADB. I got the Recovery.tar extracted the files inside it and then did the
adb push /data/recovery.img
And stuff like that
After I did all that it told me to hold the VOL+/POWER to enter CWM, I held it for like 1 minute until CWM showed and it was working. CWM version was 6.0.2.7 I think. So I was like oh ok its working now. So then I rebooted the system using the first option CWM gave me. After it turned off it didnt turn back on. So I turned it on manually and all I see is a blank BLACK screen. Thats it. It hangs and does nothing. Cant enter Recovery, safe mode, the USB is not recognized. Infact it doesnt even connect anymore.
If I hold the power button, it turns off then once I let go it turns back on doing the same thing.
Please help me as I only just got the Tablet and can't afford to lose it. Theres too many files I need to keep, only some were moved to the SD card.
4.4.2 KitKat
Click to expand...
Click to collapse
So,Wrong discussion area...Anyway
You're still under warranty,why dont you just RMA it?
just dont tell them you're rooted or anything mess with softwares.

androidvillage said:
So,Wrong discussion area...Anyway
You're still under warranty,why dont you just RMA it?
just dont tell them you're rooted or anything mess with softwares.
Click to expand...
Click to collapse
Hi, thanks for the replay, the business wouldnt replace it but they offered to have a look, I know its bricked so there is no point sending it there. I hear you can fix it in Phoenix Suite but I cant find the firmware for it.
Btw what should it be in, I had trouble sorting it lol

addy187a said:
Hi, thanks for the replay, the business wouldnt replace it but they offered to have a look, I know its bricked so there is no point sending it there. I hear you can fix it in Phoenix Suite but I cant find the firmware for it.
Btw what should it be in, I had trouble sorting it lol
Click to expand...
Click to collapse
Ok but....what is the actual model of this thing?

androidvillage said:
Ok but....what is the actual model of this thing?
Click to expand...
Click to collapse
Took ages to find out, but its called an Allwinner Q102 something with YBC, Ive heard of a similar one called Allwinner A31s Yonestoptech and was also a Q102

Hey,
What's up with your tablet? I own the same model and was thinking about installing cyanogenmod, but I have no idea yet. Have you managed to figure something out, or found any way to repair it?
Cheers!

flash ??
Try to flash the stock ROM.......

Nah man, I can't do anything with it. Turn it on just a black screen. Holding the volume down button then pressing Tue power button a couple of times makes my computer detect the tablet. But nothing else.
I cannot enter CWM, after I flashed CWM it said Can't mount boot.IMG can't Mount this and that and then I restarted it and it happened.
SO DONT FLASH ANY CWM OR ROMS ON IT.
I really want the tablet fixed man. What the hell do I do?
Sent from my HTC One using XDA Free mobile app

Try this mate
slatedroid.com/topic/40623-aml-flash-tool-aka-imageburntool/
Sent from my GT-P5210 using XDA Free mobile app

@addy187a - Did you get it done?
I have the same problem.... - I installed successfully twrp, did a backup, wiped and tried to install another rom - failed. Now I am not able to boot into recovery - it is black, not recognized by the system (so I can't use imageburntool).
It starts, is black illuminated, nothing happens, only power is possible
my device: Fusion5 F5CS 32GB, Q102, 32GB
..no idea what to do...

Hey, I know I'm 1 year late to reply but I only just logged in to XDA since ages! I know right? Anyway, the way I fixed it was to download the firmware for the tablet which I found out by keeping a note about tablet model number (Settings> About device> Model) and spent a couple minutes searching for the firmware for it. Then I used Phoenix suite or just Phoenix can't remember what it was called to flash the tablet. There are plenty of YouTube videos and instructions on the web of how to use it, I can't remember how I did it as this was over a year and a half ago! It's as simple as that and words cannot describe how relieved I felt after reviving it. If an admin sees this, please close the thread. I'm still finding out how to use this site.