Is this the official ADP "RC33" update? - G1 Android Development

My G1, which has been converted to a JF ADP1.1, gave me the following popup message just now:
! A system update is available
-----------------------------
Holiday phone update 2 of 2: This is
a full system update. Your data and
settings will be preserved.
Update now Update later
I'm going to click "Update later" since I don't know exactly what this is.
I searched the XDA Dream forums for "Holiday phone" without finding anything, but if this is something previously discussed I'm sorry for the double post.
I have tried to attach a picture of the screen as well.
~Christopher

I went to Device Info, and clicked "Check for upgrade".
The result was:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Check-in status:
CHECKIN_SUCCESS

grenness said:
Pending upgrade:
signed-holiday_devphone-ota-130444-debug.55489994.zip
Download status:
Completed (200): 45722649 of 45722649 bytes
Click to expand...
Click to collapse
Does anyone know where in the phone file system these files go?
If I can find it, I can probably copy it to the SD card and then attach it to this thread.
~Christopher

so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
i imagine it will just be RC33 for ADP, with Latitude etc.
only one way to find out

Meltus said:
so this update is only for ADP?
any idea what's new in it yet? or have you not updated?
Click to expand...
Click to collapse
I'm guessing this is for ADP only, since my phone (as far as Google knows) is an ADP (converted from a G1 using JesusFreke's ADP image) and the name of the .zip contains *devphone*.
No, I haven't proceeeded with the upgrade, I would like some other inputs from the forum first.
~Christopher

hrm, mine is saying its up to date when I hit the update checker. Guess i'll keep checking, as I would much rather stay on adp code and not run the tmobile.

this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/

kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
So it has the update for "Check for updates". Looks like it probably is the ADP1's answer to the RC33...

kash04 said:
this guy
has the same thing as you
http://andblogs.net/2009/01/new-adp1-images-leaked/
Click to expand...
Click to collapse
I appreciate the link, but JF-ADP1.1 is based off the images you linked to. Whatever the holiday update is is different.
Can you look in /cache and see if you see an update file? I'd love to get a copy. (Also, run 'logcat' and look for urls.)

I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher

grenness said:
I went ahead and accepted the update.
Took two reboots (one was probably the radio upgrade which I had installed several days ago), but now it's stuck on the pulsating android boot screen :-(
~Christopher
Click to expand...
Click to collapse
RC33 takes -forever- to do it's first boot. On the order of 10 mins for some people.
Does 'adb logcat' show anything?

I left it on the table in front of me, I swear it took around 10 minutes before it proceeded with the boot-up, and now it seems to work fine. Has Google voice search and Latitute.
Don't know what's missing - looks like Sansdroid auto-rotate no longer works.
~Christopher

the download url is similar to rc OTA updates , just need to replace filename:
Code:
https://android.clients.google.com/updates/signed-holiday_devphone-ota-130444-debug.55489994.zip

I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.

Is it possible to use this update directly on a ADP 1 with 1.0 image?
A friend of mine has not updated his ADP to 1.1 yet.

jcdekoning said:
I am the one that made a post on http://andblogs.net/2009/01/new-adp1-images-leaked/
I installed both updates and now have Google Latitude en Voice Search available. I tried to look at logcat but the information was not there anymore.
I made a post on the Google Android forum (http://groups.google.com/group/android-developers/browse_thread/thread/4fc696bd66b988f6#) and got responses from JBQ. But I doesn't make sense to me. I want to know if this update is an official one.
Click to expand...
Click to collapse
It is, it just might not be released yet.

cannot upgrade from JF1.41 RC33
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?

endolin said:
after verifying update package...
message: failure at line 4
assert getprop ("ro.bootloader") =="0.95.0000"
Installation aborted.
Which image do I need to be able to flash?
Click to expand...
Click to collapse
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.

thanks for your quick reply.
i'm not familiar with the signing process, therefore I'd be glad to see a modified
release from you.

Disconn3ct said:
It doesn't like the bootloader test. (And you won't be able to go from rc33 to adp1.1 anyway, since the userdata is different.)
If you are comfortable with the signing process, you can unpack it, remove the bootloader line from META-INF/com/google/....../update-script and resign it and it'll work. Alternately, give me a little time and I'll post one with no checks.
Click to expand...
Click to collapse
http://andblogs.net/2009/02/new-adp1-update-official-with-google-voice-and-more/ has the download that does no system checks. So anyone should be able to apply it as update.zip

Related

[OTA] 1.17.531.2 update extracted from device.

.... or maybe download link from google?
Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4
You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.
Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?
Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now
Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.
It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?
If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.
Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App
I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...
I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"

[Q] How to force SNS check for OTA update

Can&How to force SNS check for OTA 2.3.2 update.
Thankyou
You can't. You either get the .zip posted on the thread in General and update manually or you wait.
You can go into settings, about phone, firmware update.
Sent from my Nexus S
kenvan19 said:
You can go into settings, about phone, firmware update.
Sent from my Nexus S
Click to expand...
Click to collapse
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
slowz3r said:
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
Click to expand...
Click to collapse
I thought it forced a check for the update, or at least it did on my Epic.
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
nope, the closest thing you can get to "forcing the phone to get the update" is the
*#*#CHECKIN#*#* method. and even then all the CHECKIN command does is gets the phone to call home to the mothership and say "hi im here"
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
distortedloop said:
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
Click to expand...
Click to collapse
Perhaps it is the difference in where the update is coming from, I've been running 2.3.1 with CM7rc8 for a few days now don't really plan to update
The way to force the NS to get the update is to download the zip and go into recovery and update it. No root, changing recovery to apply.
1) Download it (Search forums for it.. its in General)
2) Rename to update.zip if it isnt already
3) Put it on root of sd card
4) Boot into recovery (search forums, if you dont know how)
5) Apply update.zip
6) Reboot... you're on 2.3.2
NOTE: The file you are downloading is exactly identical to what you would get from the OTA. So you're doing the same thing. When you get the OTA, you're downloading it from the same source. The URL was received from aLogCat.

Question about installing OTA

I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Hi. I don't suppose the end result would be different, whatever method you choose.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335
jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....
jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks
jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.
Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium
athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.
jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.

Oreo update not coming?

InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Samribi said:
InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Click to expand...
Click to collapse
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
4squer said:
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
Click to expand...
Click to collapse
Thank you very much. I will look at it.
Samribi said:
Thank you very much. I will look at it.
Click to expand...
Click to collapse
Please tell if it worked
dany xe said:
Please tell if it worked
Click to expand...
Click to collapse
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
The wwe version has only just been updated so you'll probably get the update in a month or so once the carrier is happy with the release. My advice is to wait. Do not root and s-off for it.
Samribi said:
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
Click to expand...
Click to collapse
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
4squer said:
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
Click to expand...
Click to collapse
I'm looking to the post, and (being S-OFF already) it says that I have to flash a Combined Full Wipe firmware and then the OTA. Does it mean that I will lose all my data?
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
EugeniusD80 said:
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
Click to expand...
Click to collapse
What kind of VPN did you use? What software?
Samribi said:
What kind of VPN did you use? What software?
Click to expand...
Click to collapse
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Thank you very much. It is downloading now. Slow but at least I will have it. Thank you again.
EugeniusD80 said:
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Click to expand...
Click to collapse
Downloaded the first time with VPN, tried to install it, but it didn't work (I had TWRP, and after reboot I got the message that the update was corrupted). I flashed the recovery from the Google Spreadsheet: https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377
using:
Code:
adb reboot download
and then:
Code:
fastboot flash recovery recovery_1.27.400.21.img
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Samribi said:
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Click to expand...
Click to collapse
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
EugeniusD80 said:
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
Click to expand...
Click to collapse
Yes, I will try to do a factory reset this weekend. If it's not working, I will try to follow the instructions on the other post to flash a RUU.
Edit: I did a factory reset, tried to update to Oreo, it still stopped at 24%. I flashed the latest RUU I could find on the spreadsheet, and then after 2 updates I'm finally on Oreo!!!
HTC u11 Oreo update received via WiFi 4 days ago

Oreo 8.1 out of Beta!!!

FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.

Categories

Resources