Database Info

[Fix] Battery 0% fix [fix]

maby this works :
1.go to CWM (without charger)
let drain your battery
when your mobile is out of battery try to get him back on Cwm
3. And wait again when it gets off.
4.
when he is complete out of battery plug in the wall.
5.
then try to get your phone on in CWM
restore rom stock .................
5. maby your phone shutdown don't worry...
6. wait and get your phone on
do another rom restore
with all fixes and wipes
when you done start up phone and your ready to charge wait to 100% then its fix
by my is it working
Stock gb rom
Root
Cwm
Sorry for my english
Damage on your phone is not my thing
Not responsible of any damage
hope it works
Sent from my LG-P920 using XDA App

does it work for you ? what rom did you restore ?

my english is poor too.... and i don't understand anything...
can someone test it and explain??

It works for me wait a second i made a new version
Sent from my LG-P920 using XDA App

Okeej the edit is online hope its work for you too guys ..
Sent from my LG-P920 using XDA App

what do you mean ''
6. wait and get your phone on
do another rom restore
with all fixes and wipes
''
what fixes did you did after stock restore ??

First restore than your wipe everything .. than restore again
Sent from my LG-P920 using XDA App

didnt work. thanks anyways

Okeej your welcome iam sorry
Sent from my LG-P920 using XDA App

have same situation here & i ve serche and spent too many houers to find solution but nothing
plz som1 post right stepls to fix this problem

llcoolr said:
have same situation here & i ve serche and spent too many houers to find solution but nothing
plz som1 post right stepls to fix this problem
Click to expand...
Click to collapse
I found something frome paultje162
First download Thaiz O3D Stock 2.7.1
And make sure you are rooted and have CWM
let it on the charger for about 2 hours.
go into CWM
Wipe data
Wipe cache
Advanced settings:
wipe battery stats
wipe dalvik
go back
Mounts and Storage:
format system
go back
Install zip from sdcard
Choose zip
Flash thaiz O3d 2.7.1
reboot
wipe battery stats again
flash thaiz O3d 2.7.1
and reboot
now let it sit on the charger for about 24 hours. after that. you will see you magically have 30% battery.
unplug it. plug it. and it charges fast again
........
Thats a post of him hope it works
Sent from my LG-P920 using XDA

It worked for me. so it should do the trick.
and if it doesnt.
you can put your phone into download mode to restore it to stock.
just unplug battery. hold power and vol up
put in usb cord
put in battery
and let LG mobile update restore it.
remember, you need to take your own KDZ and flash it manually.
like you always restore your phone.
if i'm not wrong it shouldnt ask for charging your battery first.

So, I thought I'd add my experience to this.
I'd been having the same problem with the 0% battery thing since I bought the phone off Ebay.
I tried wiping and flashing rom etc, and it didn't work.
I recently got the battery expansion cover and the larger battery.
One night, I'd had a couple beers and dropped the phone on the floor. The back case flew off and the battery flew out as well. I replaced the battery and replaced the case and turned the phone on.
What do you know, the battery problem was fixed and hasn't returned.
Strange.

everbret said:
So, I thought I'd add my experience to this.
I'd been having the same problem with the 0% battery thing since I bought the phone off Ebay.
I tried wiping and flashing rom etc, and it didn't work.
I recently got the battery expansion cover and the larger battery.
One night, I'd had a couple beers and dropped the phone on the floor. The back case flew off and the battery flew out as well. I replaced the battery and replaced the case and turned the phone on.
What do you know, the battery problem was fixed and hasn't returned.
Strange.
Click to expand...
Click to collapse
HEH HEH !!!
Now we have a solution!!
try at your own risk!!
schubeir

[Q] Galaxy ace s5830 boots only when charging

There are 2 problems
First it shows charging even when I disconnect the charger/USB cable.
Second it is booting only when I am charging, else there is no reaction even if I press the power button forever long.
Other things worth mentioning
It is also not going into recovery mode. It is going into only RAM dump mode.
It is booting only if I press the power button when the battery shows up on the screen while charging when it is off.
Most of the problems I noticed when I removed superuser permissions from all apps.(Actually there were only 2 apps proxydroid and superuser itself in the list)
The phone was rooted android 2.3.7.
I then hard reset it. It is now 2.3.6.
when phone is on it shows charging forever once I start the charging.

Now I was able go into recovery mode when charging.
So I loaded cyanogenmod 7.2 official stable version. But still the battery problem is there

puneetsays123 said:
Now I was able go into recovery mode when charging.
So I loaded cyanogenmod 7.2 official stable version. But still the battery problem is there
Click to expand...
Click to collapse
Try a factory reset once.. Also on recovery mode clear cache n dalvik cache..
Sent from my fingers to your face using xda premium.!

I have tried both also the battery wipe. No use doing it

puneetsays123 said:
I have tried both also the battery wipe. No use doing it
Click to expand...
Click to collapse
Then I guess it is a hardware problem.. Do show it in Samsung Service center..
However you can once try to use some custom ROM and see if the problem persists.. Or re flash your firmware..
Sent from my fingers to your face using xda premium.!

I have the same problem

[Q] My Tab 7 Plus is possibly hard bricked after JB ROM flash

I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?

what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....

Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now

I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?

yes, also a faulty or non-OEM cable would be the culprit.

SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.

This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...

Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app

[Q] AT&T bootloop or suddent reboot

Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.

jakov.90 said:
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
Click to expand...
Click to collapse
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599

qkster said:
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
Click to expand...
Click to collapse
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.

jakov.90 said:
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
Click to expand...
Click to collapse
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.

qkster said:
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
Click to expand...
Click to collapse
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time

post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13

qkster said:
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
Click to expand...
Click to collapse
Thank you, the post its the number #122

jakov.90 said:
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
Click to expand...
Click to collapse
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Hey thanks, that was very useful.. i risky miself to do a stock flrom flashing with pit checking the Nand erase all option in Odin 3.07, and the random reboots are gone :laugh:. Now i have one question, Do i need an special kernel for JB 4.2.2? i plan to flash the Carbon-jb-v1.6 rom but i dont know if i need another kernel

I'm glad to hear you solved your issue.
For JB, use the kernel provided with the rom.
Sent from my SAMSUNG-SGH-I997 using xda premium

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.