Related
Hey my evo doesnt want to update it!!?? why??? it reboots.. then i get the loading thing that is starting to do it. but then i get the TRIANGLE WITH THE EXCLAMATION MARK.. with the little Android bOY.. LOL.. Could it be because its rooted? :/
HOPE ITS NOT BECAUSE OF THAT!! :/ HELP PLEASE
You don't need to install the latest 3.70 release...it is just a maintenance upgrade and has no improved functionality ...I hope you made a nandroid bc you can restore that to get back to your previous state. Good luck
Sent from my PC36100 using XDA App
Im new to all this man.. i dont really know anything.. like whats nandroid?? sorry for a stupid question.. but it says is has the Swype typing thing..
One more question.. what happens if i reset the Whole phone? like with the option it has to reset it to its FACTORY DATA RESET.. WILL IT WORK? OR WILL IT JUST NOT BOOT ANYMORE? OR WILL I STILL BE ROOTED? TH \ANKS
never accept a sprint upgrade with a rooted phone, it will mess your phone up...since you dont know what a nandroid is, im assuming you never made one..you are going to have to restore the phone back to original out of the box and a factory data reset is not the way to do it...
try this ...download the 3.30 release from this site and put in root of sd card http://shipped-roms.com/index.php?category=android&model=Supersonic
EDIT...in order for your phone to see this ..boot into bootloader..when phone is off, hold the volume button down and then hold the power button...the phone will see it and flash and update it...you will be back to stock and not rooted...you will have to re root the phone and then create a nandroid...
read this for more info on nandroid backup http://www.simplemobilereview.com/android-rooted-what-is-nandroid-backup/
to recap..never accept a sprint ota upgrade with a rooted phone, you will mess your phone up (as you already know) and once rooted, always create a nandroid...if you ever mess something up, you can restore that nandroid and restore your phone to working condition
also..once you are rooted and you want to update to the latest sprint over the air updates, search this forums for rooted stock RUU and you can then flash the lastest rom from sprint which is rooted...instead of trying to accept the OTA like you did
good luck
oK.. I WILL DO THAT WHEN I HAVE TIME.. LUCKLY MY PHONE DIDNT MESS UP TRYING IT.. LOL..
oK so installing the ROOTED STOCK RUU.. it will already be rooted, and i can still install sprints updates and upgrades with no problem correct?
THANKS FOR THAT BUD! SOUNDS EASY TO FACTORY RESET THE PHONE THANKS!!
drummer2780 said:
oK.. I WILL DO THAT WHEN I HAVE TIME.. LUCKLY MY PHONE DIDNT MESS UP TRYING IT.. LOL..
oK so installing the ROOTED STOCK RUU.. it will already be rooted, and i can still install sprints updates and upgrades with no problem correct?
THANKS FOR THAT BUD! SOUNDS EASY TO FACTORY RESET THE PHONE THANKS!!
Click to expand...
Click to collapse
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades ...you don't accept any ota updates ever...just flash the most current rooted ruu and you will have the latest sprint updates
Sent from my PC36100 using XDA App
Oooh ok ok.. i think i get it.. THANKS! I APPRECIATED!!
weaselp1 said:
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades ...you don't accept any ota updates ever...just flash the most current rooted ruu and you will have the latest sprint updates
Click to expand...
Click to collapse
Self confessed complete Android/Evo newbie here... I didn't even know how to access the settings on the phone until about 30 minutes ago. I've been working with iPhones since day one and have jailbroken many releases, so I get the general idea. It's actually my wife's "work" Android, and a co-worker of hers rooted the phone at some point. She tried to install the auto-download 3.70.651.1, it failed, and she gave it to me. Pulling the battery and resetting seemed to get things back to working, but now I'm taking over management of this phone and getting things right.
Here is where the phone is:
Nag screens about updated software seen. Update now selected. Update seemed to fail with a triangle/exclamation point, phone locked.
Pulling battery gets a normal reboot. Still get nag screen about "do you want to update"
Settings/aboutphone/software info shows "Software number 3.29.651.5" after failed update
Here's what I've done so far:
On software update screen, chose to "delete update". Rebooted. No more nag.
Turned off "scheduled check" for system software updates in Settings menu.
Figured out how to boot into the recovery menu. Looks like "Clockwork backup" was already installed. (ClockworkMod Recovery v2.5.0.1)
Created a nandroid backup using clockwork.
Rebooted phone
Mounted the SD card to my Mac, backed up the SD card including hidden files.
Verified creation of clockworkmod nandroid.md5 file
A few questions:
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades Is this really necessary? Can I not just find a latest/greatest "rooted ruu" and overlay it on top of my current configuration?
I see some threads with titles like "[ROM] joeykrim-SDX-original-5.1 Odex *Stock Rooted 3.70.651.1* Dec 15th 2010". Is this an example of a "rooted ruu"?
This thread says I need to install "unrevoked 3.2.1" and "unrevoked forever". I'm guessing these are different tools than whatever was originally used to root my phone. Any chance installing them will conflict?
If I go back to a stock 3.3 ruu, what happens to all the applications and info already on the phone? Does it just overlay the software, or wipe everything clean?
TIA for helping an Android/Evo newbie out!
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
I get the "new update available" OTA click to restart and the phone restarts. I get the android with a blue spinning something in his back with the progress bar moving. at about 25% it always changes to the android on his back with a red triangle exclamation point. Nothing happens from here.
I can do a battery pull and get the phone to start fine again.
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
any help?
kegman913 said:
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
<snip>
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
Click to expand...
Click to collapse
Can't help, I'm in the same boat. Trying to think of anything I've done that could be interfering:
Adfree (changes /etc/hosts)
SecureSettings plugin (installs a helper app)
SQLite Installer for root (failed to get this to work; tried to do it manually, forget if I got it )
Maybe there's something else I did that could be interfering too, I forget. At this point I'm wondering if its time to give up on stock and go CM9?
So you rooted your phone, and installed a custom bootloader then kept everything else stock?
My best guess is the custom bootloader is interfering with some permissions being requested by the update. I would go back 100% stock (un-root and reflash the original bootloader) then apply the update with everything locked down just like Big Red likes it.
Make sure you always backup when playing with bootloaders and rooting!
Hope this helps!
i just unlocked the bootloader, this isn't considered a custom bootloader is it? basically, I never did anything custom to it
Did you change your fonts or changed anything with the UI? How about modifying the build.prop?
If you try it again and see the android guy laying down press volume up + power to show the menu. It should list where the OTA failed. (you might have to press that combo a few times)
Report back.
i'll try it a second time when I get home, but volume up and power do nothing, hitting them together, in sucession, holding them both down, holding volume up, down and power do nothing either.......weird
nope, does nothing, maybe the other guy with this prob can confirm?
Hmmm weird. I'm pretty sure you can get the stock recovery to display with a button combo.
You might have to flash the stock image to get the OTA to apply. Something had to have been changed in /system.
Read Efrant's guide on how to do so. http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
kegman913 said:
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
Click to expand...
Click to collapse
You need to flash the stock recovery image. Download the factory image for the build that you are on, extract the recovery.img file, reboot your phone into fastboot, and in a command prompt, type: fastboot flash recovery recovery.img
Have a read of the guide that El Daddy linked to. It may explain some things for you.
Red Triangle - Error info
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
umataro42 said:
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
Click to expand...
Click to collapse
Did you use Stericson Busybox installer?
I also get thus error any help would be great
drummynator said:
Did you use Stericson Busybox installer?
Click to expand...
Click to collapse
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
umataro42 said:
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
Click to expand...
Click to collapse
Well, I have it installed too and I did try to uninstall it, but it still didn't work.
Sent from my Galaxy Nexus using Tapatalk 2
Does anyone know where the downloaded update is stored?
Does anybody know where the downloaded updated is stored?
If they do can I please put the location.
I am willing to try to install the updated downloaded file using clock work mod recovery.
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
efrant said:
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
Click to expand...
Click to collapse
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
drummynator said:
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
Click to expand...
Click to collapse
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
efrant said:
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
Click to expand...
Click to collapse
That looks like the error I got when I did the VolumeUp/Power combination and attempt the update.
/system/bin/gzip is a symlink for the busybox executable. Is there a way to put back stock files for everything that busybox replaced in one go? I have a feeling if I were to figure out how to get the stock gzip back, and try to do the update, that I'd find another system file was replaced by busybox.
My Dinc is rooted S-off and I'm still getting ota update notification. I tried to run the update and it does nothing....
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
PonsAsinorem said:
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
Click to expand...
Click to collapse
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Richard6292 said:
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You have to be complete stock to sucessfully update ota. Just flash the stock 4.08.605.15 rom in the dev section. You'd be getting the same thing, without all the hastle of ruu'ing, updating ota, and then rerooting.
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Richard6292 said:
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Right, if your current rom is not based on 4.08.605.15, then you will get the ota notification. Even if you got the actuall ota to install, it would more than likley mess up the rom, and then you would have to reflash the rom and you would be right back where you started. If you want to stay on your current rom but stop the ota notification, do as i said a couple posts above and edit the build.prop file to make the update server think you already have the latest ota. What rom are you currently on?
Ok, thanks for the help!!
Sent from my PC36100 using xda app-developers app
I am using TOB so can I install the update without messing things up?
joeyz400 said:
I am using TOB so can I install the update without messing things up?
Click to expand...
Click to collapse
No tob has stock apps removed and is deodexed. The ota checks to make sure all original apps and files are present and unchanged. If you wabt to get the actuall ota tou need to ruu to stock 4.06.605.3 and then ota to 4.08.695.2 and then ota to 4.08.605.15. However tob V2.1 has been updated to 4.08.605.15 already.
Experience with this OTA update
I can't post yet to the development forums and I saw that cmlusco was on here so just wanted to share my experience. I have an SMOLED Droid Incredible and I'm rooted, S-OFF on the latest CWM recovery and I was using wildstang's stock ROM from the last update back in November 2011. I got the notification, searched the forums, and ended up installing cmlusco's stock deodexed ROM, after doing all the requisite wipes and checking the md5. My initial experience was great, apart from once when the phone simply died with a black screen and was completely unresponsive. Battery pull solved that. After I was done getting all my apps back on there (mostly via downloading and then for some of them just restoring the data from Titanium Backup), I did a Titanium Backup and a nandroid backup in the recovery. After all of these were done, I started having quite a few freeze issues. I think I had three in a row before I had one while in the process of connecting the phone to my computer. Had to do the battery pull method each time but the last time, the phone must have been right in the middle of mounting to my laptop because all of my downloaded apps were "gone". As in, they were not in the app drawer and all the icons were the default Android icon on the home screens. I think something happened with the freeze in the middle of the mount. If I reinstalled an app from the market and tried to restart it, it force closed. Then, if I uninstalled and reinstalled it, it did work. But I was still getting some force closes so I figured it might just be easier to flash the ROM again, which is what I did.
So now I'm back up and running, and mostly everything is okay. I did get another freeze while installing an app and waited for a while but since the phone was still unresponsive, I did the battery pull again. Stuff is working but I thought I'd share my experience and see if anyone else had something similar happen. Oh, by the way, I also updated to the latest radio but hadn't the first time I used this ROM. And cmlusco, thanks a lot for posting that and being very patient in the forums. If this ROM fails again, I might try Touch of Blue.
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
Thanks, I changed that line and the annoying system update is gone
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
ggoodman1022 said:
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
Click to expand...
Click to collapse
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
Also you must be s-off, or adb pull edit and push the file while in recovery.
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
cmlusco said:
Also you must be s-off, or adb pull edit and push the file while in recovery.
Click to expand...
Click to collapse
I've had s-off since a few days after I got the phone last year.
omniatic said:
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
Click to expand...
Click to collapse
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
ggoodman1022 said:
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
I've had s-off since a few days after I got the phone last year.
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
Click to expand...
Click to collapse
I retried all the methods, and flashed the file mentioned above. Still no luck
Stupid notification pops up over and over and over... Guess I may either have to update, or deal with the notification until October when I can upgrade my phone. Or try flashing a custom ROM, even though I like the stock ROM
You could always flash cmlusco's touch of blue ROM which is an optimized version of the latest OTA, so you wouldn't have to worry about update notifications on that one for sure (at least on the latest version).
http://forum.xda-developers.com/showthread.php?t=1492720
but there are lots of options here
http://forum.xda-developers.com/forumdisplay.php?f=638
So I rooted my s3 t999 so I could get cyaneginemod. I used the flashing rom way, and it didn't work,(i used twerp recovery) it kept saying failed, and then I went to the easier way of installing the rom with, the new cyaneinge mod app, (I'm still rooted). Then after waiting for it too finish my phone rebooted, but cyaneinge was not on it, instead it came with a page that said root missing I clicked on yes fix the missing root, n well nothing happens I was back on touchwiz, superuser was their but Samsung Knox kept it from doing anything but I used supersu to disable it. I thought that knox was keeping the cyaneinge mod app from working, so I decided to downgrade to 4.1 when knox didn't exist, bless that time, but I couldn't since odin kept failing at flashing a stock rom, I did this soo msoon times I went through every firm ware n back to 4.3, it kept failing, im pretty sure its boot locked, but the root is also limited, every time I reboot n go to recovery n leave it asked me if it should fix the missing root, but yes or no, it wont change, n every time I reboot it says optimizing apps 0 of 48, it takes at least 5 min to go through. N after going through every forum, YouTube video, asking friends, I still can't find a solution, n im stuck on a screwd up root version of 4.3 plz help
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
serio22 said:
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
Click to expand...
Click to collapse
i don't remember but I used twrp n as I Was flashing through rom it said failed, same thing when I flashed 4.3 stock firmware on odin later
If you have Kies that will give you problems with Odin. And make sure you have latest twrp
Reflash your current firmware with Odin. Then flash recovery, then the rom. No need to root first.
If the rom flash fails, you need to post the exact error it gives, and attach the recovery.log or theres little we can do to help.
We could start throwing out guesses, but there could be dozens of things potentiality causing your problem.
Hello, my phone recently notified me that a 4.4.2 android OTA update is available (i have a AT&T SGH-i747) however once it reboots, it will get to about 29% complete, then i get the "Update failed" message, and it reboots back into android (4.3) and i was wondering how i could get it to work?
(i'm using stock rom, i've NEVER flashed anything on it before, only thing i've done is root it to use titanium backup, however i used the saferoot thing so as to not flip the knox security stuff)
You need to unroot.
audit13 said:
You need to unroot.
Click to expand...
Click to collapse
do i have to do something special to do that? or can i just click the "Full unroot" button in the SuperSU settings tab to unroot my phone
You also need stock recovery and, preferably, all of the ATT apps on your phone. I have read that removing too many ATT apps will prevent the OTA update from completing.
I have never tried removing root that way so I cannot comment.
You should also make note of the fact that it is possible to have something go wrong during the OTA process which may result in the loss of your data. I recommend at least backing everything up to your external SD card and removing the SD card during the OTA update process.
like i said, i only rooted to use titanium backup to restore a backup for a game save, that's all i've ever done (so if that undid stock recovery, or removed AT&T apps without me telling it to, then how would i fix that)
In that case, just unroot and then run the OTA update. Titanium backup would not alter the recovery or remove apps.
well, i have 5 hours to wait before doing so, after unrooting (using the saferoot unroot.bat file, then using supersu's unroot after that to finish the process as the saferoot program said to do) i went to click check for updates, and instead got "Your device is running the latest version" and "you may check again in 5 Hours 0 Minuties" which i'm assuming is because it failed last night when i tried to update it?
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
audit13 said:
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
Click to expand...
Click to collapse
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
logoster said:
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
Click to expand...
Click to collapse
sorry for double post, just checked download mode, says i'm completely stock and official
also thought i'd mention that the check again later timer is going down, it's at 4 hrs and 3 minutes
You could also try booting into recovery and wiping cache and Dalvik. Don't wipe data.
nope, still has a timer, but it's fine as it is going down, i have about 2hrs and 47 Mins left according to it
Sorry for double post again, but timer finished, and update worked flawlessly, so unrooting did work, thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app