Database Users

cant restore phone with ruu 1.29

it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.

I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..

still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu

Have you tried flashing while in quick boot?

sorry to be such a newb. but what is quick boot and how do i get to it

Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.

ok trying that now. and no errors with drivers

still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work

do you have "usb debugging" turn OFF?

I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it

RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.

mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.

flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...

obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?

flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...

obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.

flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.

You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.

flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...

Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.

[Q] OTA 2.2.1 update manually

I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.

Please post questions in the Q&A section.

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?

I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.

I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.

remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot

If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?

remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)

Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.

remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it

Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.

ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.

[Q] Installed rom now phone is broke

Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.

You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App

Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.

THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse

not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.

If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.

mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.

1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.

Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive

adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.

Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.

[Q] Can't Update to Android 2.2 Froyo

I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.

GeNiO426 said:
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
Click to expand...
Click to collapse
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?

i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update

gosunta said:
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
Click to expand...
Click to collapse
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.

Finally working , i replace the file and i did upgrade my phone. Thanks a lot for all the info

I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?

seraphielx said:
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
Click to expand...
Click to collapse
touch the screen at right-bottom and you will see a list. Select update.zip and touch ok

hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
I'm sure there is a solution, but just forget it and install 2.2 SBF.

hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
Yes, I used Root Explorer. I'm guessing by MCFarmfresh's post that there issome sort of original build for the phone? I've looked everywhere for hours all night last night before resorting to asking somewhere, but I couldn't find anything and the "solutions" I've seen all did not work. I kept getting the same errors.
Thank you for replying. If you can help, it'll be very much appreciated.

I have a rooted Bravo and I deleted some of the bloatware, and I received the Froyo update and everytime I download and the system resets I get an error and the update stops. Selecting from memory card doesnt work for me, and I dont have a backup of the original settings to re-install (which I'm not sure how to do that either). If anyone has any suggestions I'm open.

its checking for att apps
if you renamed them name them back to apk

I didn't rename them, I deleted them off my phone.
Sent from my MB520 using XDA App

I don't know much about these things but I would think that would be a bad thing to do...
I was able to get the update to install to my phone but now it is running slow
Any more info on how to fix this issue?

OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.

GeNiO426 said:
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
Click to expand...
Click to collapse
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.

jorgonv said:
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
Click to expand...
Click to collapse
Thanks. I'm not sure what it was, but I switched to my Windows XP desktop (from my Windows 7 Home 64-bit laptop) and the SBF Flash worked perfectly, thanks bandroid, yourself, and others. I really appreciate all of the help given. 2.2 looks and feels a lot better than 2.1 so I'm really happy about that.

MCFarmfresh said:
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Click to expand...
Click to collapse
please send me one too and where do i put it.????

mismisgh said:
please send me one too and where do i put it.????
Click to expand...
Click to collapse
If you will give me your email I can get it to you. For the life of me I cannot figure out hhow to attach files through pm using my phone lol. You can also use the .sbf method to upgrade but I'll definitely get the files to you if you send me your email.

SBF'in it...
Okay....so one of your gentleman above (I'm new to the forum ish) stated that he had deleted some apps off of his OS. I did the same thing with AT&T Hotspot Locator (unfortunately, AT&T was quick on merging this standalone app into MyAT&T so I couldn't get the atthotspotlocator.apk back). I fixed this using the SBF file.
I won't give you the step by step but I can tell you RSD Lite is a free program from Motorola. It's basically the program they use to flash boot SW onto an otherwise dead device.
Don't be intimidated by it because it really is rather easy to facilitate. Just do like I did and YouTube how to load an SBF into a motorola device. You can pause and replay as you go along to assure no errors. Takes like 15 minutes once you've got all the necessary files downloaded.

Well, that lasted long...
Everything was going fairly well until this morning when I clicked on the phone button (default launcher) and tried to go into the dialer, then it just closed every time I tried doing so.
To try to fix this I rebooted my phone, nothing; restored, nothing; factory reset, nothing; re-installed 2.2.1 FroYo via flashing the SBF with RSD Lite and 'apply:sdcard:update.zip' through Android's Recovery Screen, nothing.
When I tried doing the last 2, however, I received these errors (the first one I had with the first problem and the other 2 are new):
E:Can't mount CACHE: recovery/command
E:Can't mount CACHE: recovery/caller
E:Can't mount CACHE: recovery/log
Now, with the "caller" error, I did NOT touch anything having to do with the dialer and whatnot. That I know.
The last time I had problems with my laptop so I tried it on my desktop and it worked, but now I tried the desktop and it still isn't working properly. Some of the features that I had with the update are now gone such as the "third party apps" option and the sliding "lock screen" is now permanently present.
Any help with this is appreciated.

OTA update fail?

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.