Related
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
awnorwood said:
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
awnorwood said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just an added note, as far as I know, you can't switch back to S-ON on this
device, at least, not at the moment.. If they get S-ON to work on these phones,
good, but if not, I'm not overly concerned.
http://forum.xda-developers.com/showthread.php?t=759955
and
http://unrevoked.com/rootwiki/doku.php/public/forever
for details..
Asadullah said:
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
Click to expand...
Click to collapse
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
mercado79 said:
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
Click to expand...
Click to collapse
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Asadullah said:
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Click to expand...
Click to collapse
Good information to know. Thanks Asadullah.
I was waiting to update the baseband until after the OTA rollout once it was available through the LG tool. But when I plugged into USB to do the update, I found out I've got a USB connector issue and I can't connect properly anymore. I've tried enough to feel fairly confident that it's a hardware issue at this point.
I can however connect in APX mode without issue, so I can flash back to stock ROM and recovery. Is the OTA update still available? Seems that's my only option for getting the new baseband at this point.... unless anyone has a better idea?
Thanks....
it might be, i did mine that way at the beginning of June, here is my thread on how i did it, but if your phone is still stock you should be able to go to System Settings/About Phone and click Software Update.
http://forum.xda-developers.com/showthread.php?t=1696266
I've read through that thread previously. When I restore back to stock rom and recover, I get an authentication error. Now that I did this, I recall reading something somewhere about one of the 4(?) different model numbers not working over OTA for whatever reason.
robbieas said:
I've read through that thread previously. When I restore back to stock rom and recover, I get an authentication error. Now that I did this, I recall reading something somewhere about one of the 4(?) different model numbers not working over OTA for whatever reason.
Click to expand...
Click to collapse
hadn't heard about that. there are some stock nandroids out there (2.3.3) that you can flash like any other rom and try those, but then again if its a model number that isn't allowed, then that won't matter
i guess the lg update tool would be the only way to go then. there are some good threads here on how to do that as well. i just couldn't get it to work for me
I have used towelroot and i changed the look of my software buttons using Softkeyz amd forgot to backup my rom. Will i be able to recive ota updates or will i have to flash my rom with stock first, which i really do not want to do. Just a small question i have been wondering a lot
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Thanks! I suppose i will not be able to get ota without flashing to stock
Please post questions in the Question and Answer section
Thread moved
nikssims said:
Thanks! I suppose i will not be able to get ota without flashing to stock
Click to expand...
Click to collapse
You don't even need to OTA. Beside OTA is the least reliable method of updating. Just wait till the L images are posted or until L custom ROMs come out
So if i wait until L comes out, can i directly flash it instead, using the same flashing instructions from google? From old times of roms as far as i remeber, each rom had its versions of regions, so i had to flash specific region based rom on my phone. Havent done any thing like this for years so sorry for silly question.
nikssims said:
So if i wait until L comes out, can i directly flash it instead, using the same flashing instructions from google? From old times of roms as far as i remeber, each rom had its versions of regions, so i had to flash specific region based rom on my phone. Havent done any thing like this for years so sorry for silly question.
Click to expand...
Click to collapse
Nothing to worry about with Google devices. Just go to Google's site and grab the L stock ROM for your device (D820 or D821) and fastboot it. Done. Or wait for a flashable zip
Ok thanks
Today when I decided to update to the latest android (5.1.1) with rooted nexus 5. I rebooted
my phone and it started installing when suddenly a picture of the android robot with a red triangle sign on top appears and under it it says error so I restarted my phone by holding down the power button for several seconds and when I get in to my phone it says that I'm updated to 5.1. But what I understand that's correct so now I'm wondering how to deal with future updates because I can't afford to brick my phone and I thought I could just download OTA updates normally after root so my question is, can I normally install OTA updates, if not How?
[Edit]Later today I got the update to 5.1.1 message again and its really annoying and I want the update now so how do I get it?
Thanks for reading.
Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.
jd1639 said:
Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.
Click to expand...
Click to collapse
Thank you for answering, I have a nexus 5 but I guess I´ll have to flash the stock firmware if there is no other way that isn´t too complicated.
All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5
jd1639 said:
All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5
Click to expand...
Click to collapse
I just spent 2 hours trying to flash the system but all i ended up with was a factory reset after following this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 so all i want to do now is just getting rid of root so I can update but the guides that i understand doesn´t work because when I tried to flash the hammerhead bootloader it said the my device requires another version. The i took the version that my nexus is in right now 5.1.0 and it appeared to be working so when it was finished I followed the guide and i wiped my system for about 5 minutes and then i chose reboot system from the recovery mode menu. And now im back at where i started.
(Edit) Now I´m installing SDK and following another guide online http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/
It turns out all i had to do was to unlock my phone and then I installed 5.1.1 just fine
Yep, that's the first step. Glad you got it working. I'll close this thread.
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.
Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..
lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.