Database Info

[Q] NOWAY!!! Bricked again??

I recovered my tab from a soft brick a couple of days ago http://forum.xda-developers.com/showthread.php?t=1995876 by flashing stock HC with Odin and then flashed SkyHigh. Did the Odin flash, then flashed SkyHigh via CWM, wiped everything, re-flashed SkyHigh, then ICS gapps and everything seemed ok... Then just now it did the exact same thing it did last time and it froze and would get stuck at the "Galaxy Tab 7.7" screen. I can boot into CWM but it won't let me wipe or install anything.
Which firmware should I use to bring it back? People said HC before, but what's the difference between that and flashing straight into ICS?
Does anyone have any idea what it could be? I wipe data, cache and dalvik everytime I flash. Am I wiping something I shouldn't, wrong procedure or do I need to send the tab back?
Thanks!

Looks like you are still getting partition corruption........
If you just flash back to stock for a while and see what happens over the next week? If it continues, I would return for repair....
But for me:
If CWM recovery isn't working.....
1st, I would try;
1. Reflash CWM recovery with Odin (don't boot)
2. Power off
3. Immediately flash SkyHigh ROM (flash ROM will also auto wipe cache and dalvik)
2nd, I would try;
1. Flash any stock ICS for your device model with Odin (DO NOT WIPE ANYTHING yet)
2. Flash CWM recovery
3. Flash v3.5
4. Boot.......
5. Recovery - factory reset and immediately,
6. Flash SkyHigh ROM
7. Reboot
Sent from my GT-I9300 using xda premium

you should avoid using any custom rom in the meantime to observe the condition of your device
I suggest that you first flash HC then wipe your system completely from there before flashing ICS
avoid wiping your system if you have stock ICS since this may completely fry your EMMC

Thanks. I tried both, no luck. The flashing process is fine, but then I always get stuck at the Tab 7.7 screen. I can boot in download mode and CWM still, but when I try to flash SkyHigh the Aroma installer either freezes or reboots to the screen of doom.
What state should I leave the tab in if I'm going to send it to Sammy? Also I travel a lot so I bought it in Australia on ebay, it was a Singaporean import covered by 3rd party warranty but the seller is no longer in business! And I'm nowhere near Sin or Oz... I will be in KL, Malaysia and Manila for a few days though, how are the service centres there? Will they take it in or refuse it because of the country of purchase?
Anything else I could try now or do I just risk aggravating the situation?

JAYZE said:
you should avoid using any custom rom in the meantime to observe the condition of your device
we suggest that you first flash HC then wipe your system completely from there before flashing ICS
avoid wiping your system if you have stock ICS since this may completely fry your EMMC
Click to expand...
Click to collapse
There is no "we". It doesn't matter HC or ICS. Both can be susceptible to the brick bug......
Just don't factory reset in CWM with stock. That's why I gave a few suggestions/methods to try
Sent from my GT-I9300 using xda premium

iena said:
Thanks. I tried both, no luck. The flashing process is fine, but then I always get stuck at the Tab 7.7 screen. I can boot in download mode and CWM still, but when I try to flash SkyHigh the Aroma installer either freezes or reboots to the screen of doom.
What state should I leave the tab in if I'm going to send it to Sammy? Also I travel a lot so I bought it in Australia on ebay, it was a Singaporean import covered by 3rd party warranty but the seller is no longer in business! And I'm nowhere near Sin or Oz... I will be in KL, Malaysia and Manila for a few days though, how are the service centres there? Will they take it in or refuse it because of the country of purchase?
Anything else I could try now or do I just risk aggravating the situation?
Click to expand...
Click to collapse
based on your previous thread you managed to flashed HC then fixed the bootloop by forcing it into recovery mode and doing a wipe from there..you should leave it at that state if your turn it in for service..or flash ICS if you want, just don't send it with custom firmware because it will definitely void your warranty

iena said:
Thanks. I tried both, no luck. The flashing process is fine, but then I always get stuck at the Tab 7.7 screen. I can boot in download mode and CWM still, but when I try to flash SkyHigh the Aroma installer either freezes or reboots to the screen of doom.
What state should I leave the tab in if I'm going to send it to Sammy? Also I travel a lot so I bought it in Australia on ebay, it was a Singaporean import covered by 3rd party warranty but the seller is no longer in business! And I'm nowhere near Sin or Oz... I will be in KL, Malaysia and Manila for a few days though, how are the service centres there? Will they take it in or refuse it because of the country of purchase?
Anything else I could try now or do I just risk aggravating the situation?
Click to expand...
Click to collapse
I'm not totally sure if your device has ever actually booted with SkyHigh or not?
If not;
Have you checked the md5 checksum found in Dev-host download link to ensure your download is not corrupted?
If you need to send for repair, ensure the device is stock and all root app / evidence is removed.
Sorry, can't help with the warranty issue,
But as suggested a couple of times, that you use the device in complete stock (no root or CWM) for a while and see what happens.....
Sent from my GT-I9300 using xda premium

It did boot and I ran SkyHigh for 2 days from shortly after recovery to the second brick.
Will it make any difference if it has CWM recovery when I return it? If yes, I guess I'll just flash HC with Odin and send it back...
Has anyone had any experience with returning a bricked device with corrupted partitions?

iena said:
It did boot and I ran SkyHigh for 2 days from shortly after recovery to the second brick.
Will it make any difference if it has CWM recovery when I return it? If yes, I guess I'll just flash HC with Odin and send it back...
Has anyone had any experience with returning a bricked device with corrupted partitions?
Click to expand...
Click to collapse
recovery should also be stock so i recommend a complete flash via odin
here in manila we could directly send a device at any service center as long as it is covered by warranty..given that you also bought the device locally
i am not sure about those that were bought online like yours

UPDATE: I Odin flashed P6800DXLB3 and left it there to die a slow death at the 7.7 screen since I have no way of switching it off. Than after over 30 mins it the glowing Samsung screen appeared and then the boot animation, but it now loops between these two.
Is it a bad or good thing?

iena said:
UPDATE: I Odin flashed P6800DXLB3 and left it there to die a slow death at the 7.7 screen since I have no way of switching it off. Than after over 30 mins it the glowing Samsung screen appeared and then the boot animation, but it now loops between these two.
Is it a bad or good thing?
Click to expand...
Click to collapse
Hold the power button down continuously for 10 seconds to "force" power off.
Letting it "die" may possibly damage your battery permanently
Take it to the service center, because even if you get it going, most likely the corrupt partition will cause problems again soon enough........
Sent from my GT-I9300 using xda premium

Actually when I do that it restarts it, it doesn't switch it off.
In the end I managed to boot it into stock recovery after flashing stock HC P6800DXLB3, wiped everything and this time it booted up. I rebooted a couple of times to make sure it worked and then flashed stock ICS P6800XXLQ1. I'll keep it this way for a few days and see what happens, then in the meanwhile liaise with Sammy cust support to decide what to do.
So if anyone is having the same problem, all I did was flash P6800DXLB3, wait A LONG TIME till it would go into bootloop at animation screen, stock recovery (power + vol up), wiped data + cache, rebooted.
Two questions:
- Why when on stock it is ok to wipe in stock recovery but not in CWM?
- If they ask me what I've been doing with my tab, can I mention flashing official, unrooted firmwares via ODIN, or will they not cover that on warranty?
Thanks for all the help so far.

iena said:
Actually when I do that it restarts it, it doesn't switch it off.
In the end I managed to boot it into stock recovery after flashing stock HC P6800DXLB3, wiped everything and this time it booted up. I rebooted a couple of times to make sure it worked and then flashed stock ICS P6800XXLQ1. I'll keep it this way for a few days and see what happens, then in the meanwhile liaise with Sammy cust support to decide what to do.
So if anyone is having the same problem, all I did was flash P6800DXLB3, wait A LONG TIME till it would go into bootloop at animation screen, stock recovery (power + vol up), wiped data + cache, rebooted.
Two questions:
- Why when on stock it is ok to wipe in stock recovery but not in CWM?
- If they ask me what I've been doing with my tab, can I mention flashing official, unrooted firmwares via ODIN, or will they not cover that on warranty?
Thanks for all the help so far.
Click to expand...
Click to collapse
Stock recovery uses a different protocol for erasing/formatting then CWM.
The CWM one is faster but it can fry your memory chip.
Samsung says the stock recovery is safe.
Don't tell the service center that you have been flashing using odin, just tell them you upgraded in Kies and then it failed to boot.

Please help, Samsung Stellar

Okay i rooted my Samsung stellar everything went okay, and the way i rooted it was with a S3 root, so i wanted to back up my rom to play around so i downloaded room manger, i didn't see my device supported for the clockworkmod so i downloaded a s3 one, after that, it went into recovery boating, it went into a loop, and when it finally turnt on MY TOUCHSCREEN AND SOFTKEYS WONT WORK, so i went home and just turnt my phone back to stock. still wont work. i factory reset so now my usb debugging is off. should i just start looking at a new phone? i have no warnty

kirkwoodlucas said:
Okay i rooted my Samsung stellar everything went okay, and the way i rooted it was with a S3 root, so i wanted to back up my rom to play around so i downloaded room manger, i didn't see my device supported for the clockworkmod so i downloaded a s3 one, after that, it went into recovery boating, it went into a loop, and when it finally turnt on MY TOUCHSCREEN AND SOFTKEYS WONT WORK, so i went home and just turnt my phone back to stock. still wont work. i factory reset so now my usb debugging is off. should i just start looking at a new phone? i have no warnty
Click to expand...
Click to collapse
Have you tried flashing your stock firmware? Look on sammobile.com for it, and flash it with Odin.
Послато са GT-I9070 користећи Тапаток 2

shut_down said:
Have you tried flashing your stock firmware? Look on sammobile.com for it, and flash it with Odin.
Послато са GT-I9070 користећи Тапаток 2
Click to expand...
Click to collapse
i tried all that and like a fool when it was stock it still wouldnt work so i reset it, and i cant turn usb bebugging on becuz i cant use it at all, everything works but the screen and softkeys, its stock now so i dont have anyway of doing that do i?

kirkwoodlucas said:
i tried all that and like a fool when it was stock it still wouldnt work so i reset it, and i cant turn usb bebugging on becuz i cant use it at all, everything works but the screen and softkeys, its stock now so i dont have anyway of doing that do i?
Click to expand...
Click to collapse
As I know you do not. And how about you take it to some service? You will pay some money, but they could fix it. Than you do not need to buy new phone. I do not know how much that phone worth, because I do not have it im my country.

Me too
kirkwoodlucas said:
Okay i rooted my Samsung stellar everything went okay, and the way i rooted it was with a S3 root, so i wanted to back up my rom to play around so i downloaded room manger, i didn't see my device supported for the clockworkmod so i downloaded a s3 one, after that, it went into recovery boating, it went into a loop, and when it finally turnt on MY TOUCHSCREEN AND SOFTKEYS WONT WORK, so i went home and just turnt my phone back to stock. still wont work. i factory reset so now my usb debugging is off. should i just start looking at a new phone? i have no warnty
Click to expand...
Click to collapse
Had literally the exact same thing happen. I got into recovery and did a factory reset then took it to verizon and they replaced it haha
http://www.androidfilehost.com/?a=show&w=files&flid=1311
here's a link for the rom I use flashed with goo manager

Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update

Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!

I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app

wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse

beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:

error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse

beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??

mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.

beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!

This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse

I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...

Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app

I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse

So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..

Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app

I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.

Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse

Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?

update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.

There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.

Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.

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.

Firmware upgrade encountered an issue.

I have a galaxy tab 2 GT-P3113.
Currently it will not do much of anything. I have not touched it in months but decided to try again.
In the past I have flashed many roms and kernels on it and even dual booted it at one point.
It became unstable and slow so I put it back to stock firmware. However it was still very slow and unresponsive like an old XP pc.
I don't remember exactly what I was doing but I assume I tried to reflash the stock firmware again via kies and since then it has been basically bricked.
If it does power on it says 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.'
Well I tried kies and get device not responding. When I plug it in to odin it lights up yellow and if I remember correctly it should be green. However I cannot even get it into download mode to use odin. I am afraid I have completely bricked it. Does anyone have any suggestions?

jesusfreakjacob said:
I have a galaxy tab 2 GT-P3113.
Currently it will not do much of anything. I have not touched it in months but decided to try again.
In the past I have flashed many roms and kernels on it and even dual booted it at one point.
It became unstable and slow so I put it back to stock firmware. However it was still very slow and unresponsive like an old XP pc.
I don't remember exactly what I was doing but I assume I tried to reflash the stock firmware again via kies and since then it has been basically bricked.
If it does power on it says 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.'
Well I tried kies and get device not responding. When I plug it in to odin it lights up yellow and if I remember correctly it should be green. However I cannot even get it into download mode to use odin. I am afraid I have completely bricked it. Does anyone have any suggestions?
Click to expand...
Click to collapse
If you can't get into download mode then there is no way to fix it without jtag
Sent from my GT-P3100 using Tapatalk

shsagnik said:
If you can't get into download mode then there is no way to fix it without jtag
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
well jtag is the one thing I have zero experience with? Do you know anything about it?