I've been receiving [incessant!] prompts that an OTA update was ready to install on my phone.
So - I unrooted my phone and replaced the stock recovery using this process.
Following that, I checked that I no longer had root, and booted to recovery to confirm it was the stock recovery... and then back into the phone to finally tap the "install" button when prompted.
The phone rebooted into the stock recovery, started to install the update... then, in red text - an ERROR message (that I failed to capture because after a few minutes the phone just went to an android with a red ! triangle over it).
I had to pull the battery since the buttons didn't do anything and there were no other options. The phone booted back into recovery, and then I got some sort of confirmation message in yellow text that sounded like "success", and I was still in the stock recovery.
So, I selected the "reboot" option and booted back into the phone.
All seems well (I'm still 100% stock, not rooted), but I am completely unclear if the update worked or failed.
If I go to "system update", I get messages in all four categories:
( i ) Error
The PRL update could not be
completed. Please try again later.
If the problem persists, you may
need to contact Customer Service.
Error: (Code:4)Client Authentication
Error
Click to expand...
Click to collapse
The Update Profile, Update Samsung Software, and Update Firmware all return the same error message.
How can I check the status of my device?
Any ideas what these errors indicate?
Looking for an answer on this- either:
1) What does "Error: (Code:4)Client Authentication Error" indicate when checking for updates in the System Update category?
and/or
2) How do I check to confirm if the OTA update completed successfully?
On a side note - I'm also interested in learning what is/was in that update. The answer to 2) might help me find a thread specific to that OTA update.
Help is appreciated, thanks.
Are you using a custom recovery like CWM or TWRP?
The Root said:
Are you using a custom recovery like CWM or TWRP?
Click to expand...
Click to collapse
No. As described in the first post -
I had previously rooted my phone and installed CWM recovery (to flash a 'root from recovery' update).
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
As mentioned, the appearance is that I can't force the phone to check for a new version due to the error message I get in the System Update categories, so I'm unclear whether the OTA applied, didn't apply, if it caused an issue, or if this is all normal?
What would indicate that the OTA update applied? Baseband version number? What should it be?
If you check for a System Update on your device, do you get this same message that I'm seeing?
Thanks!
geolemon said:
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
Click to expand...
Click to collapse
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.
The Root said:
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.
Click to expand...
Click to collapse
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?
geolemon said:
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?
Click to expand...
Click to collapse
If you're on LG8 it should be the update to LI3. Have you Odined to stock, stock?
Sent from my SPH-L710 using xda app-developers app
I may be misunderstanding the question... clicking that link may help.
I was 100% stock prior to a client visit two weeks back. I rooted following the process in that link.
In brief (using files in that link)
1) installed CWM via Odin
2) use CWM to flash "root from recovery" file
This week I started getting prompted there was an OTA.
Knowing I at least needed stock recovery or it would fail,I restored back to stock following the restore process in that link.
In brief (using restore files in that link):
1) flash unroot file via CWM
2) use Odin to flash stock recovery.
I used root checker to confirm root was gone, rebooted to recovery to confirm CWM was gone, booted back to phone and accepted the OTA.
The phone then booted into recovery and events occurred as described in post 1.
Anything unusual spotted with the process?
Sent from my Nexus 7 using xda app-developers app
Here's a screen capture of the update error message:
Sent from my SPH-L710 using xda app-developers app
Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
DrgnRebrn said:
Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?
geolemon said:
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?
Click to expand...
Click to collapse
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
DrgnRebrn said:
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
I'm over the novelty of rooting, that's all, years ago. Going back to my G1 (the first Android phone ever!), I rooted that one even.
In the case of my Magic (basically a G1 without a keyboard), it was really to extend it's life, I was running custom ROMs on both the G1 and Magic (CM6), was a great option. Kept it a long time, loved that phone actually. Still miss a trackball.
Here, I rooted for a specific purpose - and actually the Wifi Tether app was the one I used, since I've had experience with it on my other phones. Always worked flawlessly, going back to the Magic days even.
But on the GS3 - I don't know if you've tried it or not - it's not reliable. You'll find threads for it (I worked through several of them in the airport trying to get it working, using different profiles, different settings, even sideloading an older APK that predated the GS3 profile, as some users mentioned that as the path. Bottom line regardless - it's just not 100% on the GS3. I spent somewhere close to 2 hours, 1 of that in the airport, reading through threads and troubleshooting suggstions, none were 100%.
And I wouldn't pay for it, we travel with MiFi devices that the company pays for. This was just a backup plan, me being a nice guy. Thought it would be easy, as it always has been in the past. There's something unique to this phone that's very different than others, not sure if this is your first, but other phones are usually simple... root, use Wifi tether. No hassle.
So, that being the case (or until an option exists for tethering that is reliable), I don't have much need for root. Even Titanium Backup. Would be nice to do nandroid backups, but if it's all stock... should be no real need.
I didn't read that thread (yet), but there's an "everything about Wallet" thread here. That one may be linked... Wallet works, I haven't had a problem with it not working, but with the device in a Modified status, it gives you some eyebrow raising warnings.
I believe that thread is actually for people who didn't read that "everything about Wallet thread", have flashed a custom ROM without clearing Wallet, and as a result now find themselves in tears with a locked/bricked Wallet. That'll make some people happy.
If my device is going to show a "modified" status, with the (hopefully few) risks inherent in that (ie. Sprint support), I'll at least go to a JB leak ROM or CM10 or similar and get some bang for my commitment, as opposed to the "least modified possible" route yet showing modified status. I just had no need to yet, not looking forward to wiping my phone, reinstalling, reconfiguring.
Triangle Away has been around a long time too - I didn't bother with it when I rooted because of this disclaimer:
- On the SGS3/Note2/etc, System->Settings->About device->Status still shows "Modified"
This is outside the scope of Triangle Away. The "system" status is not even always resettable in the bootloader. If you are going for warrenty, you need to also reflash a full stock firmware and wipe your device. If they boot up your device and find root apps, you're not going to get any warranty anyway. If you do such a full stock reflash and wipe, the "Modified" value will go away.
Click to expand...
Click to collapse
The Modified status did go away when I flashed the stock recovery back. Wallet is my only concern with that status btw, it's slick how it gives you transaction statuses, however it apparently leaves many of them as "unknown" in this state, which I'd like to fix (or stay stock for now).
Related
Just recently purchased an almost new Nexus that was originally purchased from Google.
Just got the notification that there was an update avail, 4.1.2 but it failed with an error and I see CWM listed.
How can I remove ClockWorkMod and get back to stock android?
Thanks
If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895
martonikaj said:
If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you very much for the link. I'll have to make sure I don't loose anything since it's my wife's phone. I should have looked more closely when the install bombed out but I saw CWM and there was the typical list of things that you have to increment thru to get to what you want to install. Maybe the big system in the sky will try to do another OTA update before I get around to reinstalling.
All stock but cannot update
martonikaj said:
Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Click to expand...
Click to collapse
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.
masasin said:
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.
Click to expand...
Click to collapse
2nd post of this thread
http://forum.xda-developers.com/showthread.php?t=1419170
Read it. Part of it is true for official (directly from gservers to the device) updates. If you want, you can then update yourself (read also 1st post) like instructed or put it like it needs to be and use normal update from within android again.
Read the stickies people, before pressing the "new thread/reply to" button.
Sent from my i9250
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
charley000 said:
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Click to expand...
Click to collapse
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
rangercaptain said:
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
Click to expand...
Click to collapse
Well tried that. Still fails.
I suspect there is some app or setting that I have to have for ATT to allow me to do it. Others have commented that you need all the ATT Bloatware and other stuff. I am not sure what I have wrong.
Read back one.. I was typing while you were sending
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks. Probably the best thing for me to do is just to wait until after 4.3 comes out. By that point, you guys will have figured it all out. Then I can either go from scratch (Odin to stock and the update) or I can pick the best ROM from here. I will probably do the latter.
I am leaning towards one of the ROMs that is close to stock such as Clean Rom or Jedi unless someone has a better suggestion.
Thanks everyone for your help.
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks for this info, very helpful.
Though I am rooted and on a custom ROM and all that, I'm far from an expert on this stuff. I plan on trying the AT&T 4.3 update when it drops, but I am also currently contemplating trying to go to MH3 stock, and maybe then re-root on MH3 and make a full Rooted stock backup available "just in case"...
With that in mind - Question: Can you tell me if getting the stock LJ2 or MA4 firmware via sammobile and loading it via Odin takes care of *completely* "stock"-ing your phone, all in one shot, including resetting the flash counter to "0" and all that good stuff? OR - would I still need to then CF-Auto-Root, Triangle Away, and then do a "Full Unroot" in SuperSU to accomplish all this? Just want to make sure I get it right
Thanks in advance. Been searching but have not found a clear-cut answer to this just yet.
Anonymously_Unknown said:
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
Click to expand...
Click to collapse
Will this work if I have TWRP installed?
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
n01un0 said:
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
If you are on stock and have a valid AT&T SIM card in the device with full access to Wi-Fi and the AT&T network, you should be able to get an OTA update. Root could, however, indeed prevent an OTA update so your best bet may be to unroot. You could unroot and uninstall SuperSU from the SuperSU app just as you suggested. This should do it. However, if it doesn't and you would really want to avoid Odin and custom recovery, then you could do a 2-step manual update to 4.3 via stock recovery - first to 4.1.2 and then to 4.3. This will naturally update your phone to (full) stock 4.3 and we can then see if the phone will take the Kit-Kat OTA update from there.
You can see the instructions for the 2-step update via stock recovery in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
1) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
2) Copy the zip files to a good quality (micro) SD card
3) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
4) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
5) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
6) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
7) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
8) Repeat the process for the second update file.
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
n01un0 said:
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Larry2999 said:
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Click to expand...
Click to collapse
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
n01un0 said:
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
Click to expand...
Click to collapse
Glad to know you were finally able to update. To try to answer your questions ....
1. Towelroot indeed comes well recommended for rooting on Kit Kat. You could, however, first try CF Auto Root which is one of the simplest approaches to rooting. If this doesn't work, you could try Option 2 in the thread below ... The thread also contains instructions to CF Auto Root.
http://forum.xda-developers.com/showthread.php?t=2538991
2. I'm not sure what that battery indicator is. I run 4.4.2 also on my S3 but I cant see this. Can you try a reset to see if it would go away?
3. You can try removing this from settings.
Im glad you asked this...
I too noticed Im on 4.1.1 stock but rooted. I wondered if you could go to 4.4.2 as my phone tried to OTA update on its own last week and failed. I did not know if it was worth it to try or not another way. About the only thing I see that would want me to try is Google Wallet now working with S3 on 4.4.2 without having to jump through all kinds of hoops, mine used to work fine, but now GW will not open up all the way. Im not sure its worth doing if I have to re setup all my crap as I will be upgrading my phone whenever I want, just holding out to see if the Nexus 6 will be out end of the year and on AT&T..Im not liking that all the new phones are getting so freakin big, the S3 is just right and I dont want to have to end up with a damn Note sized phone but that is a whole other discussion
If you're still on 4.1.1, BEFORE ANYTHING ELSE, UNLOCK YOUR PHONE IF HASN'T ALREADY
otherwise you'll regret it
then the rest, tbh, you don't need to unroot at all to upgrade, just flash the firmware in ODIN or recovery..
edit: nvm it seems like you've already upgrade yours to KitKat
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.