Related
Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.
OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.
neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come
What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails
I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.
but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.
Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**
Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*
DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?
JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Can not we flash back that old RC29 File again ????
The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img
spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang
RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.
syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.
I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30
well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?
How to get back to RC29? by modifying the update script?
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Click to expand...
Click to collapse
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
fluke.l said:
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
Click to expand...
Click to collapse
As soon as you change one byte in the update.zip folder, the update won't verify against the signature, and will fail.
I've tried.
How did you modify the update.zip?
Did you package it in jar way -- which will count the sha1sum of each file and put into MANIFEST.MF?
How do the phone verify the update.zip? by cert files or just check the sha1sum?
Question: what happens, if I try to apply rc29 from SD card (i.e. signed-kila-ota-115247-prereq.TC4-RC19_RC28) after getting RC30 OTA on my G1?
1. update fails
2. update bricks the phone
3. I can have my root back
Does the name _really_ mean that TC4-RC19 is the only thing it will install over?
What checks are actually made before it bootstraps a SD card update.zip?
Can someone comment on the likely result before I get impatient and discover it is #2, please
Doesn't work but doesn't brick
I just tried it. The update will fail, but you won't brick the phone.
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
dagentooboy said:
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
Click to expand...
Click to collapse
Because only {Google,T- Mobile,HTC} have the OTA private keys needed for creating an OTA signed file.
I guess the only hope is google/t-mobile releasing a full update
Downgrade from RC30 to RC29
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Nice to know. Thanks
so if i let it reboot after it installed the update than im pretty much screwed for now?
ChrisAshton84 said:
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Click to expand...
Click to collapse
U Said your Phone taking foreever to get Update
This means you must be on RC19 and phone was trying to get Full RC30 from google.
Becuase of Full update it paused some where and ask you to reboot, Becuase Patch RC30 Update dont ask for it.
Please Explain you Full Situation !!
yup i got stuck with the RC30 update about an hour ago. was dialing a number and it popped up and i accidentally pressed update now! it bites, oh well
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
I'm mad that I didn't decline the update to rc30!!!!!!!
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
Thanks for your reply
hmm, possible reasons
it seems to me (very close to a complete moron) that the updates get copied to a "ramdisk"(4 lack of a better term) then when you see that arrow going into the chip after reboot is when its written from this "ramdisc" to the flash?
maybe its just the hash talkin take it for what it is an educated guess... AKA a theory.
bhang
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
great tip this is bound to help many others, anybody by any chance know when the next update is coming out?
I tried to Simulate Same thing
1. I already had Updated the phone to Stock RC30 and
2. I Copied RC30 on to SDCard as update.zip
3. Started into Recovery Modem and Pressed ALT+S
4. The Phone Started Verifying the File
5. Then i have Format Boot, System Partition
6. Copied some thing to Phone and asked me to Press Home+Back
7. I pressed it and its flahed Radio Image and reboot in recovery ode twice and did something.
In your Case the Phone might have Extracted the Images into Ramdisk but it might didnt flashed it to phone really and between that u got that Reboot Option and Reflashed the Full RC29 again.
We can reflash the same Version as many time we like but we can not flash lower version as the Recovery command dont allow.
If we keep RC30 as Update and remove the SDCard in between and put a new Card with Update.zip of RC29 the phone unmount the SDCard and then it dont detects the new SDCard is inserted and flashes error so Simulating your Process by Swapping 2 SDcard with RC30 and later on RC29 dont work for me.
If i could place RC30 into Phone and then Try to Simulate that it got the RC30 update frmo Internet and in between flash it with RC29 from SDcard might help me. But i am still not sure.
Downgrade from official RC30 to RC29 ?
My try to change some file on my system then my font was brick . But I use recovery mode, update to official RC30 then I phone worked again. But I want to acess my phone again. Please tell me how to downgrade to RC29 from official RC30 ?
DO NOT FLASH THIS UPDATE UNTIL YOU HEAR FROM THE BIG GUNS OR RISK LOSING YOUR ROOT!
Please Be Patient!!!!
Sprint is pushing out a system update this morning with a size 21.43mb
Update Download Links:
http://www.mediafire.com/file/2myavzqygir/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip Thanks Calkulin!
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip Thanks Joeykrim!
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel Version
2.6.29-789bf291
[email protected] #1
PRI Version 1.40_003
PRL Version 60667
Thank you joeykrim for the following:
RADIO - the radio is updated through a radio.diff.
SYSTEM - no system/app files are changed
it appears this OTA is much more extensive than the previous OTA.
this one appears to apply small patches to every application in /system/app. a few are large in size, but most are very small.
it also appears to patch:
16 files in system/bin
etc/wimax/
etc/firmware/fw_bcm4329.bin and (ap)
31 files in framework
28 files in lib
2 files in lib/modules - bcm4329.ko and sequans_sdio.ko
SYSTEM updated files (might be more, researching now):
wifi module - BCM4329B1_002.002.023.0396.0402.hcd
android.hardware.camera.flash-autofocus.xml
android.hardware.telephony.cdma.xml
ton of framework files
libCamera_donut.so
libCamera_eclair.so
Fixes & Bugs:
From user npace: (I extracted and fastboot flashed the kernel zImage. Here's a rundown of the issues that I tested for fixes
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
3. 30 fps cap -- still there
same radio by your title?
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
danon.brown said:
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
Click to expand...
Click to collapse
Even if you rooted via toasts method, i would not update until a custom ROM is put out with the update included. You could lose root ability forever.
Anyone know the location of system updates are stored on the phone? I am trying to locate using the adb shell but have had no luck finding the download yet.
huoter said:
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
Click to expand...
Click to collapse
can you post this OTA .zip?
joeykrim said:
can you post this OTA .zip?
Click to expand...
Click to collapse
Its done downloading, just trying to find the darn file right now. Any ideas?
Awaiting an update zip
Here's the untouched update zip for those that want it. If you want to put it in the OP, feel free to
OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip
huoter said:
Its done downloading, just trying to find the darn file right now. Any ideas?
Click to expand...
Click to collapse
i didn't look into the last one and this is my first HTC phone so im not familiar with their OTA process.
perhaps try /cache? or any type of temp directory on /data or /sdcard?
we know it won't be on /system.
We install this from recovery, right?
herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
I'd recommend not installing it at all until the devs here have had a chance to go through it and release it themselves. You risk loosing your root if you don't. Then follow their release instructions to apply it.
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Shidell said:
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
Click to expand...
Click to collapse
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
donatom3 said:
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
if you've applied this, can you take a screenshot of the about phone -> software versions or manually type all the info up on here?
im wondering about the PRI ...
herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
No, looks like just about all the preloaded APK's are in there, including the Sprint crap. I assume if you apply it as stock you'll get them back, but I could be wrong.
herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
The official froyo release from HTC / Sprint will definitely contain all the "Sprint Junk" and if you've given up root to one of these updates and go to apply that it will all come back. You may never get root again in order to re - clean it up once you apply froyo.
Be patient. It won't take the devs here long to cook up an update for us. Flipz had the rooted .6 update rom out in 24 hours or so...
.....
Just took a look inside the zip file. All the apk files are there, including the sprint junk...
Just installed....all is well with root...
Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?
Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly
Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...
Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!
I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.
Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?
Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one
pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.
exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome
Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.
We all know that users who own AT6T devices are not able to receive OTA updates if they are not part of the AT&T network or are outside the US.
Can someone who uses AT&T capture OTA update url link for Android 11, so that we who are unable to receive OTA updates can manually upgrade our devices ?
Also you can use this "OTA Link" app for capture url,
Edit: to working app properly you need first Clear Google Play Services
I think it would be very useful for the whole community who does not use AT&T services.
Im in the process of doing that. will get a sim from At&t in a few days and follow the guide you provide.
Oh man... eagerly waiting for this...still stuck on April 2020 update
I will send my gratitude beforehand as I am also waiting
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
PesSarmiento said:
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
Click to expand...
Click to collapse
Which of the ways to get the link are you using?
PesSarmiento said:
I need help. There is an update. The phone is downloading over wifi. I can't cancel or pause the update. I'm following the guide and I can't fine any zip or ota file. Installed the app and is not showing any link to copy. I don't know how to cancel the update and start from zero. I only manage to turn off wifi to avoid finish the download
Click to expand...
Click to collapse
I hope no update is installed, so as not to download the update, Turn off wifi or via ADB you can run this command
Code:
adb shell pm disable-user com.lge.lgdmsclientatt
to disable apk for update, also you can stop connection over change DNS to private set for dns anything like "blabla.com" and internet connection will be stopped or go to go to ‘Settings’ → ‘System’ → ‘Developer options’ and turn off the ‘Automatic system updates’ toggle.".
maybe you are not runed logchat before stated uta updating.
if you using apk OTA link app, must be granted permissions via adb.
I'm not sure if it's possible to delete the OTA ZIP that is already in the process of updating, if you can factory reset the phone then remove the sim card, after deleting it will have to download again however prepare according to the old method of capturing the link again.
I did grant permision to the app with adb, I followed the insructions on the guide, I dont know if this is android 11 update or what, doesn't event mention on the update. I turn off wifi to prevent from donwloading the update, the I turn on the wifi and will download automatically I try the ota lext logcat several times after download resume but again I can't find the download adress using all those keywords. I'm going to try again this evening, and yes the automatic system updtaes is off
PesSarmiento said:
I did grant permision to the app with adb, I followed the insructions on the guide, I dont know if this is android 11 update or what, doesn't event mention on the update. I turn off wifi to prevent from donwloading the update, the I turn on the wifi and will download automatically I try the ota lext logcat several times after download resume but again I can't find the download adress using all those keywords. I'm going to try again this evening, and yes the automatic system updtaes is off
Click to expand...
Click to collapse
also you can try with Traffic with Wireshark on the Same Network
I'm sorry. I failed to get that ota link. And that app doesn't work. I try multiple times with the app, even uninstall and installed again granting permissions and nothing. Im on Android 11 already
PesSarmiento said:
I'm sorry. I failed to get that ota link. And that app doesn't work. I try multiple times with the app, even uninstall and installed again granting permissions and nothing. Im on Android 11 already
Click to expand...
Click to collapse
Thank you for your effort.
Maybe these methods no longer work on newer android systems, then the only thing left is to listen to the connection via computer, when I have the will I will study and write a tutorial.
One question, can you ask AT&T support can you get OTA update in roaming ?
Hey all, on Cricket here. Borrowed my friends AT&T sim today and got the notification to update almost instantly. Will attempt to capture the file later today, will post an update.
davolesh said:
Hey all, on Cricket here. Borrowed my friends AT&T sim today and got the notification to update almost instantly. Will attempt to capture the file later today, will post an update.
Click to expand...
Click to collapse
Thanks, a security update came out 2 days ago
I'm not sure how much the described method really works for android 11 because the previous try od user is not successful, study a little how to catch traffic via computer, with Fidder, Wireshark and similar tools
Tried all methods, the download just started automatically when it connected to wifi and is now completed. I tired the app, wireshark, bug report methods and all failed. The update is NOT yet installed, just downloaded. Any suggestions?
davolesh said:
Tried all methods, the download just started automatically when it connected to wifi and is now completed. I tired the app, wireshark, bug report methods and all failed. The update is NOT yet installed, just downloaded. Any suggestions?
Click to expand...
Click to collapse
Unfortunately I have no suggestions, the .zip file cannot be accessed directly without root permissions if ota downloaded.
Thank you for your effort
Don't know how these updates work on these newer devices or what kind of system AT&T use, but normally LG OTA updates aren't zips. Previously if any bigger update, the path was /data/fota/dlpkgfile and if smaller then same on /cache. Updates were possible flashable using LGUP - or maybe if put to the certain path to the /sdcard having .UP as extension and using Hidden Menu's FOTA Test...
Used SandroProxy to catch the urls... server's address was h t t p://dl01.gdms.lge.com:5005/ back then...
Any progress made?
FC06 said:
Any progress made?
Click to expand...
Click to collapse
No, must be captured via computer
Is there anyone here who is on Android 10 and has the ability to update to android 11 or any future update from ATT?
Waiting for the updare, too. If it's possible to update with a ATT sim in other countries, I would buy one via Amazon or something...