Hey guys,
Yesterday my Galaxy R (GT-I9103) was stuck at the BootUp screen (the Samsung and Galaxy R screen).
I googled around and found the "booting recovery" method. I got to the menu without Problems (Pwr + VolUp + Home) and used the "wipe cache" function. After rebooting the device I was stuck again on the Samsung logo.
Okay, back to the "booting recovery" for the factory reset. After the automatic reboot, guess what, Samsung logo again. After waiting for a while I restartet the device again and tried to enter the "booting recover". But instead of getting into the recovery mode I only get a message with "deleting cryption meta data".
So I searched and searched read threads and threads with similar issues but didn't quite find the right answer. So I decided to flash the phone and install the stock rom to the phone.
I found a pretty nice thread in your forums and the flash worked without problems:
here is what i used:
Odin3-v1.85
I9103XWLA4_I9103DRELA1_DRE.tar.md5 <- stock rom for Austria
Superuser-3.2-RC3-arm-signed
After installing the new stock rom the device rebootet and I got stock at the Samsung logo again and the "deleting cryption meta data" message still appears.
then I installed the Superuser which made difference.
Can you give me some advice how to proceed? I stumbled over the Galaxy R - Dead Repair, but since i had no chance to backup my /efs folder i didnt want to try this method.
This is a very interesting issue! I have never encountered that message. You can take EFS backup if you are in CWM as it has adb running by default (I have thought of risky situations.). Have you ever flashed ICS?
Sent from my CM10-powered GT-I9103
Adam he had flashed gb rom coz he had used i9103_xwla4.. File
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
Adam he had flashed gb rom coz he had used i9103_xwla4.. File
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
I know that XWLA4 is GB. I just asked if he has flashed ICS ever.
Sent from my CM10-powered GT-I9103
have you encrypted your device when you are using ICS if so then flash ICS again it should work....
I was stuck at the same issue couple of weeks ago. I managed to recover with a cwm backup of ics.
But had issues with reboot, stuck at Samsung splash screen, went to ssc as I had just a fortnight of warranty left. My motherboard was changed. All is well now. You can try and experiment to recover if you have breather time till warranty expires. Else take to ssc.
Sent from my GT-I9103 using xda app-developers app
Hey guys,
sorry for the late reply but was pretty busy over the holidays .
I finally brought the phone back to life .
Actually it wasn't a big deal. Just flashed a new Kernel (some Aradat Version, dont know the exact number but I can check when I'm back on my other PC).
After flashing the new kernel the phone booted without further problems.
Great to hear that buddy.. Do change the title to [solved] so that if someone has a similar problem they'll be able to find the fix
From my CM10.1 powered galaxy R
vbz89 said:
Great to hear that buddy.. Do change the title to [solved] so that if someone has a similar problem they'll be able to find the fix
From my CM10.1 powered galaxy R
Click to expand...
Click to collapse
I'd love to, but I just can edit the post itself and not the title
Pretty sure there's a superobvious button I was missing but i didnt find it ...
Related
I bought a g2x of a friend and it worked fine and all of the sudden i got stuck on a boot loop
PLease help
Should of used nvflash method. The did you use rom manager?
Sent from my LG-P999 using Tapatalk
def need more info if u want help theres a bunch of reasons y that could of happened
I havent rooted or anything it just started doung it..I took the battery out and i still get the lg boot screen over and over.
ur gona have to install recovery wiyh nvflash use the updated one 5/19 n then u can find the stock image place it on sdcard n flash u should be good after that
its all in development search is ur buddy
Mine did the same, you're going to have to hard reset your device. Power off device then power on and hold power btn & vol. up together.
Sent from my LG-P999 using Tapatalk
Thanks for all your help guys i got it fix with the nvflash
Having the same ReBoot issue but my problem was caused after being rooted then installed Rom mang but when i installed recovery i picked the wrong phone instead of the G2x by Tmobile i picked the OP Gx2 can someone please help still stuck in reloop mode!
Ive been using the thread to Odin back to stock as im getting a replacement phone in a few days. Followed everything correctly, but Ive been getting a boot loop between the green android guy and the white Samsung startup logos. Redid the process in odin and now im getting "firmware upgrade encountered an issue, please select recovery mode in Kies and try again" when I go to download mode. i know I have a saved Nandroid backup on my SDcard, I just cant get to it. I also have mini Kies installed on my computer if there is a way to fix it thru that. I cant figure out how to get into recovery mode either. If anyone can help it would be greatly appreciated! Im just trying to get my phone working until my replacement is here.
I did Odin again, but now im stuck in a boot loop between the greenm android guy and the white samsung startup screens.
itsLYNDZ said:
Ive been using the thread to Odin back to stock as im getting a replacement phone in a few days. Followed everything correctly, but Ive been getting a boot loop between the green android guy and the white Samsung startup logos. Redid the process in odin and now im getting "firmware upgrade encountered an issue, please select recovery mode in Kies and try again" when I go to download mode. i know I have a saved Nandroid backup on my SDcard, I just cant get to it. I also have mini Kies installed on my computer if there is a way to fix it thru that. I cant figure out how to get into recovery mode either. If anyone can help it would be greatly appreciated! Im just trying to get my phone working until my replacement is here.
I did Odin again, but now im stuck in a boot loop between the greenm android guy and the white samsung startup screens.
Click to expand...
Click to collapse
That's because you had to factory reset and erase all data before flashing to stock. I had the same issue when flashing from dk4 to stock to lf4
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
So how do I get my phone working again? Its stuck in a bootloop after following the directions for Odin back to stock thread
itsLYNDZ said:
Ive been using the thread to Odin back to stock as im getting a replacement phone in a few days. Followed everything correctly, but Ive been getting a boot loop between the green android guy and the white Samsung startup logos. Redid the process in odin and now im getting "firmware upgrade encountered an issue, please select recovery mode in Kies and try again" when I go to download mode. i know I have a saved Nandroid backup on my SDcard, I just cant get to it. I also have mini Kies installed on my computer if there is a way to fix it thru that. I cant figure out how to get into recovery mode either. If anyone can help it would be greatly appreciated! Im just trying to get my phone working until my replacement is here.
I did Odin again, but now im stuck in a boot loop between the greenm android guy and the white samsung startup screens.
Click to expand...
Click to collapse
This issue only occured when you uncheck Auto reboot in Odin. Try Odin again with Auto reboot checked
If you getting an boot loop, do exactly what I've done in Odin thread
If you get a boot loop All you do is boot in stock recovery and wipe data
Sent from my SGH-T769 using xda premium
snoopy1e11 said:
If you get a boot loop All you do is boot in stock recovery and wipe data
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
Can't go to stock recovery in this case. This issue only occoured when Odin to stock ROM after using/flashing custom ROM that you forgot to format system or clean data. I've run into this problem before
It looks like after all this, Titanium Backup's backup was erased. I do have a Nandroid saved on my SDcard. Is there a way to pull everything from that? When I go to CWM and try to do a Nandroid, it says there isnt anything there. But When I connect to my computer, I can see the saved backup. I have been able to pull a few backed up apps off the Nandroid backup, but only certain ones or it says batch restore failed. Im wonder how it can see the Nandroids, but CWM cant? They're saved on my SDcard.
Is there another way Titanium Backup saves backups that I could possibly get to them? Im really trying to figure this out before my replacement phone gets here in a few days. I did backup everything, Im just having a difficult time restoring after the numerous problems Ive had thanks to Tmobile's "troubleshooting"
What are you currently running? If you are back to stock titanium won't function correctly as you have to be rooted. But since you mentioned cwm I wasn't sure.
Sent from my SGH-T769 using Tapatalk 2
Im just on stock but I am rooted. I just dont know where all my backups went after the bootloop and issues with reverting to stock after Tmobilr screwed up my phone trying to figure out why I kept getting "Call Ended" when trying to dial out.
Where is your nandroid backup currently located?
Sent from my SGH-T769 using Tapatalk 2
On my external SDcard/clockwork mod/backup/ whatever the date was.
Seems normal. Not sure why it wouldn't be visible. Sorry I can't be more help.
Sent from my SGH-T769 using Tapatalk 2
In recovery they are visible, but when I go to flash one it says no files found..
I was also stuck in a boot loop after attempting to get my phone back to stock since I got a replacement phone. Followed all of the instructions, but realized although I did a factory reset, I forgot to wipe data. So I simply got CWM through Odin....got into recovery wiped data....rebooted and voila! I'm back to stock no root. It took all of 1 minute to do. Maybe that will work for you too
samsung s blaze stuck !!!!!!
please help,i need to get my Samsung s blaze to recovery mode, i already rooted and updated to Cm 10 11 19 nightly and i try to go back to stock rom from using the Odin but i backed up my cm rom,after flashing the stock ROM my phone try to reboot but got stuck at the Samsung logo after the android logo..i tried to get to recovery mode by pressing volume up +home button plus power at the same time but it wont,please your help will be much appreciated,
rashcapone said:
please help,i need to get my Samsung s blaze to recovery mode, i already rooted and updated to Cm 10 11 19 nightly and i try to go back to stock rom from using the Odin but i backed up my cm rom,after flashing the stock ROM my phone try to reboot but got stuck at the Samsung logo after the android logo..i tried to get to recovery mode by pressing volume up +home button plus power at the same time but it wont,please your help will be much appreciated,
Click to expand...
Click to collapse
You gotta search bro all you have to do is flash cwm then reboot to recovery and do a factory reset
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
Thank you for your quick response.I am able to get to recovery mode.and wipe data and factory reset.I got cm10 1117 nightly on my SD card and I install that and my phone is back.then I install jelly bean Google app.I will never try to go back to stock ROM again. this ROM is cm10 1117 nightly is better than stable cm10 for me.I thank all the devs who worked together to bring this your effort is much appreciated.
This is how I get to recovery mode on my Samsung galaxy s blaze.
1.press the vol up + vol down + power button at the same time.
2.as soon as the Samsung logo light up I release power + vol down button but not releasing releasing vol up button but rather press it harder..and there it comes....may be someone might be having the difficulty I had before
Give it a try...
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I have searched threads all over XDA similar to this one to ensure it is not a duplicate. Sadly I have not found any so I hope one of you at XDA can help me. I got my Galaxy S3 and rooted it as soon as it was available. Then two days ago I flashed Cynogenmod 10 onto it without a hitch. I liked it a lot but sadly there were some shortcomings so I wanted to reflash stock. This is where I believe I messed up. I looked up some instructions, and gave it a go. When I turned on the phone, the annoying verizon bootup image and sound came on, but my phone goes no further. I have no care about my data, I just want my phone back to stock, could a developer assist me in this?
If so I would be eternally grateful.
Just reboot to recovery (hold home, volume up, and power). Wipe everything and flash again.
Sent from my SCH-I535 using xda app-developers app
trent407 said:
I have searched threads all over XDA similar to this one to ensure it is not a duplicate. Sadly I have not found any so I hope one of you at XDA can help me. I got my Galaxy S3 and rooted it as soon as it was available. Then two days ago I flashed Cynogenmod 10 onto it without a hitch. I liked it a lot but sadly there were some shortcomings so I wanted to reflash stock. This is where I believe I messed up. I looked up some instructions, and gave it a go. When I turned on the phone, the annoying verizon bootup image and sound came on, but my phone goes no further. I have no care about my data, I just want my phone back to stock, could a developer assist me in this?
If so I would be eternally grateful.
Click to expand...
Click to collapse
Click gs3 link in sig
thanks so much guys!! both of you were big helps
droidstyle said:
Click gs3 link in sig
Click to expand...
Click to collapse
Im having a similar issue as the OP. I made a mistake last night and flashed cwm via rom manager and then loaded CM10. Now my phone just bootloops, but I can get into cwm. MY nandroid backup wont load, says "file invalid". I try to get into odin mode but when I hold the volume buttons and the power it just boots into cwm.
Help!
dreamsti said:
Im having a similar issue as the OP. I made a mistake last night and flashed cwm via rom manager and then loaded CM10. Now my phone just bootloops, but I can get into cwm. MY nandroid backup wont load, says "file invalid". I try to get into odin mode but when I hold the volume buttons and the power it just boots into cwm.
Help!
Click to expand...
Click to collapse
hold volume down and the power button
sent from locked bootloadrer SGS3 running a custom kernel
Hi, I am using an at&t Samsung Infuse 4G... My phone is stuck in the Samsung logo.. it doesn't reboot or anything.. it is just displaying the logo and that's it... The phone was working great running RemICS-UX rom but I installed ROM Manager and selected 'Backup Rom' and it did some thing in the clockwork recovery and took me to the blue recovery screen.. I selected reboot now and it took me to the clockwork recovery reboot again... I did this several times and it still took me to the same place.. it wasn't loading the rom.. I tried wiping the cache, dalvik cache, and user data and reinstalled the RemICS-UX rom.. when I select reboot again.. it took me to the same clockwork recovery again.. it was in a loop... I tried installing another OS.. MIUI gingerbread one and now the phone is stuck on the Samsung logo and I had to remove the battery to switch it off... I tried holding the vol up and down and power key but just reboots to the Samsung logo... its not even taking me to the recovery screen...
Is my phone gone for good??? I tried looking for the solution all around xda and nothing seems fit my problem.. if someone could help me out or link me to a similar place.. I would be very grateful...
and my clockwork recovery was very messed up before it became like this.. looked all glitchy and stuff..
Try heimdal or Odin back to stock and start over.
Sent from my SGH-I997 using Tapatalk 2
The rainbow recovery is because you don't have GB bootloaders.
Be careful flashing those as a bad flash of them would live you with a complete brick.
andros11 said:
The rainbow recovery is because you don't have GB bootloaders.
Be careful flashing those as a bad flash of them would live you with a complete brick.
Click to expand...
Click to collapse
okay.. i am in heimdall one-click and it connected to my device and when i tried to flash it.. it says i have to install driver.. and from the drop down.. i have "Gadget Serial".. in a tutorial, i saw that it should say "samsung USB composite" and so i downloaded and tried to update the driver and i am getting the error "This device cannot start".. how do i fix this??
sunnylegends said:
okay.. i am in heimdall one-click and it connected to my device and when i tried to flash it.. it says i have to install driver.. and from the drop down.. i have "Gadget Serial".. in a tutorial, i saw that it should say "samsung USB composite" and so i downloaded and tried to update the driver and i am getting the error "This device cannot start".. how do i fix this??
Click to expand...
Click to collapse
Gadget serial was the only way my computer would recognize my phone.... so I ignored the tutorial and selected that option...worked fine for me:
http://forum.xda-developers.com/showthread.php?t=1844630&highlight=gadget+serial&page=3
My phone is working again all thanks to XDA.. After many and many attempts, my system connected to my phone.. I was able to flash successfully, but encountered rainbow screen multiple times.. but at the end, everything was working normal (In gingerbread).. I flashed again with the bootloaders and that got rid of the rainbow screens... I now have my Infuse back!!.. Thank you all!.. :good:
Yup ya just have to keep at it the infuse is unbrickable lol well you know what I mean.
Sent from my SGH-I997 using Tapatalk 2
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.