Related
Hi guys.
My sister has a s3 (4.0.4). She wanted me to update it. (OTA not available). The phone is on 3 (UK). So i plugged it in kies and started to update it. After it had finished i turned the phone on and to my surprise it was asking for an unlock code! I was confused because it was working before the update. What made it even worse was that it hadnt updated to jellybean rather it was still 4.0.4. I was baffled.
So i decided to root it then do an unlock. This worked fine however i don't want the root for my sister as she is not into all this stuff. So i checked online if i could unroot. The only option i found was to a factory reset!. I can't do that as my sister will kill me. So now I'm stuck. Kies won't recognise my phone because its rooted. So what do i do??? I cant update it till its unrooted so I'm stuck.
Can you please tell me if there is any way round this. And how can i get jelly bean?.
Thanks.
keep it rooted and hide the root apps from the app drawer, that way your sister won't use them / mess the phone up.
Only other way is a factory reset + stock reflash i guess. :/
Well if you reeeally want to unroot, then install triangleaway first and do the "traditional steps of removing the binary count".. and then just flash a firmware from sammobile.com
Cheers!
Sent from my GT-I9300 using xda premium
mzr07 said:
Hi guys.
My sister has a s3 (4.0.4). She wanted me to update it. (OTA not available). The phone is on 3 (UK). So i plugged it in kies and started to update it. After it had finished i turned the phone on and to my surprise it was asking for an unlock code! I was confused because it was working before the update. What made it even worse was that it hadnt updated to jellybean rather it was still 4.0.4. I was baffled.
So i decided to root it then do an unlock. This worked fine however i don't want the root for my sister as she is not into all this stuff. So i checked online if i could unroot. The only option i found was to a factory reset!. I can't do that as my sister will kill me. So now I'm stuck. Kies won't recognise my phone because its rooted. So what do i do??? I cant update it till its unrooted so I'm stuck.
Can you please tell me if there is any way round this. And how can i get jelly bean?.
Thanks.
Click to expand...
Click to collapse
Rooting doesnt stop KIES from recognising your phone. It doesnt stop you from updating via KIES. After updating you will lose the root. You are doing something wrong. Also ...your phone is carrier locked so after the update you will have to unlock it again. There are different ways /software for unlocking ....choose a permanent way.....then flashing will not affect your unlock status
Cheers
If you don't want to be rooted, buy an unlock code from your network.
The software methods all require root.
Sent from my GT-I9300 using xda app-developers app
There is no reason to suddenly need an unlock code after a firmware update...
I would check the right version if the Rom you installed.
Unroot is not very complicated, it's mainly erasing the su binary in /system/bin I think and uninstalling super user app.
Hi everyone, I have a quick question. I am currently running Stock ICS rooted with Safestrap 3.11 installed. Can I perform the OTA JB 98.72.16.en. update? I know I should use OTA Rootkeeper to temp unroot before attempting to upgrade. Then restore root after upgrading via the saved backup. Yesterday I tried to install the update but it failed at some point during the process. I did not have Safestrap installed at that time. Not sure if there was something wrong with the downloaded update or not, but I don't want to try again until I know it will work and not screw anything up. Has anyone else updated to JB using OTA from a rooted Stock ICS ROM? If someone can point me to a detailed procedure that would be great. Thanks
I actually just did the same thing. Just beware, the kernel upgrades with the OTA as well, so if you're running any custom ROMS, they may not work with the new update. In order to perform the OTA update, you should unfreeze any bloatware apps you may have frozen with TItanium Backup. I also used Voodoo's OTA Rootkeeper and maintained root without a problem, although I've heard mixed things. I left Safestrap installed when I upgraded, but I don't know if that was a good idea or not.
I actually had problems upgrading with safe strap installed. Gave me a failed update 3 times until I finally un installed. Flashed fine after that. Safe strap does indeed work after for me. That is with the official cm10.1 nightly rom. So far so good. Still dual booting on a phone with a locked bootloader. Ha...
Sent from my large and in charge GN2 using Forum Runner
immikevalentino said:
I actually just did the same thing. Just beware, the kernel upgrades with the OTA as well, so if you're running any custom ROMS, they may not work with the new update. In order to perform the OTA update, you should unfreeze any bloatware apps you may have frozen with TItanium Backup. I also used Voodoo's OTA Rootkeeper and maintained root without a problem, although I've heard mixed things. I left Safestrap installed when I upgraded, but I don't know if that was a good idea or not.
Click to expand...
Click to collapse
UrbanDroid said:
I actually had problems upgrading with safe strap installed. Gave me a failed update 3 times until I finally un installed. Flashed fine after that. Safe strap does indeed work after for me. That is with the official cm10.1 nightly rom. So far so good. Still dual booting on a phone with a locked bootloader. Ha...
Sent from my large and in charge GN2 using Forum Runner
Click to expand...
Click to collapse
So uninstalling Safestrap might be the best bet. I am running a rooted Stock OTA ICS ROM, nothing special, just what came from Verizon. I actually started with Gingerbread 2.3.6, rooted that, and when ICS came along, I did the OTA after temp unrooting with OTA Rootkeeper. Been running that since. Now I just recently got the message on my Razr that JB is available. I tried updating but it failed. I think the download might have been corrupted or something. I redownloaded the update earlier today but have put off updating until posting on here. So i guess I will uninstall SS and then try the update again and hope I keep root. Then reinstall SS after that. If anyone else has any input or ideas please feel free to post your methods and results.
Anyone else have any experience performing the OTA update to JB or installing Stock Verizon JB in some other fashion. I would like to hear about it as I am still a little unsure about performing this update and don't want to lose root priviledges. Thanks.
Well I just tried to perform the OTA JB update again and it failed again. I temp unrooted using Voodoo OTA Rootkeeper, set SuperUser to OTA Survival, rebooted my phone, and then attempted the update to JB and about 1 minute into the process it craps out and gives the triangle exclaimation point and then reboots 30 seconds later. Nothing seems broken, its right back to my Stock verizon ICS 6.16.211.XT912. Of course I am rooted but as i stated in a previous post, I have been rooted since GB 2.3.6 and was able to perform the update to ICS using the same method I tried here for JB. What gives? Is anyone else having these issues. I have seen on other forums something called the DroidRazrUtility which is supposed to update you to JB and provide root if needed. Is this the only option for me? Also if I perform a factory reset will that screw my phone up since it is rooted? Will I lose root if I factory reset it? Will a factory reset then allow me to update to JB with ease? Lots of questions but I want to be sure of what I am doing. Any help is much appreciated. Thanks in advance.
Tried two more times and the update failed each time. I think I am going to try a factory reset and see what that does. As a note I did have CWM Touch 5.8.4.5 installed with ROM Manager but uninstalled both and also had Safestrap after that and I made sure I removed that too. Unless I didn't get it all removed. Is there a procedure to ensure they have been fully removed?
For those of you who are having touble getting JB to load on your XT912 Razr, use the following script by Developer mattlgroff. http://forum.xda-developers.com/showthread.php?t=2192467
Follow the instructions as he says to and it works perfect, to include rerooting using the Razr Blade script. Be sure to not only thank him but donate if you can. Developers like this are a life saver to all us that rely on them to provide us the freedom we deserve on our mobile devices. I spent 2 days doing everything I knew how to do to get JB installed and all to no avail. Used mattlgroff's Droid Razr Utility and life is once again good.
I have a rooted Razr Maxx and can not get the update to work. It has failed 3 times now. Any suggestions?
Sent from my DROID RAZR using Tapatalk 2
lockg300 said:
I have a rooted Razr Maxx and can not get the update to work. It has failed 3 times now. Any suggestions?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
use the link in the post right above yours
Should I do a backup first? If so what is the best for that?
Sent from my DROID RAZR using Tapatalk 2
Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.
I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
santiagorook said:
I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
Click to expand...
Click to collapse
You're posting in a forum for the SCH-I545. That's a Verizon Galaxy S4.
The SPH-L720 is an international phone, You'll need to post on a forum for that particular variant of the GS4 if you expect any help.
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Modify_inc said:
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Click to expand...
Click to collapse
It is perfectly normal. You described the expected sequence for a phone with any custom recovery. OTA updates download then reboot into stock recovery. Absent that ..what you said.
For your update path, I. urge you to visit xda's i747 forum & read up on the controversy & pitfalls of AT&T's OTA 4.3
Look out for:
locked bootloader
Knox Warranty bit
one way upgrade
(on pain of brick)
It's different this time around.