Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.
vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?
GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.
vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.
I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.
I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly
Related
I thought about rooting, and started the process with the one click mod about a month ago. I got the superuser app in the process. Never went any further. Now I am trying to download the official froyo (which is technically on hold), but it aborts everytime. I am wondering if the superuser or CWM is causing this. I have done a wipe/factory reset three times. Any suggestions? Thanks.
jkmola said:
I thought about rooting, and started the process with the one click mod about a month ago. I got the superuser app in the process. Never went any further. Now I am trying to download the official froyo (which is technically on hold), but it aborts everytime. I am wondering if the superuser or CWM is causing this. I have done a wipe/factory reset three times. Any suggestions? Thanks.
Click to expand...
Click to collapse
I'd suggest updating by using the official Samsung update on their web site, which you can run from a PC. It seems to provide a much more trouble free update. It will also totally wipe your phone (but not the SD card) so be sure you have a way to restore your data.
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
Assuming you have a PC, click on the software link, then click on the EXE link for the EB13 update. Install on your PC and follow the directions.
odin back to stock, use eb13 in the pda slot you will have a stock updated phone
i would also advise against updating ota because it's my understanding that it was problems with the ota process that caused sprint to pull the plug. it's really hard to adequately stress how simple using the samsung exe is. if you can turn on a computer you can have a fresh installation of eb13 froyo
wait for the actual fixed release from either sprint or samsung and use either the samsung tool or odin to do a clean install.
I have 2 Epics, one stock, one rooted and rommed. I ran the Samsung .exe
and it caused nothing but troubles on the stock, so had to return to 2.1.
To do so, either go to Service Center or run Odin.
This will also work to unroot and return to stock. The easiest instructions I have found to follow are on Android Central under Epic Forums. Look in Roms and Rooting Section in stickies. Title is something like unbrick. It gives all the links for downloads and how to's. You must be registered to use
but it is less techy there so might be easier to follow.
Thanks, everybody. I just finished the update via the samsung site. Phone just came back online. I will start messing around with it and see how everything worked out. Thanks again!
ilostmypistons said:
odin back to stock, use eb13 in the pda slot you will have a stock updated phone
Click to expand...
Click to collapse
When you odin all you put is the eb13 file in pda and nothing else? No pit? Also where can you get the eb13 stock tar?
Sent from my SPH-D700 using XDA Premium App
ErlyD said:
When you odin all you put is the eb13 file in pda and nothing else? No pit? Also where can you get the eb13 stock tar?
Click to expand...
Click to collapse
You get it right out of the installed .exe file you installed to.
Sent from Bonsai 6.0.3
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
I can't yet because of root. I need access to my computer.
crystalstylez said:
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
Click to expand...
Click to collapse
Installed it...
I got it also. 16gb u.s. Wifi version. it was installing & updating android apps as I left out for work.
Any changelog on what was changed or added?
I want to install it but will a root method be made for it. I am not near a computer to use the zedomax root method. Anyone had root while installing this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Downloading it now. Will install shortly.
Sent from my GT-N8013 using XDA Premium HD app
Edit:
Installed, must have wiped cache as all apps went through the updating process. No noticeable differences or problems. Seems to be a tick faster but that's probably just my perception.
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
californiarailroader said:
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
Click to expand...
Click to collapse
I hope one of the fixes is making bookmarks appear quicker in the stock browser.
cmunho said:
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Click to expand...
Click to collapse
I wonder exactly which bugs. I hope that folder & keyboard bug got fixed. the one where they open by themselves when going to homescreen from certain apps or whatever. it was getting irritating having to constantly close them. Lol
Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
OK, as expected, lost root. Odin flashed the original cwm recovery back. reinstalled the original root file and and back to being rooted.
Still 4.0.4.
All you had to do was use voodoo ota rootkeeper to backup n restore root file. access to computer not needed.
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
vanillanesquik said:
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
Click to expand...
Click to collapse
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
mitchellvii said:
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
Click to expand...
Click to collapse
I used OTA rootkeeper as specified above. If that does not restore root I can re-do the Odin. Thanks
Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
ye i just did it and i lost root but the first thing i noticed that is working faster. also the snote app was update you can upload your own template finally. when choosiing a background on the window pop up touch the little square image on the top right corner and it lets you choose from images in your gallery.
tmaurice said:
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
Click to expand...
Click to collapse
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
californiarailroader said:
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Click to expand...
Click to collapse
Thanks - I saw that link a couple of days ago, but didn't use it because it's the N8000 and we've got the 8013 here in the States.
I downloaded the official OTA update. When I went to install it the phone needed to reboot and now I've been stuck looking at the Green Android screen saying Downloading... Do not turn off target!!! and in very small writing could not do normal boot, Odin mode. I am rooted. Please help
What version is the phone? I'm reading up on things in preparation of updating myself. I'm on MF3 and for what I've read I need to Odin back to stock before updating since I'm rooted. This may not be your case figured I'd toss it out there.
brought to you by my not so sexy GS4 MF3
padgaland said:
I downloaded the official OTA update. When I went to install it the phone needed to reboot and now I've been stuck looking at the Green Android screen saying Downloading... Do not turn off target!!! and in very small writing could not do normal boot, Odin mode. I am rooted. Please help
Click to expand...
Click to collapse
Same with me. I'm stuck at the emergency firmware recovery screen. My phone was at 4.2 and it did the OTA to 4.3.3 and froze. What do I need to do to go back to stock rom?
SGH-I337 16GB.
schreiber37 said:
Same with me. I'm stuck at the emergency firmware recovery screen. My phone was at 4.2 and it did the OTA to 4.3.3 and froze. What do I need to do to go back to stock rom?
SGH-I337 16GB.
Click to expand...
Click to collapse
You i think you should use Kies to go back they actually have a feature for that. Mine won't even be recognized by the computer or anything.
I am rooted and I was running 4.3 GoldenEye v 11 rom BTW awesome ROM and Dev support best I've ever seen on xda. Any way today I installed my nandroid back up of stock ROM 4.2 Att gs4 sgh 1337 let it boot up any settle in 10 min..when I looked at phone I saw the Att redwhite arrows in task bar I quick shut down WiFi and now under settings status it says update continue or something .now my back up is mdb never ota before. so is this update mf3 the one u that is bootlocked or is it the 4.3 update?? I read some were Att was to start with 4.3 update yesterday what u guys think I should do? Thanks in advance ..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ok I am going to try to go back to stock by using a firmware DL and Odin v3.07 If it works I will tell everyone. If not I may be screwed.
I'm currently on MF3 and had rooted my device previously and would like to upgrade to the new OTA. Would someone be so kind to link me to ODIN and the stock file,so I may return to stock and apply the OTA.
Thank you,
Did anyone go to recovery and factory reset?
Sent from my Nexus 7 using Tapatalk 4
Andrew149 said:
Did anyone go to recovery and factory reset?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'd recommend it but it's to late for me.
This worked for me to unroot.
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Ditto
silrosriv said:
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Click to expand...
Click to collapse
Same exact problem!
wading through threads for answer!
Ok I have my phone working again. I am not on 4.3 but its back to where it was before I started, which is better than nothing. After running Odin once and it failing like it always does (I have never seen it work) I was able to get the holding down volume, home and power button option to work and I just said no and to reboot and it worked. I then went into SuperSU app and unrooted. I will try to update to 4.3 at a later time. I am glad I wasn't the only one having issues. I usually pride myself on knowing technology and being able to figure it out.
silrosriv said:
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems.
So if I oden to stock again don't root Then hit the update it should go? Weird thing is I installed my back up today and it a stock backup fresh rich from a oden wipe and it stared DL on its own before I stopped it with killing WiFi. I s this 4.3 update or is it mf3 since I never did that update. ..help. Thanks
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
tried that..didnt work
padgaland said:
Ok I have my phone working again. I am not on 4.3 but its back to where it was before I started, which is better than nothing. After running Odin once and it failing like it always does (I have never seen it work) I was able to get the holding down volume, home and power button option to work and I just said no and to reboot and it worked. I then went into SuperSU app and unrooted. I will try to update to 4.3 at a later time. I am glad I wasn't the only one having issues. I usually pride myself on knowing technology and being able to figure it out.
Click to expand...
Click to collapse
Tried unrooting through SuperSU and managed to still be rooted after reboot, and OTA 4.3 still didnt work
SIGH
Read that u have to oden to stock dint root and the try ota they say this worked gunna oden back to stock and try..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
thanks
ralphie1267 said:
Read that u have to oden to stock dint root and the try ota they say this worked gunna oden back to stock and try..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
could you point me in the right direction for that procedure? Im trying to do it on my mac using hiemdall but I think im about to go try odin on a PC.
MasterShakeMan said:
Tried unrooting through SuperSU and managed to still be rooted after reboot, and OTA 4.3 still didnt work
SIGH
Click to expand...
Click to collapse
Take it to Best Buy. "Kies broke your phone" *wink*wink* and they can flash it back to stock without messing up your data. You can do it yourself. Plus they have this mysterious awesome SMART tool. Lol
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
MasterShakeMan said:
could you point me in the right direction for that procedure? Im trying to do it on my mac using hiemdall but I think im about to go try odin on a PC.
Click to expand...
Click to collapse
Use the link in my previous post (post #13). That has the files and procedures for using Odin to get back to stock 4.2.2 and then you can do the OTA upgrade from there.
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?
Received this update, doesn't look like anything major
Sent from my SM-P900 using XDA Premium HD app
Downloading mine as we speak.
Rolling out in the Netherlands as well. For now no significant changes. Like to see a full changelog..
New:
PDA: P900XXUANC4
CSC: P900OXAANB6
MODEM: P900XXUANC4
Downloading in on a US purchased WiFi model right now.
Sent from my SM-P900 using Tapatalk
"Your device has been modified, software updates are not available."
Tried the Cellular South version on Sammobile. Full wipe and install via Odin 3.09. Seems snappier to me. Reinstalled all my apps. Leaving it unrooted for now.
Sent from my SM-P900 using Tapatalk
Applied update today.
Two things I notice:
1. Viewing large images in stock gallery now much speedier. Before, there was a long delay drawing large images.
2. Suddenly X-plore my preferred file manager has write access on SD card! Before this update it didn't. Haven't really looked fully if other apps have write access that didn't before. Hancom office updated also but it still can only write to a specific location on SD. Maybe X-plore was just a fluke either way? I'm not sure, but happy it works now.
I just notice the update and I just want to know what it will change for better since the device already good enough for me.
Sent from my SM-P900 using Tapatalk
Update in the Netherlands caused much faster WiFi connection. It was extremely slow before while doing a test with the speedtest.net app. The whole device feels speedier and snappier now. For me a big improvement. I hope more will follow, because the speed experience on this very expensive device is a bit disappointing to me.
Lost Root
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
I flashed the update in odin, lost root, flashed cf auto root again and regained root, everything working great and fully rooted on the latest firmware.
Sent from my SPH-L720 using Tapatalk
hendav said:
I flashed the update in odin, lost root, flashed cf auto root again and regained root, everything working great and fully rooted on the latest firmware.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Would you please let me know your build Number? I did so much flashing today I don't even know if I got the latest build now.
Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
you won't lose root. You just have to reinstall SuperSU and everything will be fine. I lost root after updating to the new firmware, however after rebooting I reinstalled the SuperSU and I Have root again.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
I am now rooted on build P900UEU1ANC5 from Cellular South firmware I got from Sammobile. No noticible changes and no problems so far.
Russbad said:
I am now rooted on build P900UEU1ANC5 from Cellular South firmware I got from Sammobile. No noticible changes and no problems so far.
Click to expand...
Click to collapse
Yup, Thats the latest firmware update that was most recently rolled out for the P900 series. ( P900UEU1ANC5 )
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
same happened to me. reinstalling supersu didn't work. I tried rerooting with cfautoroot and it hangs on cach.img then my screen goes striped red and freezes. couldn't even boot, had to re flash recovery to boot.
shouldn't have updated.
madjinx said:
same happened to me. reinstalling supersu didn't work. I tried rerooting with cfautoroot and it hangs on cach.img then my screen goes striped red and freezes. couldn't even boot, had to re flash recovery to boot.
shouldn't have updated.
Click to expand...
Click to collapse
1. Reflash root with Odin.
2. Reboot.
3. Reinstall SuperSU.
4. Enjoy root privilages.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
1. Reflash root with Odin.
2. Reboot.
3. Reinstall SuperSU.
4. Enjoy root privilages.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
there a root to flash other than cfautoroot? that's the only one I've seen.
madjinx said:
there a root to flash other than cfautoroot? that's the only one I've seen.
Click to expand...
Click to collapse
cfautoroot is the only one that I'm aware of to flash, that's working anyways. I've seen other work in another forum however it hasn't been fully successful.
Android.Ninja said:
cfautoroot is the only one that I'm aware of to flash, that's working anyways. I've seen other work in another forum however it hasn't been fully successful.
Click to expand...
Click to collapse
as I said in my other post, cfautoroot isnt working for me.