OK here goes.....
Turned my phone on and got "Process com.android.phone stopped unexpectedly. Try again." Clicked Force Stop as I couldn't get past it otherwise. Then got to the "Touch the android to begin". So touched the android and ...... nothing!! It just stayed on that screen. I can't get to any apps or settings and can only use the keypad to dial emergency numbers.
I searched the internet, as one does these days, and tried the touching all 4 corners of the screen to get around the android, and still nothing.
I've tried doing the reset and hard factory reset, taking the battery out and waiting, then putting it back and trying the reset again, but each time the phone reboots I get the "Process com ......" or "Touch the android...."
I'm not that au fait with Android and am finding it hard to understand much of what's being said on these forums (so much jargon and so many acronyms, it seems like you all were born knowing this stuff!!! ) that I'm sure the more things I'm trying the worse I'm making it!!
I can still get into Recovery and Download so I don't think I've messed up completely, but I'm so p!$$ed off with it now I just want to throw the phone down the toilet!!! So, pleeeeeze somebody, can you explain in absolute idiots language what I should do.
The phone is:
Samsung Galaxy Y Duos GT S6102 and it is rooted.
Any help would be appreciated.
What rom are you trying to flash?
Sent from my GT-S6102 using xda app-developers app
Aakashtitli said:
What rom are you trying to flash?
Sent from my GT-S6102 using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to flash any ROM. I just want to use my phone.
It was Gingerbread but I don't know which version or which version of Android.
As I said above, I just turned it on yesterday morning and I got the message about Process blah blah......! I wasn't trying to do anything else except turn it on as usual.
deleted
ckr1986 said:
This worked for me:
Clear data for the phone app and contacts , force stop and try again. (back up your contacts before clearing data cuz it wil be erased)
Click to expand...
Click to collapse
I'm sorry but I don't know what you mean.
are you able to reach the homescreen of your device?
http://forum.xda-developers.com/showthread.php?t=1990997
You can ask here if you dont understand something. I believe that your firmware in your phone got corrupted or the internal SD is bad/corrupted.
If its the former, good you can fix that with the above link. If not, then your phone is bust. Its not going to get fixed.
Lower end smatphones do have these types of issues, so if you do change your phone to something else, just visit alot of forums and make up your mind, at least you wont get suprised when you see others report problems. I hope that this could help.
ckr1986 said:
deleted
Click to expand...
Click to collapse
ckr1986 said:
are you able to reach the homescreen of your device?
Click to expand...
Click to collapse
I turn on the phone and the Samsung icon comes up with the jingle. After the vibrate, it goes to the black screen with the android with a message saying "Touch the android to begin". Below that are 2 options - Emergency call and change language.
After a few seconds a window comes saying "Process com.android.phone stopped unexpectedly. Try again". And below that is a button "Force Stop". If I press Force Stop, I get back to the first screen with the android and the message "Touch the android ..........". If I leave it at "Process com..............................." that's how it stays.
So to clarify - the only screen I get is the "Touch the android to begin". I cannot get any further.
I have tried the touching the 4 corners of the screen to bypass the android but nothing happens.
Alright ...guess the best bet for you is to reflash your stock rom (the software thats currently in your phone). You could check out the link that shadowcore posted above.
Sent from my SM-N9005 using Tapatalk
ckr1986 said:
Alright ...guess the best bet for you is to reflash your stock rom (the software thats currently in your phone). You could check out the link that shadowcore posted above.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
OK, so couldn't understand how to flash the rom suggested by shadowcore! Told you I needed an idiots guide!!!!
Anyway I downloaded stock firmware XXMA3 from samMobile. Opened it up in Odin 3, let it do its thing until Odin said PASS. But phone looped at reboot so I had to wipe data in Recovery thinking I would have to start all over again but.....voila!!!!
All sorted!!!!!
Thanks for your help anyways.
Glad to hear it all worked out !
Sent from my SM-N9005 using Tapatalk
Related
phone is on infused v2 and is now just looping after i restarted it, samsung samsung samsung.... how to fix this?
aviationmech406 said:
phone is on infused v2 and is now just looping after i restarted it, samsung samsung samsung.... how to fix this?
Click to expand...
Click to collapse
Have you tried anything to fix this......??
if not just pull batt, hold power and both volume up/down at the same time....when the first samsung logo appears let go of power and continue to hold till you get into recovery. should be like 10 sec maybe 15
wipe data factory reset and you should boot past the loop....if not you most likely have to reflash or use the ultimate unbrick.
mine did this when i deleted the lagfix folder by accident (trying to fee up space) i ended up booting into red recovery and disabling voodo lagfix, rebooted then went back in to recovery and re enabled it.
Im not able to get the recovery to come up, everything is jacked, im trying to track down instructions for that ultimate unbrick..
Ok found this http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick but the part where it says make sure your phone is com## in the odin, mine isnt showing up with that?
aviationmech406 said:
Im not able to get the recovery to come up, everything is jacked, im trying to track down instructions for that ultimate unbrick..
Ok found this http://forum.xda-developers.com/showthread.php?t=1116251&highlight=unbrick but the part where it says make sure your phone is com## in the odin, mine isnt showing up with that?
Click to expand...
Click to collapse
Did you get this working? When I was running Infused I had to repeatedly do battery pulls and the three button meth. to get the recovery. Should seriously try to get recovery to start before doing a back to stock.
As for Odin recognizing the phone, did you make sure you have the kies with the drivers installed, did you try different usb ports and/or computers caus sometimes the drivers act funky. Have seen other people have problems with Odin and the drivers.
Got odin to work and its back to stock, only problem i have now is when the date/time is set to automatic it sends it completely off the grid, i have to manually set it which i dont like to do, any quick fix to this?
I'm having a similar problem. My phone is bootlooping and my pc and odin are recognizing it, however the issue is that the phone only turns on for half a second before shutting back off, not allowing me to do anything with it. Anyone know of a way to fix this?
aviationmech406 said:
Got odin to work and its back to stock, only problem i have now is when the date/time is set to automatic it sends it completely off the grid, i have to manually set it which i dont like to do, any quick fix to this?
Click to expand...
Click to collapse
Even on stock? Ive seen this problem with custom roms like dlevrom 5.0 but not on stock? Cruise over there and see what he did to fix it. I believe there is a program called fastfix to force the locales to show up with North America. Nevertheless, check your locale and text in settings to make sure if the correct locale for your area is shown. If not there is a program in the market to force the correct one. Sorry, dont recall the programs name. Maybe the fastfix or fasterfix.
Sent from my SAMSUNG-SGH-I997 using XDA App
Astirnon said:
I'm having a similar problem. My phone is bootlooping and my pc and odin are recognizing it, however the issue is that the phone only turns on for half a second before shutting back off, not allowing me to do anything with it. Anyone know of a way to fix this?
Click to expand...
Click to collapse
Go to either the thread on the Heimdall one click back to stock or the thread on the Unbrickable mod, read up on your download mode access problem and figure which direction to go. Sounds like a soft brick but anything other than a black screen period is salvagable so your all good.
Sent from my SAMSUNG-SGH-I997 using XDA App
Pull battery plug in USB cable hold volume s power buttons insert battery should put you at download screen to odin to stock.
Sent from my SAMSUNG-SGH-I997 using XDA App
JLR9914 said:
Go to either the thread on the Heimdall one click back to stock or the thread on the Unbrickable mod, read up on your download mode access problem and figure which direction to go. Sounds like a soft brick but anything other than a black screen period is salvagable so your all good.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Ok I did both, Odin had a different "modem" I guess so my time was off, I tried the heimdall one and it gave me the gingerbread update which is nice but im having a problem I turn on phone after and after the Samsung comes on it does this sketchy screen with a lot of colors then boots into "atts rethink possible" not sure if anyone can help with that.
aviationmech406 said:
Ok I did both, Odin had a different "modem" I guess so my time was off, I tried the heimdall one and it gave me the gingerbread update which is nice but im having a problem I turn on phone after and after the Samsung comes on it does this sketchy screen with a lot of colors then boots into "atts rethink possible" not sure if anyone can help with that.
Click to expand...
Click to collapse
Sounds like the rainbow thing peeps were getting when they used gb leaks with the froyo bootloaders? You are still booting up fine so that is good. Head over to one of the leaks like UCKJ2 or 4 and study first because the gb bootloaders might solve your rainbow but they are to be used with caution, you could brick your phone real quick.
Sent from my SAMSUNG-SGH-I997 using XDA App
So I'm completely new at this stuff and I followed this guide (http://forum.xda-developers.com/showthread.php?t=1470716). I got to the point where I had a custom ROM (Valhalla Black Edition) and it was working,but I decided I didn't like Valhalla Black Edition and I wanted to go back. So I went to CWM and selected backup and restore, selected my backup that I backed up earlier. It all seemed to work but now my phone is stuck at the boot screen. Any help would be greatly appreciated and sorry if I come across as a noob, it's because I actually am a noob.
Ur pretty screwed this point
Responded to your post in the other thread. Earlier versions of CWM had issues restoring on different versions of CWM than the back up was made from.
Hi. In the recovery menu try a full wipe before restoring the rom: wipe system, wipe cache, wipe dalvik cache.
Sent from my GT-I9300 using xda app-developers app
Taiwan671 said:
Ur pretty screwed this point
Click to expand...
Click to collapse
You should NOT be giving any advice!
@Fridge.....just flash back to stock using heimdal or Odin ....you will be just fine
I was just about to reply to that, but then i saw your post.
Sent from my SGH-T959V using xda premium
lumin30 said:
Responded to your post in the other thread. Earlier versions of CWM had issues restoring on different versions of CWM than the back up was made from.
Click to expand...
Click to collapse
Hey lumin, i understand u have some experience with the SGS4G, so i want to know if i can "revive" my phone, last night i was trying to restore a bad flash with odin but just before the bar fills to 100% it says "failed" now the phone does not turns on, even trying the battery out, volume buttons hold down, connect to pc and putting battery back. I hope you can help me, because i don't know what to do. I apologize for my bad english, it is not my native language.
Lacryma said:
Hey lumin, i understand u have some experience with the SGS4G, so i want to know if i can "revive" my phone, last night i was trying to restore a bad flash with odin but just before the bar fills to 100% it says "failed" now the phone does not turns on, even trying the battery out, volume buttons hold down, connect to pc and putting battery back. I hope you can help me, because i don't know what to do. I apologize for my bad english, it is not my native language.
Click to expand...
Click to collapse
What where you flashing with odin? First thing I would check is to make sure your battery has charge. These phones are really hard to brick but it can happen.
When you insert battery, does the computer see the phone? Sometimes, even with the black screen, you are still in dl mode.
Sent from my SGH-T959V using xda app-developers app
hechoen said:
What where you flashing with odin? First thing I would check is to make sure your battery has charge. These phones are really hard to brick but it can happen.
Click to expand...
Click to collapse
The stock rom, i was trying to flash the 2e recovery, but it was bad because after the recovery the phone was saying it was another galaxy s model, i can't remember t9000 whatever... after that, the screen was buggy ( various colors in the screen), and finally decided to go back to stock, the process was almost complete but before it finish says failed! so i disconnect the phone and restart it, and it did not turn on.
Thanks for the reply, i will try to recharge the battery and see if the pc recognizes.
---------- Post added at 11:06 AM ---------- Previous post was at 10:54 AM ----------
champ1919 said:
When you insert battery, does the computer see the phone? Sometimes, even with the black screen, you are still in dl mode.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I can not tell ,will try that after charge battery, thanks.
but it was bad because after the recovery the phone was saying it was another galaxy s model, i can't remember t9000 whatever... after that, the screen was buggy ( various colors in the screen), and finally decided to go back to stock, the process was almost complete but before it finish says failed! so i disconnect the phone and restart it, and it did not turn on.
Wish you luck. Sounds like wrong firmware. If you have the sgs4g, use the link from first post and try the one click.
Sent from my SGH-T959V using xda app-developers app
champ1919 said:
but it was bad because after the recovery the phone was saying it was another galaxy s model, i can't remember t9000 whatever... after that, the screen was buggy ( various colors in the screen), and finally decided to go back to stock, the process was almost complete but before it finish says failed! so i disconnect the phone and restart it, and it did not turn on.
Wish you luck. Sounds like wrong firmware. If you have the sgs4g, use the link from first post and try the one click.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Ok, I just did that, and the phone does not apear connected in the comand prompt and in Heimdall, what can i do?
Thanks in advance!
All,
Hopefully this is an easy one. I looked through the board and did not see anything I haven't similar but i can be wrong. Quick background, I rebooted the phone it looked normal on shutdown but it never came back up.. What I have tried is tremove the battery and left it for day and tried to turn on with no luck. A couple of times it showed the battery indicator but would go black screen if i tried to turn it on. I have reloaded the stock rom using ODIN still no luck. The only thing I can make it do is go to the download screen, that's it. This is a stock ATT Skyrocket no mods or anything. It seems to be a software issue but I do not know how to fix it. Any Ideas Thanks
oops!
l33t_killa said:
I'm in the same boat. Root was a confirmed success after the OTA update, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), the Samsung logo comes up before this and it's all that it does now. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. PLEASE HELP.......
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
Click to expand...
Click to collapse
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
xcrazydx said:
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
Click to expand...
Click to collapse
Didn't notice that....
l33t_killa said:
Didn't notice that....
Click to expand...
Click to collapse
Glad I caught it before you bricked using our files. Good luck!
Sent from my GT-P5113 using Tapatalk 4
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.
Bought this phone and didn't like it. Felt like my G3 was a better phone, so I went and bought myself the Note 5. Anyways....
I backed up everything from my G4 and did Factory reset. Now when I try to setup the phone, I complete the last step and I'm greeted with the "Unfortunately, LGSetupWizard has stopped" Message and then it returns to the first setup (choose language) screen. Just happens over and over. I just have this phone and don't know what to do. I really don't want to flash the PR stock file to my phone. Does anyone know of a solution or some sort of setup bypass?
Thanks in advance
do a hard reset, turn off the device, then hold volume down and press the power button until the lg logo comes up, release the power button and immediately press it again until you boot into the factory reset. Keep the volume down button pressed continuously until the factory reset screen comes up.
Yea, I tried that a while back but still the same problem...
tyiphius said:
Yea, I tried that a while back but still the same problem...
Click to expand...
Click to collapse
Did you root before? replaced some app to system? I have this problem before cause of deodex home..but still can access it..
If you can reach wifi setting after start screen, try to pull status bar down...then go to setting>home screen>select home..
My advice is you have to reflash stock image but the problem will be MTP mode..
download sg usb mass storage enabler for access storage via pc..
Yes the phone was rooted.
I don't think I debloated by removing system apps. I think my problem might have came from using the debloated tool by gatesjunior. Though nothing of it when I reset the phone. If disabling the apps wasn't the problem then I guess I did go delete system apps.
But if I deleted Setupwizard, I wouldn't have the setup at all correct?
tyiphius said:
Yes the phone was rooted.
I don't think I debloated by removing system apps. I think my problem might have came from using the debloated tool by gatesjunior. Though nothing of it when I reset the phone. If disabling the apps wasn't the problem then I guess I did go delete system apps.
But if I deleted Setupwizard, I wouldn't have the setup at all correct?
Click to expand...
Click to collapse
Its still has setup UI, because before this i've froze those app ..
try go to setting and select home 1st...from my previous comment
faizalotai said:
Its still has setup UI, because before this i've froze those app ..
try go to setting and select home 1st...from my previous comment
Click to expand...
Click to collapse
Still nothing. I brought it to a ATT device support center and they'd replace it but there was non in stock, so ATT will send me one in 4 bussiness days.
The device center will swap out the phone if they can't fix it and once its under its 1yr manufacture warranty. You don't ATT mobile insurance either. I had my Note 4 swapped out by them in store before.
You should just have to reflash the system img and it would work.
Sent from my LG-H810 using XDA Free mobile app
I had this problem too.. Couldn't find an answer short of flashing it to PR... After a loooooong time on the phone with AT&T tech support, finally did an RMA... Send the other one back this morning, I hope it doesn't come back and bite me later bc it was rooted.
I had serious thoughts of flashing an international system image to it so it could brick. But couldn't bring myself to do it...
I would however like to know what I did to get that.. I did just like the OP and did a simple factory reset. I did delete a few things from system manually, but that was mainly att stuff and Google books, magazines etc. I haven't rooted the new one yet bc now I'm skeptical on doing anything with this damn phone.
Sent from my LG-H810 using XDA Free mobile app
It happened because system cannot access lg setup wizard apk, either its been delete or froze.
What do l do when my LG70 is showing unfortunately LGSetupWizard has stopped