Related
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!
Fixed it myself
andrewt2323 said:
This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!
Click to expand...
Click to collapse
Since I didn't spark enough interest for anyone to offer advice, had to spend most of the afternoon/evening fixing these problems myself. Everything seems to be working, so I thought I would pass along key parts of this hard-learned lesson in case anyone else finds himself in such a situation.
First I booted into adb sideload mode, which is all I could do anyway. I installed philz_touch_6.23.9-jflte.zip and the aromafm.zip. I was then able to boot into a "normal" recovery mode. Aromafm was troublesome, and I eventually had to manually put the zip into place for it to work consistently. These are both WONDERFUL , and I highly recommend them both. Thanks very much to the creators! I used the file manager to find the files that I didn't want to lose, and used ADB to pull the files over to my PC. (ADB pull <source> <target>) Then I did a full wipe and factory reset. That did little other than delete all my data, which I had already copied anyway. The phone still would not boot past recovery.
I tried to use ADB to install a new ROM, but got a variety of errors. My phone being an L720T, there are not many ROM's available, at least not for which I could find functioning links. I finally found a TAR, L720TVPUBNG5_L720TSPTBNG5_L720TVPUBNG5_HOME.tar.md5, and used ODIN v3.09 to install that.
I still need to go back and re-root the phone, and install lots of APPS and restore data, but at least I have a functioning phone, and I can do the rest on my plane ride tomorrow.
I found the information I needed in a variety of posts here on xda developers, and would not have been able to get through this without all the helpful advice posted to other threads. So thanks to all of you for the wealth of information available here!
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.