ICS Update - Samsung Epic 4G Touch

Hello All,
FYI: This is stock Not rooted.
I got the prompt this morning on my Sprint Galaxy S2 Epic Touch 4g for a system update to ICS It had a full charge I clicked to reboot it started counting down and all it did was reboot, it didn't update I checked the about section and the build and everything is the same and if I go to the system update area now it just says your phone is up to date. Any ideas on what happened?
Thanks in Advance.
Ryan B.l

Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229

sfhub said:
Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
Thanks for the prompt reply, I appreciate it. I just booted into recovery and wiped the partition cache and rebooted to see if that would help at all. If not then I may just have to manually update as suggested.

I've been using one of Calkulin's ROMs - If I want to try out the stock ICS update, should I flash back to a stock GB ROM first or would I still get a notification to update?

If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229

sfhub said:
If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I found the firmware update at the link below and downloaded it and renamed it to update.zip and rebooted to recovery and ran the update from sd and it updated fine
http://community.sprint.com/baw/thread/89419?start=105&tstart=0

Related

EK02 OTA Update failing..

Hey guys,
So I am on EG30 modem (stock), and I only installed crawlcj's odexed stock rooted ROM.
I got the OTA update notification today morning and I just pressed update and walked away for like 30 minutes, and when I came back there was a yellow triangle with the android figure on the screen and it seemed to be stuck.
So I just held down the power button to turn the phone back on and it seems that the phone is still working fine under EG30 but EK02 was nowhere to be found.
I'd like to get the EK02, do you know why it failed and what I need to do to get the OTA to install correctly?
Thanks in advance
it failed because you are rooted and dont have stock recovery anymore. so if you want to upgrade to EK02 you should just flash the update that is posted already for rooted phones its fast and easy to do.this is the link to get you right to the new modem. after you flash the modem upgrade just chose a rom that has also be upgraded too. now you have the new update its just that easy
http://forum.xda-developers.com/showthread.php?t=1352310
ewalk4866 said:
it failed because you are rooted and dont have stock recovery anymore. so if you want to upgrade to EK02 you should just flash the update that is posted already for rooted phones its fast and easy to do.this is the link to get you right to the new modem. after you flash the modem upgrade just chose a rom that has also be upgraded too. now you have the new update its just that easy
http://forum.xda-developers.com/showthread.php?t=1352310
Click to expand...
Click to collapse
I'm going to jump onto this thread to because I'm having the same issue (and have searched this high and low for a solution). I have Crawrj's Stock EG30 Deodexed with Root 3.0/Busybox 1.18.4 on my phone. All I would like to do is to upgrade to EK02 and 2.3.6 (which I'm not sure if it's one and the same), remain stock but retain root. I don't have an SD card in my phone and I don't have clockworkmod (@ewalk4366 the video in your link assumes the upgrader has CWM). Since the OTA failed, I'm at a loss of how to proceed next. It seems I'm missing one thing or another when it comes to trying to upgrade. Any help would be appreciated.
P.S. Sorry for some noob butter but I still don't have all the terminology down correctly, so there may be times where I say modem but I mean rom and visa versa. For the sake of this thread, I think I'm saying what I mean.
just install the new EL13 modem using odin... i hope you are rooted
ewalk4866 said:
it failed because you are rooted and dont have stock recovery anymore. so if you want to upgrade to EK02 you should just flash the update that is posted already for rooted phones its fast and easy to do.this is the link to get you right to the new modem. after you flash the modem upgrade just chose a rom that has also be upgraded too. now you have the new update its just that easy
http://forum.xda-developers.com/showthread.php?t=1352310
Click to expand...
Click to collapse
Thanks for your response but don't I still have the stock recovery? Crawlrj's odexed busybox rooted 3.0 rom didn't have any other recovery mods..
And I'd like to have the completely stock version of the EG30 ROM and the Modem.. So I should flash both? Wouldn't that erase my memory?
Skoksn,
I was using this thread and a few others to solve my problem which I think was similar to yours
[ACS][How to] EVERYTHING EK02 AND EG30 Android 2.3.6 Gingerbread
Step 1)
How to install ACSRecovery5 (EK02 Kernel):
http://www.youtube.com/watch?v=anjwB9mhn3Q
Step 2)
How to update to EK02 with Clockworkmod:
http://www.youtube.com/watch?v=N80j39tk7fE
Step 3)
How to install the EK02 Modem:
http://www.youtube.com/watch?v=5VDxEnO1tow
I did these 3 things in this order and I'm now on 2.3.6 and EK02 Modem. Hope this helps.

02 root cwm to el29 last few questions please

OK, i used auto root for rooting 02 and installing cwm recovery. then i installed the hotspot mod. perfect, everything working as expected. well now im getting the update nag. sorry for asking repetitive questions, but i want to be sure i have this correct first.
so if i run preroot el29 one click and preserve user data, it will be like the ota update but with root?? then i need to go back into the autoroot option c to get cwm recovery installed again??
will the nag screen go away then for the update??
doing these steps will get me back to root, cwm, and the latest "ota" update?
thanks so much for the time,
Joel
You got it! If you do exactly what you said you will be stock el29 rooted with cwm and you won't get nagged to install an update anymore.
If you'd like to test it out, I put together a rooted EL29 OTA update.
http://forum.xda-developers.com/showthread.php?t=1473538
The advantage is it will patch your existing ROM rather than overwrite your ROM.
There are 2 versions provided. One is rooted. The other is rooted+CWM.
Keep in mind the only repacked EL29+CWM available is Rogue, which supports custom boot animations. The way it is configured, it uses the default Android logo boot animation. Nothing was changed on your ROM, the Sprint 4G animation is still there, just the initialization of the bootanimation was changed.
thanks guys, the rooted el29 and guide is in the sig odin el29 correct??
[ODIN][TAR] SPH-D710.EL29_CL852097 (EL29 Modem/Kernel/ROM - Full Restore - Rooted) ??
the rooted update sounds good, will that keep my cwm, or i need to reinstall it??
where can i find the update to patch my rom?? will i loose my root or cwm or anything with that one?? just need el29 to hotspot again, and root.
thanks again,
Joel
a14) EL29 OTA (patch EK02->EL29) - Sprint OTA [stock recovery] is that the patch method ?? then if i run the check and go that route, i loose root and cwm??
does rootkeeper work for going from 02 to 29 ??
ok found the [CWM][OTA][EK02->EL29] Rooted EL29 OTA update (patches your existing ROM) thread. soooo do i want the cwm option?? i will loose my old one or does this update it??
k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack.
42 years on the planet and i feel like its 42 days sometimes. heh
JS_racer said:
ok found the [CWM][OTA][EK02->EL29] Rooted EL29 OTA update (patches your existing ROM) thread. soooo do i want the cwm option?? i will loose my old one or does this update it??
Click to expand...
Click to collapse
Yes, that is the one, I forgot to put the link earlier.
There is only one CWM repacked with EL29 right now. It is Rogue CWM. You could run CWM repacked with an earlier kernel if you'd like, but if you want the EL29 kernel, there is just one choice. They also have a recompiled kernel based on EL29.
k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack
JS_racer said:
k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack
Click to expand...
Click to collapse
Well if you put the old ones back in place either because you backed up the file or did a nandroid backup prior to installing the hotspot hack, then you could put those back in place and run the rooted OTA. Otherwise go with one of the full updates that don't care what you currently have.
thanks so much, did the one click el29, still up and running so thats good.
was there anything funny with the cwm el29 from autoroot option c?? bootlogo or anything or it will look just like before. i have the hotspot files to transfer, guess just the jar files. should i do them by hand or install the cwm and install from sd and backup again ??
thanks so much for everything, much appreciated
Joel
Rogue CWM supports custom boot animation and it is initialized with the standard android bootlogo by default. That's the only stock EL29 repacked with CWM right now.
If it bothers you, you could run stock El29 and just install CWM when you need it, or you could install EL26+CWM (chris41gs repack) or I could dig up something to use the Sprint 4g animation. All the files are still there, just the initialization changed.
damn that was spooky, got stuck at the galaxy logo after a botched copy file operation. guess i need cwm to update the hotspot.
hit the oneclick 29 again, and it worked, damn.

Can I do OTA 4.0 update with Rogue recovery?

I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
You can use sfhub's auto root tool to check if your ROM is compliant. If it isn't, it will fail the update.
http://forum.xda-developers.com/showthread.php?t=1342728
Why don't you just use sfhub's one click FF18 with root. You need to be on stock el29 to accept the update. If not it will fail.
Sent from my SPH-D710 using xda app-developers app
Stuck on triangle
cphil99 said:
I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
Click to expand...
Click to collapse
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
I'm having the same issue.
Edit: I got it. I installed it in the folder not the root of the sd card.
Sent from my SPH-D710 using xda app-developers app
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
I got it!
sfhub said:
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
Click to expand...
Click to collapse
That did it! I just downloaded and ran the new Odin file and it worked like a charm with no loss of data. Thank you so much for you help!

Root OTA FH13?

I'd like to update to FH13 (OTA not leak) with root. Is it possible to root the OTA or is there a rooted OTA that I can flash?
Edited.
Edit: hey Horace My apologies for being an ars.. sorry!
Sent from my SPH-D710 using Tapatalk 2
This guy has only been a member since 2007 go easy on him.
Sent from my Nexus 7 using xda app-developers app
People aren't finding it becase the thread title doesn't show rooted.
Look for rwilco12's FH13 thread - post 3 has what you're looking for.
garwynn said:
People aren't finding it becase the thread title doesn't show rooted.
Look for rwilco12's FH13 thread - post 3 has what you're looking for.
Click to expand...
Click to collapse
Isn't it post 2? And I thought that was still the leaked version?
D2dyno said:
Isn't it post 2? And I thought that was still the leaked version?
Click to expand...
Click to collapse
Its the same as one on kies.
Sent from my SPH-D710 using xda app-developers app
Oh, okay. Thanks! I must have gotten the one before this, because that one was leaked, but rwilco12's post didn't change, so I assumed it was still the leaked version.
Horace said:
I'd like to update to FH13 (OTA not leak) with root. Is it possible to root the OTA or is there a rooted OTA that I can flash?
Click to expand...
Click to collapse
All u have to do is Odin Agatha stock fh13 kernel with cwm. Then boot into recovery and flash su.zip. then u will have root.
Sent from my SPH-D710 using xda premium

			
				
Horace said:
I'd like to update to FH13 (OTA not leak) with root. Is it possible to root the OTA or is there a rooted OTA that I can flash?
Click to expand...
Click to collapse
Ok, so I don't know how anyone roots their ROMs - and I mean root, not replace with an already rooted ROM - but here's what I did on my phone:
1. Installed FH13 thru Kies
2. With a little nudge I ODINed AGAT's custom kernel (v2.1?), which gave me the Triangle on startup.
3. Googled, found and installed superuser zip from recovery.
4. Installed the Busybox app from the Play Store. Then opened Busybox, hit install.
5. Installed Supersu from the Play Store, then used my already-installed Root Explorer to delete superuser.apk from system/app.
6. Deleted the Busybox app from settings/applications.
7. Installed a copy of TriangleAway-v1.25.apk that I keep on my sd card, then opened it, used it to clear the Triangle created in step 2, then restarted the phone to check.
8. Deleted TriangleAway from settings/applications.
9. Installed leaked FH13 stock kernel thru recovery. I couldn't find the pulled official OTA one, but they're supposed to be identical.
and Voila! I had what I wanted - official ROM, stock kernel and root.
Can't we just flash a custom recovery (like CWM or agats) via Odin and then flash su.zip in that recovery and then you are rooted? This way nothing changes with the kernel?
That is how I originally rooted my Galaxy Tab 10.1. But now that I am typing this I am remembering that someone just recently told me that the recovery is part of the kernel for our E4GT so then just flashing a recovery is not possible, correct?
I had bad luck with one of the first OC FF13 rooted methods because there is something not compatible with the old bootloader and FF13. So I nandroided back to my FF18 build and then updated to FF13 via kies and so far (knocks on wood) everything is great with this updated. I really don't want to install a different kernel right now because I don't want to mess with a good thing but I really need my root back.
Raistlin1 said:
Can't we just flash a custom recovery (like CWM or agats) via Odin and then flash su.zip in that recovery and then you are rooted? This way nothing changes with the kernel?
That is how I originally rooted my Galaxy Tab 10.1. But now that I am typing this I am remembering that someone just recently told me that the recovery is part of the kernel for our E4GT so then just flashing a recovery is not possible, correct?
I had bad luck with one of the first OC FF13 rooted methods because there is something not compatible with the old bootloader and FF13. So I nandroided back to my FF18 build and then updated to FF13 via kies and so far (knocks on wood) everything is great with this updated. I really don't want to install a different kernel right now because I don't want to mess with a good thing but I really need my root back.
Click to expand...
Click to collapse
Right the recovery and the kernel are the same on this device. So you have to replace the kernel to get custom recovery. You could install the custom kernel, flash su and install the stock kernel. Or you can Odin Odexed No Data Wipe Tar from http://forum.xda-developers.com/showthread.php?t=1844109 and be done.
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
cferd said:
Ok, so I don't know how anyone roots their ROMs - and I mean root, not replace with an already rooted ROM - but here's what I did on my phone:
1. Installed FH13 thru Kies
2. With a little nudge I ODINed AGAT's custom kernel (v2.1?), which gave me the Triangle on startup.
3. Googled, found and installed superuser zip from recovery.
4. Installed the Busybox app from the Play Store. Then opened Busybox, hit install.
5. Installed Supersu from the Play Store, then used my already-installed Root Explorer to delete superuser.apk from system/app.
6. Deleted the Busybox app from settings/applications.
7. Installed a copy of TriangleAway-v1.25.apk that I keep on my sd card, then opened it, used it to clear the Triangle created in step 2, then restarted the phone to check.
8. Deleted TriangleAway from settings/applications.
9. Installed leaked FH13 stock kernel thru recovery. I couldn't find the pulled official OTA one, but they're supposed to be identical.
and Voila! I had what I wanted - official ROM, stock kernel and root.
Click to expand...
Click to collapse
Here is what I would change to cut down a step.
1. Installed FH13 thru Kies
2. With a little nudge I ODINed AGAT's custom kernel (v2.1?), which gave me the Triangle on startup.
3. Install SuperSu from here http://forum.xda-developers.com/showthread.php?t=1806111.
4. Installed the Busybox app from the Play Store. Then opened Busybox, hit install.
5. Deleted the Busybox app from settings/applications.
6. Installed a copy of TriangleAway-v1.25.apk that I keep on my sd card, then opened it, used it to clear the Triangle created in step 2, then restarted the phone to check.
7. Deleted TriangleAway from settings/applications.
8. Installed leaked FH13 stock kernel thru recovery. I couldn't find the pulled official OTA one, but they're supposed to be identical.
and Voila! I had what I wanted - official ROM, stock kernel and root.
Of course you could just Odin Odexed No Data Wipe Tar from http://forum.xda-developers.com/show....php?t=1844109 and accomplish the same exact thing in one step
crawrj said:
Here is what I would change to cut down a step.
1. Installed FH13 thru Kies
2. With a little nudge I ODINed AGAT's custom kernel (v2.1?), which gave me the Triangle on startup.
3. Install SuperSu from here http://forum.xda-developers.com/showthread.php?t=1806111.
4. Installed the Busybox app from the Play Store. Then opened Busybox, hit install.
5. Deleted the Busybox app from settings/applications.
6. Installed a copy of TriangleAway-v1.25.apk that I keep on my sd card, then opened it, used it to clear the Triangle created in step 2, then restarted the phone to check.
7. Deleted TriangleAway from settings/applications.
8. Installed leaked FH13 stock kernel thru recovery. I couldn't find the pulled official OTA one, but they're supposed to be identical.
and Voila! I had what I wanted - official ROM, stock kernel and root.
Of course you could just Odin Odexed No Data Wipe Tar from http://forum.xda-developers.com/show....php?t=1844109 and accomplish the same exact thing in one step
Click to expand...
Click to collapse
Yea, I knew I had taken more steps than needed when I rooted my phone, but the steps I mentioned were the steps I actually took so I felt the need to post them that way. I do however have the SuperSU file you posted for future use, thanks.
Once i odin the no wipe tar ill be stock rooted with custom recovery ?
Edit: figured it out!
Sent from my SPH-D710 using xda app-developers app

[Q] Can't Install 4.4 OTA Update

Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.

Categories

Resources