OTA update fail? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.

HeDsh0t said:
I am running a newly stock, factory restored s4 running 4.2.2. 3 times now I download and attempt to install , but it keeps stopping, rebooting and saying the update failed. What gives?
Any alternate method to update?.
Click to expand...
Click to collapse
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.

leesumm said:
I get the same thing with the wife's S4. I downloaded the update 3 times now in the last month. Each time it shows installed but when verifying the OS and number its the same. So, got on chat with an ATT tech. Seems there is another "hold" on the update, they contacted Samsung tech and the deal is this according to Samsung.
The update comes from Google as an Android update,its up to the carriers to approve the update. Att says it comes from Samsung and its there responsibility to do the update. So where does this go? The usual pass the buck so and so says this. ATT says its Samsung, Samsung says its Google, Google says its ATT. As for the update. Its there but it don't install because ATT stops it with another hold on it.
Click to expand...
Click to collapse
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)

HeDsh0t said:
Really? Hmm, didn't know they stopped it again. Would I be able to side load it using abd? I heard that works. (I know very little about it, but read the thread here)
Click to expand...
Click to collapse
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.

leesumm said:
You can't load something that isn't there. I have yet to find an OTA update to load but keep looking. Att says it will put it out when it gets ready. Only other option you have is to root and go custom. Mine is rooted with TWRP recovery, but as of yet I don't have a custom rom. It's my wife's phone and she isn't into the techy things as I am so I have let it go and when it happens it happens on the GS4. The HTC one I have is all dolled up with unlocked bootloader, S-Off , TWRP, and converted to a GPE model then running a custom rom.
Click to expand...
Click to collapse
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759

dwanhala said:
Grab the file from post 694 in this thread http://forum.xda-developers.com/showthread.php?t=2498897&page=70, change it to .zip and then sideload using the instructions from this thread http://forum.xda-developers.com/showthread.php?t=2529759
Click to expand...
Click to collapse
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?

leesumm said:
I didn't know there was a download of the OTA anywhere. I have been googleing and looking on the XDA for it for a while and come up empty handed in all searches. Now my question , rather than go thru the ADB stuff would it be possible to just copy the file to a folder such as roms , downloads etc. on the internal SD then use TWRP (if installed) to flash the zip ?
Click to expand...
Click to collapse
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?

dwanhala said:
Some people have flashed it from stock recovery from their external sd card, but this does do a full wipe I believe, where the ADB sideload doesn't wipe. Haven't heard of anyone flashing it thru TWRP, you may want to find a version without the bootloaders so that you don't lose the rom flashing ability. I'd imagine that your on MDL?
Click to expand...
Click to collapse
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.

leesumm said:
Yeh, I finished reading the posts then found out it wipes the card , sorry my bad . But still can't get it to sideload successfully keeps saying failed.
Click to expand...
Click to collapse
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.

dwanhala said:
You'll either have to Odin back to stock and do the update, or research the error codes and see what you can do from there.
Click to expand...
Click to collapse
Samsung and rooting is not one of my favorite phones. This is my wife's phone but I rooted it a long time ago , just never did any thing with it so I know very little about it. The sideload failed with no error codes, it wont install from anywhere. From what I am reading any way, I just maybe should leave it alone till ATT gets it together if they do and comes down with a good download. Even the tech on chat yesterday said they pulled the download because of issues but failed to know it was still up for a download.

Related

[FOUND] OTA Update Link!

Just got prompted for a new update here is the link
https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip
Instructions?
if you want to install this you just downlaod it put it on the root of your sd card, than rename it to update.zip than rebbot to rcovery than select apply update.zip.
Im not saying its ok to install this, as for me i am going to wait for a bot till i can look into more.
Mirror Here
Anybody without a corp account try flashing this yet?
i flashed it today and I do NOT have the CorpEmail account. I really hope this doesn't stop me from getting root.
Gimpeh said:
Anybody without a corp account try flashing this yet?
Click to expand...
Click to collapse
i have, no differences at all. battery life will tell in a day or two
So are we safe letting update go thru? Or should we hold off if we want root?
I wouldn't flash it yet. It contains a recovery image and I don't know if anyone knows for certain what's different about the image.
Would this have the correct test keys?
I flashed. Not noticing anything unexpected. Im getting my incredible replaced anyway. Sounds like I'm listening to people talk underwater.
I doubt you'd notice anything different; I'm just afraid that they've closed a useful hole.
Now if this thing would just stop asking me every 20-30 minutes ... grrrr.
The update fixes the email client for business users.
The meat of the update they don't tell you about, however, is there is a new recovery image in the updater. So yeah, maybe a hole was closed.
I held down volume down button and hit power, booted into the prompt, selected "recovery mode," and all I got was a red triangle and exclamation point.
I downloaded the zip, renamed it update.zip, and put it on /sdcard using Astro.
Am I doing something wrong?
I have the exact same problem.
dont do it
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
This whole subject was coverd in another thread.
http://forum.xda-developers.com/showthread.php?t=770091
swindelljd said:
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
Click to expand...
Click to collapse
read the other thread, you need to update to 1.22.605.2 first, easy and does not lose date.
Root and OTA
I have rooted with unrevoked 3.1 but still have stock 2.1. Do I need to unroot to install the OTA or will the OTA still be pushed to my phone while I am still rooted?

[How-To] Install OTA Update on after Root/Custom Recovery

*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?

[Q] Stuck on Downloading Screen...

Before I get jumped, YES, I did do countless readings to the point of going blind with information overload! Rooting phone was a confirmed success after the OTA update, and I did not do any bootloader roms, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), quickly (Samsung logo comes up before with the blue corner text) before this, and it's all that it does now. I think I might have pulled the battery a couple times when I saw the first image, my dumbass fault, as a quick power button push wasn't doing anything to reboot. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. Just looking to get her back to normal
UPDATE
Plugged stock USB cable/Phone in another USB slot, Odin picked it up (See pics), of course I can't downgrade to MDL from MF3.... failure.
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
l33t_killa said:
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
Click to expand...
Click to collapse
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
scott14719 said:
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
Click to expand...
Click to collapse
,
Yep, I missed that tidbit of info, I did try your suggestion from another member via this thread http://forum.xda-developers.com/showthread.php?t=2407443 as I'm getting closer as per my updates there. Going to try out ou812bkewl's method here http://forum.xda-developers.com/showthread.php?t=2360859
MF3 Nandroid Backup
I was able to get a full Nandroid Backup for AT&T S4 with the MF# firmware using an app called OBackup. Im not real sure if any of the files would be helpful to those stuck after trying to install a custom recovery. I think if you could get into download mode and in Odin, these .tar files might be helpful.

OTA push

OK, I must have inadvertantly started OTA and got the must install / delay screen pop up. I froze the smaller update system app to rid the pop up, and removed the update.zip package.
So far 2 weeks of reboots and use age no OTA package installer pop ups.
Is that for your I467 model and are you blocking the KitKat update, or a different model?
On both types... I am not dissabling OTA, as I may want to install 4.4.2 later. Just keeping the blasted install update notice from popping up every so often. It does not effect downloads or app installs, just keeps the notice from being a pain in the arse.
Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?
dandroid7 said:
Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?
Click to expand...
Click to collapse
Not for the i467 as I never connected with AT&T, just rooted and unlocked to use Virgin UK. Though I froze the software update to mirror my GT-N5110 settings.
OK thanks for the response
dandroid7 said:
OK thanks for the response
Click to expand...
Click to collapse
Sent you a message
gooberdude said:
On both types... , just keeps the notice from being a pain in the arse.
Click to expand...
Click to collapse
I thought I had read somewhere that you had both models, it was a pain.
I just couldn't remember how I stopped my pop-up, thanks you.
Quote godzulu
If you have the file would you be willing to post a link so we can download it and work on rooting it?
I'm sure that I have yet to complete a download of the OTA for I467. For years I'd preferred a custom Rom or kernel vs a carrier update - with that being said, how can I Download it & then STOP the installation (i do not want the update without root) & next, locate the zip to get it to you?
I would already guess that you and others have already tried.
***********************
It looks like someone had passed the file along & maybe Da_G is attempting a a workaround, yea!
OK, I realized that I had changed the option in about device to set auto update. If you go into app manager, and clear cache and data in both software update apps, you will reset parameters for FOTA. The nice thing about doing so on the GT-N5110, is that you can select world ROMs. UK GB is what I use, as it has 13 channel WIfI already set.
If you choose automatic, you will get a notice and will ask to install once the download iscompleted. if you do it manually, it will download when you select download.... but you can cancel.
The Firmware is located in System/cache/update, and the fle is update.zip.
If you like to mess with a library of ROMs, you can download as many as you like after renaming and moving them to SD.
As for rooting... Saferoot.zip works fine. there are a few topics that have it downloadable. just search in the Note 8.0 general and Q&A sections.

New OTA update today

Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.

Categories

Resources