Hello,
I rooted my ATT SG2 some time ago and i tried a few of the popular ROMs. After trying them i went back to the original ATT ROM as it is a very good ROM.
Some time last week i got a message saying there is a new update for me to install, my question is, if i do the update will i lose root?, will i need to redo everything i did to root my phone without affecting the flash counter? or just the root part??
Thanks
PToN22 said:
Hello,
I rooted my ATT SG2 some time ago and i tried a few of the popular ROMs. After trying them i went back to the original ATT ROM as it is a very good ROM.
Some time last week i got a message saying there is a new update for me to install, my question is, if i do the update will i lose root?, will i need to redo everything i did to root my phone without affecting the flash counter? or just the root part??
Thanks
Click to expand...
Click to collapse
I believe the OTA update will remove root, but doing the update won't increase flash counter. But in order to get root back, you must follow the same steps you did to ensure you don't trip the counter.
You're the first person I've heard who likes the stock ATT Rom w/ Root (not touched at all).
My assumption is yes, you will lose root. Can anyone confirm this?
Skyrocketing with QuickWiz via XDA Premium
I was unable to apply the update with a rooted device.
I installed the image from this thread
http://forum.xda-developers.com/showthread.php?t=1381497
having trouble getting root with superoneclick (must be forgetting something)
Hi,
i bought a Samsung Galaxy S3 GT-I9300 about two months ago, it's a Spanish device. I think the device came with 4.0.1 update of ICS, some weeks after buying it got 4.0.4 update and then using CF-Root 6.4 and Odin 1.85 managed to get root access so i was able to install busybox and UMS application from xda forums. So everything was working fine. Then, about 3 days ago i got an update notification which showed me a message which said "Updates will be provided in the request order preference" or something like this, i tried to update a few times more but no luck, i always got the same messages so i thought i had to wait for 4.1 update to get published but anyway everything was working fine.
The curious thing is yesterday ( August 25, 2012), when i woke up i noticed a firmware update was ready to be installed so went through it (without uninstalling CF-Root 6.4, supersu, etc.) but the strange thing was, after the update completed fine, went to settings to check the version and i saw it still/again was 4.0.4 version of ICS. Also noticed Google Play Books and Google Play Movies got installed so on one hand it seemed everything went fine cause new apps were there and everything worked as expected but on the other hand i think i already had 4.0.4 update installed on the device. Till that point one can think i got confused on the versions i got installed before the update and no major problem here. After that, as i already had root access on the device, i went to check if i still could run UMS app but it complained about missing root access so as i did before that last Android update took CF-Root 6.4 and Odin 1.85 to flash the device and get root access again (Without removing any previous install of CF-Root, super su, busybox, etc. ) but had no luck, so now it's not possible for me get root access again but i'm also still wondering how is it possible that today's update left the phone with the same Android version as before the update.
The only explanation i can find is the phone came with 4.0 version, first update got me to 4.0.1 and today's update guided me to the 4.0.4 but i'm still wondering why root access is not working as it should.
So my questions are, did i got confused about each version update? Then why can't i get root access again just repeating the same first process?
When opening busybox i can read "Not Enough Free Space in /system". Opening /system directory with Root Explorer i can read 1.05GB used, 436.39MB free. Is it right /system directory takes up to 1GB of the space? Why Busybox thinks there is 0.0MB free there?
Hope someone can help. Thanks in advanced!
Thousands of posts say OTA updates may fail if the phone is rooted .
Usual is to fail part way through an update ..
Suggest wipe the phone flash stock rom with Odin then root .
jje
JJEgan said:
Thousands of posts say OTA updates may fail if the phone is rooted .
Usual is to fail part way through an update ..
Suggest wipe the phone flash stock rom with Odin then root .
jje
Click to expand...
Click to collapse
Thanks a lot for the info. Am i going to loose installed apps, system settings, etc when doing the suggested process? Do i really need to wipe the phone before flashing the phone? I suppose i can find stock rom for my model here in the forums. Thanks!!
Hi,
i'm looking for a stock firmware for my SGS3 BaseBand I9300XXLH1 but i'm not able to find it. I think the firmware which came with my phone is unbranded and from Spain. But the question which i'm wondering is, do i really need to flash the phone? Isn't possible to solve the issue in another manner? After updating through OTA the rooted device, what's supposed to went wrong?
Lastly, what's wrong on updating a stock rooted firmware using Phone/Android update system? Don't understand how doing that can break the phone forcing me to wipe data and flash the phone.
Hope someone can help. Thanks a lot!
PD: After rebooting the phone in recovery mode i can see stock recovery has been installed with last update. Hope someone can make a bit of sense about it all. Thanks in advanced.
sibok said:
Hi,
i'm looking for a stock firmware for my SGS3 BaseBand I9300XXLH1 but i'm not able to find it. I think the firmware which came with my phone is unbranded and from Spain. But the question which i'm wondering is, do i really need to flash the phone? Isn't possible to solve the issue in another manner? After updating through OTA the rooted device, what's supposed to went wrong?
Lastly, what's wrong on updating a stock rooted firmware using Phone/Android update system? Don't understand how doing that can break the phone forcing me to wipe data and flash the phone.
Hope someone can help. Thanks a lot!
PD: After rebooting the phone in recovery mode i can see stock recovery has been installed with last update. Hope someone can make a bit of sense about it all. Thanks in advanced.
Click to expand...
Click to collapse
Get your firmware from here http://www.samfirmware.com/
then use odin to flash it, I had the same problem
Baseband is modem not firmware.
jje
Sent from my GT-I9300 using xda premium
Thanks to both for your answers. Maybe it's stupid but i'm some what more peaceful knowing other people also happened the same issue although it still feels very weird. All i did is flashing with CF-Root 6.4.
I've been looking for the stock firmware which is supposed to came with my phone at sammobile site but i'm not able to find it, although at that point ( where the phone got the same update twice, 4.0.4 ) i don't think i can trust the information provided by the phone. Under phone settings i can see Model Number is GT-l9300 and Base Band Version is i9300XXLH1 but i can't find it no sammobile site. What i find at sammobile site is I9300XXBLH1 ( notice B letter ) but i think that before this weird behaviour happened the phone showed Base Band Version I9300XXBLFB.
Is it all possible or the weird one is me?
Kickasskev, did you got 4.0.4 update twice?
Thanks again to all!
REPEAT BASEBAND IS NOT FIRMWARE nor is it firmware version .
To locate firmware try CHECKFUS .
Or stock providers roms from the sticky on XDA .
jje
sibok said:
Hi,
i bought a Samsung Galaxy S3 GT-I9300 about two months ago, it's a Spanish device. I think the device came with 4.0.1 update of ICS, some weeks after buying it got 4.0.4 update and then using CF-Root 6.4 and Odin 1.85 managed to get root access so i was able to install busybox and UMS application from xda forums. So everything was working fine. Then, about 3 days ago i got an update notification which showed me a message which said "Updates will be provided in the request order preference" or something like this, i tried to update a few times more but no luck, i always got the same messages so i thought i had to wait for 4.1 update to get published but anyway everything was working fine.
The curious thing is yesterday ( August 25, 2012), when i woke up i noticed a firmware update was ready to be installed so went through it (without uninstalling CF-Root 6.4, supersu, etc.) but the strange thing was, after the update completed fine, went to settings to check the version and i saw it still/again was 4.0.4 version of ICS. Also noticed Google Play Books and Google Play Movies got installed so on one hand it seemed everything went fine cause new apps were there and everything worked as expected but on the other hand i think i already had 4.0.4 update installed on the device. Till that point one can think i got confused on the versions i got installed before the update and no major problem here. After that, as i already had root access on the device, i went to check if i still could run UMS app but it complained about missing root access so as i did before that last Android update took CF-Root 6.4 and Odin 1.85 to flash the device and get root access again (Without removing any previous install of CF-Root, super su, busybox, etc. ) but had no luck, so now it's not possible for me get root access again but i'm also still wondering how is it possible that today's update left the phone with the same Android version as before the update.
The only explanation i can find is the phone came with 4.0 version, first update got me to 4.0.1 and today's update guided me to the 4.0.4 but i'm still wondering why root access is not working as it should.
So my questions are, did i got confused about each version update? Then why can't i get root access again just repeating the same first process?
When opening busybox i can read "Not Enough Free Space in /system". Opening /system directory with Root Explorer i can read 1.05GB used, 436.39MB free. Is it right /system directory takes up to 1GB of the space? Why Busybox thinks there is 0.0MB free there?
Hope someone can help. Thanks in advanced!
Click to expand...
Click to collapse
0. Remove all root apps from your phone.
1. Back up your rooted rom in cWM.
2. Use triangle away to get rid of the traingle.
3. Format system and cache.
4. Flash an official rom.
5. You should have all your apps + settings on a stock rom without the status being 'modified'.
victorator said:
0. Remove all root apps from your phone.
1. Back up your rooted rom in cWM.
2. Use triangle away to get rid of the traingle.
3. Format system and cache.
4. Flash an official rom.
5. You should have all your apps + settings on a stock rom without the status being 'modified'.
Click to expand...
Click to collapse
I've used checkfus and now i know my firmware.
Thanks for the step by step tips, but my phone is not rooted so i cannot use cwm, triangleapp and so. I. Annot also remove cwm manager nor supersu. I suppose i'll have to flash stock firmware first of all. Am i right?
Pretty strange, first time i rooted the device through cf-root6.4 it run flawlessly, but now i had to remove the battery after flashing ( while device was on ) and enter into recovery mode by hand which started the rooting process.
Thanks!
Hi guys,
I am experiencing a problem I dont find any answer to but which may happen to others, too.
I got my new S3 one week ago and for beginners, i didnt want to flash a whole rom. As i was coming from HD2, I wanted to give TouchWiz a chance. I used the SGS3 Toolkit though to root/busybox/cwm all, as nothing is more terrible than an unrooted phone =D.
My problem today is, that my phone just told me there is a Samsung update available to install (~91MB downloaded) and if I wanna do it now -> YES. Phone reboots to CWM and asks me if I really want to install the update, which didnt work then. My guess is, that my "original" Samsung ROM intended to use my (not available) "original samsung recovery" and cwm couldnt handle this request.
Can I create a update.zip to falsh it with cwm or is there any other possibility to flash the update WITHOUT getting a custom Rom?
Thanks allready!
Cmoe
:EDIT: I found the possibility using KIES but it tells me there might be problems with rooted phones. As I hat 4 build to chose from when rooting the phone with toolbox, is it better to first unroot it with toolbox, then appliing the update and then reroot again?
As per thousands of same posts remove root first .
jje
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
Hi, so I tried searching but I couldn't find anyone with the same problem.
So I upgraded Android 4.1.2 to 4.3 a couple of days on my galaxy s3 & I noticed that the root was gone with the update, little did I know that there was this awesome new Knox software (solving problems by creating new ones, heh) which would prevent superSU from starting after rooting. Not to mention this amazing Samsung program also wouldn't start on rooted devices so there was no way I could uninstall it either.
So I realized I had done a mistake and did a hard reset, however, when the phone started again I saw that SuperSU was still there and I was getting the same error as before & Knox (would you believe it) still refused to start. So I heard that my only option now is to flash my Galaxy S3 with 4.3 with Odin to clean it completely, however I'm not able to find a Rom to do it with ever since SAMSUNG released the update in KIES.
I don't really care for Knox and would like it gone completely. I just want my phone to work again with root, my warranty already ran out anyway.
Any help appreciated. Thank you.