hey I have a question
you know, if there is an OTA update, you can get the URL of the update via adb logcat.
my question is, where does the updater look for updates?
you know, there must be some xml file or something that is downloaded and read by the phone, where it finds the URL of the update package.
logcat doesn't give me anything. maybe a sniffer would do?
if it's a xml file, you could check for updates via pc
I'm just curious, trying to understand how the update process works
greetz, JW
Related
I have a quick question I was wondering if someone could answer.
I updated my Atrix but forgot to reset my host file from within Adfree and now I get some ad errors from sites and games that I play. (I did remember to remove root so I wouldn't have a superuser icon floating around.) I would like to reset my host file and I believe my only option would be to flash the original SBF, root, install adfree and reset my host file.
If I don't feel like doing the above and I just wait it out and Moto/ATT releases Gingerbread, will this overwrite/reset my host file?
Hope I made sense and any help or tips would be greatly appreciated.
Hi,
/etc actually points to /osh/etc, /osh is a partition mounted read / write, so something like echo "127.0.0.1 localhost" >/etc/hosts from an adb shell or from a software terminal on your phone would probably do the trick.
Cheers!
Thanks for the response!
I'm not sure if that tip will save me to many steps though since I already ran the latest update I don't have root so I'd still have to flash the stock SBF, re-root, and then use terminal.
If I'm missing something please let me know, I'm still new to this whole thing. The ad errors aren't making my phone unusable so I was hoping by waiting for Gingerbread it would fix my host file once I upgraded to it. Any thoughts if that would work?
I flashed with the stock SBF file and all is fixed.
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
AndrewTL said:
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
Click to expand...
Click to collapse
You need to go through all the lines of code for that and I believe some of them are binary files as well. Possible but will take much time. For now we must wait until someone finds a better solution.
Sent from my Kindle Fire using Tapatalk
signature issues.
6.2.1 experiment?
transfuntioner said:
signature issues.
Click to expand...
Click to collapse
Maybe I don't follow the process.. but I'm guessing no signatures..
not a signed bootloader.. no signatures required...
Get beyond compare and look at the differences between the OTA updates and the zip that Eldarerathis put together.
The ".bin" files are just ".zip" files renamed.
Look at
META-INF/com/google/android/updater-script in the bin files they release.
It is just a script.
And to do the things that it is doing, it has to be getting root permissions while it is running.
I don't know how to recover if it doesn't work, but I half wonder if you were to take the zip that fellow created, change the extension to ".bin" and just dump it into the update folder if the fire would install it for you?
He took out the image files from the script. He's just updating the system tree directly. He doesn't update the bootloader, recovery or backup trees.
For that matter if those contained something nasty, they could probably be pulled from an earlier update.
== cut ===
package_extract_file("recovery.img", "/dev/block/platform/mmci-omap-hs.1/by-name/recovery");
show_progress(0.100000, 10);
package_extract_file("u-boot.bin", "/dev/block/platform/mmci-omap-hs.1/by-name/bootloader");
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup", "/backup");
package_extract_file("backup_userdata.zip", "/backup/backup_userdata.zip");
== cut ===
Please nobody try this idea that doesn't know enough to recover if it doesn't work, because I've not a clue how.
But could someone explain why wouldn't it work?
Worst case the rev might need to be manually edited to bump it one for the script.
Seems like it might be an easy way to get around headaches with OTA updates.
Andrew,
Are you having issues with getting into recovery so that you can test this? The Devolopers have a copy of TWRP 2 working perfectly on the device so you can get a clean backup of the OS before you test.
You sound like you may know what to do to fix the issue and I just want to help you get a good recovery in case it doesn't pan out or for testing.
~enjoy.
Actually I'm just afraid of messing up what I have working now.
I've got TWRP 2 running with the 6.2.1 image.
I'm setting these up as gifts. I spent a good 12 hours yesterday fighting the darn things. Guess I'm getting gun shy. Had a lot of issues with adb. Kudos to the new utility and setting the second ports up. I'm learning.
The OTA install wipes the system directory. It's in the script.
I was tempted to just comment that line out and see if it would leave the rest alone.
If I brick the thing its going to be painful for me to sort out.
I also didn't want to risk losing root. I also haven't tried loading an older OTA version.
At the time, I couldn't ask the fellow that developed the rooted 6.2.1 zip the question in his thread as I didn't have enough posts.
I'm going to be out of pocket for quite some time. I'm not going to have time to spend like this again for at least a few days.
But I was checking the zip he made versus the .bin/.zip files that the OTA releases using beyond compare. I wanted to see what files had actually changed.
That's when I found that script. It is manipulating permissions directly. It has to be running at a root level. I don't see anything like a signature on it, so why couldn't their own update system be used to tweak their own updates to allow for root?
I rooted my TPT with the yet another root exploit method while on version 0089_US, and it worked great. Then I installed RootKeeper and temporarilly unrooted. My TPT is not and never has been modified in any other way, no CWR, no apps deleted, nothing.
When I try to install the OTA ICS update, it will start to install, and then fail with some kind of assert failed error message that mentiones busybox, and then say error in /cache/update.zip.
Anybody know what's going on???
I had the same issues with the ROW update. I followed this thread (thoroughly) and got ICS with root intact.
http://forum.xda-developers.com/showthread.php?t=1723048
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
userno69 said:
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
Click to expand...
Click to collapse
Here's what I needed to do to get busybox restored and access to my stock recovery again:
1. Downloaded a previous update from Lenovo's site. (had to go two versions prior to find one with a busybox file in it).
2. Extract the Busybox file from the archive (system/xbin Directory)
3. Copy the file to your tablet
4. Using ES File Explorer or Astro, copy this Busybox over to the system/xbin Directory on your device. Note: I had trouble here with permissions that came down to a few settings in ES File Explorer (system access, write permissions, etc).
5. Reboot into recovery by pushing Vol + a few times after Lenovo appears.
Hope this helps.
-A
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
garypen said:
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
Click to expand...
Click to collapse
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled). These settings are required to make changes to system files.
EpsilonTheGreat said:
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled).These settings are requibe able to overwrite busybox.
Click to expand...
Click to collapse
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
garypen said:
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
Click to expand...
Click to collapse
I saw the exact same thing after fixing busybox. Glad it worked for you (so far)!
Worked like a champ. Rocking ICS on my TPT with root.
It's really not a huge diff from HC. But, lots of little things that I had become accustomed to on my ICS phone.
The tpt does seem a little faster now. Play store is working better, too.
I just wish I could replace that stupid Lenovo quick app icon with the android app launcher icon, like on my nexus. Why do they locate the apps icon at the very top corner? Makes no sense.
I've tried all the busyboxes that I can find and still no update. Can someone post a working one?
I used the one from the 0086US update.
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Also, I kept root.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0069_0130_US:user/release-keys")
Error in /tmp/sideload/package.zip
Summonabeeeetch!!!! I noticed its the first step of the script... any ideas? Anyone? Maybe Ian not destined for ics :-( any ideas?
daswahnsinn said:
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Click to expand...
Click to collapse
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
Busybox is located in the system/xbin folder.
garypen said:
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
It's located in the system/xbin folder
Click to expand...
Click to collapse
For some strange reason I couldn't get any of the ones from the lenovo site to work, Thank though this should help someone else for sure.
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
ScotchtapeLoser said:
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
Click to expand...
Click to collapse
Which ones did you comment out?
Your Tablet may vary....
I started with
Build.prop
Gmail
Anything starting with Google...
MarketUpdater
MediaProvider
Mediauploader
NetworkLocation
I would comment out the line, add the new updater-script to the zip file. Try it. When it threw out an error I would comment out that line... rinse and repeat
After a time I just became annoyed and comment out all of the apply_patch_check (around 450 lines). I do not advise using this shotgun approach.
bigsnack said:
Which ones did you comment out?
Click to expand...
Click to collapse
ICS OTA install busybox error
Hey guys I didn't want to start another thread because this one is very similar to the issue I am having now. My tablet asks me to install an OTA update but once its about half way done in recovery in spits out some kind of error(check attachment). When it comes to tablets Im a noob but I was wondering if you guys can give me some solid instructions on how to get past it?
Thanks in advance.
Reference this thread:
http://www.thinkpadtabletforums.com...ds-and-development/ics-ota-failing-w-busybox/
I am having an issue applying the JWR66Y update to my nexus 7. I get the following when applying in sideload
assert failed: apply_patch_check("/system/bin/debuggerd", "d8ee8b6a18f902e8842a0bf706a35f4359ef73d8", "led6fc2f1287d0dccdaa4e50b917c0cd3dfa6a")
Thanks for any help
Bumped to keep on main page
Check your private messages.
Groid said:
Check your private messages.
Click to expand...
Click to collapse
I'm having the same problem, and I had to register to ask you to please share
Same hash values in the updater script.
EDIT: I have fixed it myself. I figured out how to use simg2img to unzip and mount the system.img from the factory image download, and from that I was able to grab the original file. Update successful!
Guys this is all well and good, but would it be possible to give a bit more info on how to fix the issue? Pretty please?
I don't have enough post's, so cant post a link.
Search for member AndDiSa and go to his blog, which has a link in his sig.
He has instructions to for extracting a factory image and installing with fastboot.
Has worked for me on the last two updates.
Or just Google for debuggerd, Nexus 7, android 4.3 and xda; there's a thread somewhere here where someone posted a copy. It's how I fixed mine when I upgraded.
Just download it and copy it to /system/bin. Easiest if you can do it in recovery, as Chainfire used that file for some of his software hacks for either Super SU or Stickmount and unfortunately it can get copied over again on boot or reboot.
Sent from my GT-N5110 using Tapatalk 2
Seems i have found a way to capture OTA without need to root for sharing with other people. If any step seems wrong one can correct me. @S0bes and @MarckozZ can take a look if its relevant or not doing so Since i find you guys know more into this.
Disclaimer: I am not responsible for any brick. Shared this just for your information. You may try at your own risk.
As soon as one receives OTA notification.
1. Connect your phone with your PC and Take adb logcat > log.txt
2. Tap "Download" button on your phone to initiate download of update.
3. Press Ctrl+C to stop logcat. Now, look into log.txt file for the URL. Press Ctrl+F and look for keywords like URL. A line will appear something like "http://android.clients.google.com.........546.zip". Now this filename need not be the system_version name Eg: Blur_version.xxx.zip. It may appear as some unknownfilename Eg: 9851455bbsfdxxxxxxxxx.zip
4. Now this URL can be shared to users for downloading the official OTA manually. User can then download OTA via shared URL on their PC and place in their adb folder.
5. Reboot into Stock recovery and select option "Appy update from ADB".
6. Now, from PC do "adb sideload OTAfilename.zip". Where OTAfilename is the name of the OTA file that you downloaded.
This should install the OTA on your phone. Once you see Install from ADB is complete , proceed to reboot.
References: Droid-life and 9to5google
Install Motorola Drivers and Setup ADB . You may Download Motorola drivers and adb tools from this thread. Extract Adb-tools_treibier.zip and get ready for above steps.
Really?wow hope this is real!that would be great
Sent from my VS985 4G using XDA Free mobile app
I think you will need to disconnect the phone before opening that log file..
if not logcat might still want to throw contents in it continuously..
Also it will be good to include a link to guide to setup of adb for Moto G to avoid users coming with any queries related with it.
Pretty interesting if this works its a great find, thanks! I gave your post a thumbs up.
Will definitely verify this method when the Lollipop OTA comes.
This method is known, but thanks, anyway.
Great Post @==vj== ...
Guys whoever gets the update please be kind enough to do this and post the link ......