Related
The OTA update for GRI54 was downloaded by my phone, however because I use Clockwork Recovery the update Google update procedure did not work.
Anyone know where I can manually download to GRI54 update to 2.3.4 (GRI40 isn't working it seems)?
Look in your logcat for download Link and post it here plz.
Sent from my Nexus S using XDA App
Oh yes.. please do post the link
Agreed... haven't seen a GRI54 link yet. Need to get that to MoDaCo Paul ASAP (although he's probably busy watching the wedding)
Unfortunately logcat only seems to show messages since last reboot. And I already rebooted in order to try to get the update installed Also I can't get the phone to attempt to download it again.
May be someone else could check before rebooting their phone?
Could you upload the update itself somewhere?
Do you know where on the file system I can find the update?
i would search on root of your sd card (/sdcard mount point) or in download dir on sdcard?
Or you can just search for .zip files on your sd card with weird file names
Oh.. nexus s does not have sdcard (just USB storage) but the mount point is the same /sdcard
Found it
Unfortunately I can't post URLs yet. So take the GRI40 update URL and replace the filename with:
486786a7fd97.signed-soju-GRJ22-from-GRI54.486786a7.zip
Note: I have not tested this update myself yet. Use at your own risk!
As I see only 2.3.3-to-2.3.4 link is known now, look on AndroidCentral:
GRJ22-from-GRI40: http://android.clients.google.com/p...749.signed-soju-GRJ22-from-GRI40.a14a2dd0.zip
Should wait a bit for logcats from other versions.
SanjuroE, where did you find it, aren't there GRJ22-from-GRH78C ?
Downloading... will update you all as soon as I apply this.
Grab it from here
I found it in my /cache directory. My phone was at GRI54 when I bought it, so I don't have any other updates.
SanjuroE said:
Found it
Unfortunately I can't post URLs yet. So take the GRI40 update URL and replace the filename with:
486786a7fd97.signed-soju-GRJ22-from-GRI54.486786a7.zip
Note: I have not tested this update myself yet. Use at your own risk!
Click to expand...
Click to collapse
Just to make clear.You download it or comes as an ota update after chcking from you phone for the update (This is what i understand from your first post)?
Ok just saw your last post
emdzej said:
Downloading... will update you all as soon as I apply this.
Grab it from here
Click to expand...
Click to collapse
Does that one work with Baseband version I9023XXKB3 aswell?
haltemien said:
Does that one work with Baseband version I9023XXKB3 aswell?
Click to expand...
Click to collapse
I am not sure. But that is also my baseband version.
Signature failed...
emdzej said:
Downloading... will update you all as soon as I apply this.
Grab it from here
Click to expand...
Click to collapse
Tried to install on my Rogers (Canada) Nexus S that is currently on GRI54 and got a signature failed... any clue why that would be?
your infor is very confusing, your first post say it was download through OTA, then in your other post you say it came with the phone.
Pitrick said:
Tried to install on my Rogers (Canada) Nexus S that is currently on GRI54 and got a signature failed... any clue why that would be?
Click to expand...
Click to collapse
It has faild for me also.
I have i9023, maybe its for i9020?
kms108 said:
your infor is very confusing, your first post say it was download through OTA, then in your other post you say it came with the phone.
Click to expand...
Click to collapse
He said that he bought the phone with GRI54 and he found the link after the ota upgrade in the /cache directory....if i understand correct
emdzej said:
It has faild for me also.
I have i9023, maybe its for i9020?
Click to expand...
Click to collapse
I have i9020A ...so it doesn't work on both...
Got an update notification last night for 3.14.531.17 (19.72 MB). I'm running Unknown's ROM 1.7.1 so I thought this was a bit strange. Has anyone else received this update?
Anyways, here's a link to the update file for anyone that's interested and intrepid enough to try it. https://www.dropbox.com/s/ajueet3ta...e_320853foljnqxv82dc62l1.zip.20263.enc?v=0mcn MD5: af450b9f70e14fd01798031e7c52228e
So far I have not run it. I am on CID: T-MOB010, S-OFF for anyone that's curious.
Your file is corrupted.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
no its encrypted that is what the .enc at the end is.
mkinney88 said:
no its encrypted that is what the .enc at the end is.
Click to expand...
Click to collapse
Oh yeah. Forgot about that encryption crap that HTC has.
hasoon2000 said:
Oh yeah. Forgot about that encryption crap that HTC has.
Click to expand...
Click to collapse
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
mkinney88 said:
can you remove the .enc from the ota.zip.enc cause i know there is a program to remove the encryption from RUU ROM01.zip but i don't know if it works on the OTA zips cause the RUU ROM01.ZIP that is encrypted doesn't have the .enc at the end.
Click to expand...
Click to collapse
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
hasoon2000 said:
Your file is corrupted.
Click to expand...
Click to collapse
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
mongoosesRawesome said:
I just deleted the file, ran the update check and downloaded again, and I'm getting the same file - MD5 matches. So if it's corrupted, then it's likely the source file that's corrupted.
Click to expand...
Click to collapse
i wonder if you try to run the update and when it reboot it will unencrypt it and before it errors out you and adb pull from a temp folder or something
---------- Post added at 03:46 PM ---------- Previous post was at 03:36 PM ----------
hasoon2000 said:
Just tried it right now actually and it says "Invalid HTC AES encrypted zip file". I'm not very familiar with Ubuntu but I have decrypted a few RUUs before, just not OTAs.
Click to expand...
Click to collapse
did you try and remove the .20263.enc off the end and try decrypting it
mkinney88 said:
its not corrupted its just encrypted, ill keep trying to check for an update but i don't get anything. I even ran the RUU and still no dice??
did you try and remove the .20263.enc off the end and try decrypting it
Click to expand...
Click to collapse
Yup. I'm thinking of ways to decrypt it
hasoon2000 said:
Yup. I'm thinking of ways to decrypt it
Click to expand...
Click to collapse
any new ideas?
mkinney88 said:
any new ideas?
Click to expand...
Click to collapse
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
hasoon2000 said:
I renamed it as update.zip and attempted to flash it. It failed. My One S is completely stock since I'm going to sell it. So it may be a bad download or something. Not too sure.
Click to expand...
Click to collapse
It's definitely weird, I'll give you that. Especially since I haven't seen anyone else receive this update OTA. I just deleted, rechecked for updates, and it downloaded again, and I checked the MD5 with the previous file, and it matched, again, so we can rule out a bad download. Perhaps a bad source file.
MD5: af450b9f70e14fd01798031e7c52228e
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Lionhardt said:
What does the new update do?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Since no one's been able to apply the update and it's not listed on the t-mobile website, who knows.
My phone is stock, but I haven't received this update. I'm guessing this is supposed to fix the battery drain from GPS always being on when wifi calling is enabled.
HTC has updated their ROM Update page with a 3.14.531.17 RUU.
HTC One S for T-Mobile ROM Update | 6.24.2013
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Anyone who's familiar with ruuveal want to take a crack at it?
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
---------- Post added at 08:00 PM ---------- Previous post was at 07:44 PM ----------
darrin976 said:
I too am running unknown 1.7.1 and am getting an ota update that is 19mb. I as wondering if should run it.
Click to expand...
Click to collapse
My file is named OTA_Ville_U_JB_45_S_TMOUS_3.14.531.17-3.14.531.11_release_320853foljnqxv82dc62l1.zip
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
mongoosesRawesome said:
You guys should upgrade to 1.8.1 here: http://forum.xda-developers.com/showthread.php?t=2250573
It contains the fixes for battery usage and wifi calling. If anything, I think it might be better than ICS. Now if I could only get Google Navigation to work properly in 3D mode (using Waze instead for now).
Click to expand...
Click to collapse
I tried to yesterday unsuccessfully, I am going to try again soon.
Anyone know what will happen if I do this ota update?
The update you are referring to is going to be from T-mobile, so it will not work. What problems did you run into with the 1.8.1 update?
Thought i followed the directions for Rooting. Got the .apk listed and pushed it to the phone. It tries to install and a get Install Parse Failed No certificates. Im stumped
Problem resolved.
swigginpig said:
Thought i followed the directions for Rooting. Got the .apk listed and pushed it to the phone. It tries to install and a get Install Parse Failed No certificates. Im stumped
Problem resolved.
Click to expand...
Click to collapse
Please post up how this was resolved. Looks like I'm in the same boat
tblade2 said:
Please post up how this was resolved. Looks like I'm in the same boat
Click to expand...
Click to collapse
I'm sorry I tried to just delete the post and was not smart enough to find the delete option after I hit edit/delete. I thought I read that this would work after the update but later found that not to be the case. I'm already on 4.4 so I am assuming that that was the problem for me. Sorry I'm no help
Been looking for awhile to root my T-mobile Galaxy Note Edge updated to 5.0.1 lollipop, tried a few none worked, in addition a lot of the links have been removed or taken down. .need help thanks for the help in advance. .
Sent from my SM-G9250 using XDA Forums
did you try the steps in this link?
http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
DudePharaoh said:
did you try the steps in this link?
http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Click to expand...
Click to collapse
Yes and it fails and then I have to use kies to reinstall factory rom?
Sent from my SM-G9250 using XDA Forums
the more detail you can provide us the better we can help you, maybe someone came across the issue you are crossing.. like what error message do you get
did you clear cache, when does the error happen? etc...
DudePharaoh said:
the more detail you can provide us the better we can help you, maybe someone came across the issue you are crossing.. like what error message do you get
did you clear cache, when does the error happen? etc...
Click to expand...
Click to collapse
Okay I'm at work so I do have all the correct zip files and Odin version, but I used Odin and automobile rar. File started Odin and it failed half way through, when I tried it a second time it seemed to get further but failed also, once I unplugged and reboot, a message said the update failed to use kies to complete the update. The kies reinstalled the rom back to factory and I lost everything. .
On CJ's Rooted Device
As far as I know the CF-Auto-Root/TWRP method still works fine in Lollipop.
Curtis_HTC said:
Okay I'm at work so I do have all the correct zip files and Odin version, but I used Odin and automobile rar. File started Odin and it failed half way through, when I tried it a second time it seemed to get further but failed also, once I unplugged and reboot, a message said the update failed to use kies to complete the update. The kies reinstalled the rom back to factory and I lost everything. .
On CJ's Rooted Device
Click to expand...
Click to collapse
If I remember correctly don't go back inro DL mode after CF Autoroot pull the battery and restart then load TWRP into Odin and install and you should be good.
scoobysnack said:
If I remember correctly don't go back inro DL mode after CF Autoroot pull the battery and restart then load TWRP into Odin and install and you should be good.
Click to expand...
Click to collapse
Pretty much. From what I've seen, this has worked on every note edge with an unlocked bootloader on both kitkat and lollipop.
---------- Post added at 05:39 ---------- Previous post was at 05:38 ----------
At this point, if someone could make a sticky that'd be great so we don't have to answer this question every time
jooniloh said:
Pretty much. From what I've seen, this has worked on every note edge with an unlocked bootloader on both kitkat and lollipop.
---------- Post added at 05:39 ---------- Previous post was at 05:38 ----------
At this point, if someone could make a sticky that'd be great so we don't have to answer this question every time
Click to expand...
Click to collapse
Is there a YouTube video on how to do this it would make it easier?
Sent from my SM-N915T using XDA Forums
Curtis_HTC said:
Is there a YouTube video on how to do this it would make it easier?
Sent from my SM-N915T using XDA Forums
Click to expand...
Click to collapse
I don't know about youtube videos but the process is simple and there're at least a dozen extremely detailed instructions all over the Q&A and General forums
---------- Post added at 10:10 ---------- Previous post was at 10:09 ----------
Basically: Flash autoroot, flash twrp. done.
jooniloh said:
I don't know about youtube videos but the process is simple and there're at least a dozen extremely detailed instructions all over the Q&A and General forums
---------- Post added at 10:10 ---------- Previous post was at 10:09 ----------
Basically: Flash autoroot, flash twrp. done.
Click to expand...
Click to collapse
Yeah I tried three different ways and I have rooted multiple devices for years, maybe I'm missing something simple. .
On CJ's Rooted Device
Try vroot or kingroot you can find kingroot at kingroot.net you can vroot at www.mgyun.com/vroot apk there's an apk version and there's a PC version
I have just tryed rooting using vroot as suggested here with no luck, at least with the apk. SM-N915F note edge unlocked on 5.0.1 , any ideas ?
describe your process exactly
Me: ?
I was downloading the app from url mgyun com
And hit root
But it faild
koopg said:
Me: ?
I was downloading the app from url mgyun com
And hit root
But it faild
Click to expand...
Click to collapse
Lolol this process literally takes two mins and their are guides everywhere
jooniloh said:
Pretty much. From what I've seen, this has worked on every note edge with an unlocked bootloader on both kitkat and lollipop.
---------- Post added at 05:39 ---------- Previous post was at 05:38 ----------
At this point, if someone could make a sticky that'd be great so we don't have to answer this question every time
Click to expand...
Click to collapse
I am furious that this simple process has gotten hard for me. I flashed CF auto root, and it failed (as the thread said it would). I went through the steps to flash TWRP and it fails the same way THAT CF auto-root failed. I tried to use the no-download mode option on step 4 instead (like you guys suggested) and my odin just sat there. It was still on, but everything was grayed out. There was no change to my phone and it was still usable.
I rooted this phone no problem when I bought it. I just factory reset it and flashed to 5.0.1. What am I doing wrong?
I just got a "really blue" pixel XL today and I seem to have the problem that so many people are facing, I can not unlock my bootloader
The guy I bought it from said it was the google version, but not 100% sure if it is or not, and not sure how to distinguish if it is or not.
Anyway, to my question, the main reason I bought the phone was to try out Android P, but it seems I can not install it, since my bootloader is lock, correct? and I would assume there is no workaround for this, either?
Thanks!
I could be mistaken, but I think if it's stock software you should be able to flash the file provided by Google.... On a locked bootloader.
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
tember1214 said:
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
Click to expand...
Click to collapse
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
cms062407 said:
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
Click to expand...
Click to collapse
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
tember1214 said:
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
Click to expand...
Click to collapse
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Dup post.
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
Your sure your downloading the ota file and not the factory image ?
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
ohhhhh, that is more than likely it! I didn't see "OTA " files before..but i just googled it, and I see they are different file names...downloaded the OTA now, and about to try to install.
before, I just googled "android p pixel xl" and it brought me to this page... https://developer.android.com/preview/download.html
but the OTA downloads are on a totally different page at https://developer.android.com/preview/download-ota.html
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
cms062407 said:
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
You can't with a locked bootloader haha. Glad you finally got it working
---------- Post added at 11:39 PM ---------- Previous post was at 11:31 PM ----------
Enjoy!!
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Tried side loading old version and no go.
mswlogo said:
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Click to expand...
Click to collapse
Don't think so on a locked bootloader. Are there any issues in particular with P?
Sent from my Pixel using Tapatalk
cms062407 said:
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
mike.s said:
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
Click to expand...
Click to collapse
They will not install on Verizon device without unlocked bootloader.
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
Jazznax said:
Don't think so on a locked bootloader. Are there any issues in particular with P?
Click to expand...
Click to collapse
Been using Android P since it came out. It's my daily driver. Works great. Only thing is now my Samsung gear watch won't work because the app isn't updated for new version of Android.
Pedroking78 said:
I've tried sideloading Android P but it keeps saying build date to old can not down grade??
Click to expand...
Click to collapse
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
joedeuce said:
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Oh that's annoying. Any idea when that might be/how often they typically release updated builds?
Pedroking78 said:
just unlock your bootloader
and you can flash it thats want it did :laugh::laugh:
Click to expand...
Click to collapse
How do you unlock it then?
That's cool and all but personally I'd rather just wait for a new build of P.