Trying to figure out how to open up my OTA update.zip and get stuff out of it, all compression/uncompression programs I have fail. It seems like a topic that should have been discussed somewhere but I'm not finding anything useful in search (one thread said to use a tool to "repair" the zip first but that it didn't seem to be the complete filesystem he was expecting so I don't think that's the solution for me).
What I have is the update.zip pulled from the /data/fota folder. I also have some uncompressed blahblah.tmp file from trying to get the update from Kies instead, if that's any easier to extract data from.
The goal is to pull out the stock recovery and other pieces.
Device: Samsung Galaxy Tab3 8" SM-T310 on stock 4.2.2
Related
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
I've tried pulling it from /cache which works.... but not really
when trying to open it I get an error. can't remember exactly what the error was but it's something like "file does not exist"
once I have this file, I'm fairly confident I can create a guide on how to update rooted tabs (and keep root of course) as I've done this previously with the Acer Iconia A700
any help would be appreciated... just need to get my hands on this file whether by download or description of how to properly obtain it.
already tried Samsung's website... there's no downloads of any kind available
if anyone has kies installed maybe you could acquire it from there and upload
Hi all,
just having some problems flashing my tab 10.1 3 p5220.
Kies is refusing to do it as I suspect it is because the rom in it is
currently a german one.
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
I seem to remember being able to do this on the htc and assume
we can do the same with the samsung. This way I hope I can I
reflash it via odin.
Many thanks in advance,
Andrew
Just download a firmware from sammobile and flash through odin
BennyCat said:
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
Click to expand...
Click to collapse
Not sure if you've managed it now?
Anyway here is how you do it, also may be useful for others too, I've done this in the past, although I was doing an emergency recovery instead of an upgrade, this works either way.
I take absolutely no credit for this:
Here is a guide to save the firmware during your kies update,so u can save that firmware for future use .i just copy paste this from some where else
1. On your pc, windows explorer, check the option "Show hidden files, folders, and drivers".
2. Now connect your phone to pc via kies to begin the firmware upgrade.
3. Kies will begin to download the firmware files...
a. The files will be saved under a tmp file called "tmp****.tmp"
(NB: **** can be any letters or numbers, e.g. In my two times of upgrade via kies,
first timethe tmp files was "tmpA4CE.tmp", and on the second it was "tmpD900.tmp"
b. In Windows 7, this tmp file is located at, C:\Users\*\AppData\Local\Temp
(NB: * is the pc user session name, e.g. C:\Users\Spacks\AppData\Local\Temp)
4. When download is complete, kies decompresses this tmp file into a folder called
"tmp****.tmp.zipfolder" and begins the firmware upgrading process.
a. The folder has same name as the tmp file but now with an extention of .zipfolder.
(So scroll through the folders in the same directory to locate it).
b. When kies begins the upgrade process starting from 1% until it reaches 100%,
quickly copy the "tmp****.tmp.zipfolder" to your desktop.
You have about 2 to 3 minutes to do this. Kies will delete the folder once upgrade is 100% (completed).
5. The "tmp****.tmp.zipfolder" contains all the firmware files kies has used to upgrade your phone.
Now you have a backup of official firmware from kies. This is also useful in case kies fails to complete the upgrade process.
Click to expand...
Click to collapse
:good: Credit to & quoted guide by blackperl @ androidforums.com :good:
My Sprint HTC 10 is on a stock rom, but has a custom recovery. I read about it and was told that I can possibly try flashing the update.zip from the OTA update using TWRP to install it without having to do through the mess of flashing stock recovery, relocking, and possibly having my phone format itself from all this. Issue is, I can't figure out where my phone downloaded the update.
I tried reading this post:
https://forum.xda-developers.com/htc-10/how-to/guide-ota-tricks-extracting-manual-t3367449
But the app_fota folder mentioned in that post does not exist.
Any idea where I can find the update my phone downloaded so I can try to manually flash it?
From the link you mentioned, try doing the second method, using the log cat etc.
I don't have root on the stock rom to do that though. TWRP itself is the only root access I have.
you dont need root from what I remember. I have done it in the past using command prompt, it just uses adb. Not the Shell or superuser. It saves the output to a text file and from there, you can CTRL+F the word OTA or FOTA to get the link.
Oh, so the idea is to see where it downloaded the update from and download it directly using my PC?
Can I just download a log viewing app on the phone itself then?
Basically yes. I imagine you can find an app, its just easier to scroll through and find that information using a computer, I find. You dont want the log running too long, otherwise it will have tonnes of information. Even just starting the log, clicking "check for updates" and then stopping it collects quite a lot of data.
But once you have the OTA file, which will look something like this in the log file:
OTA_PERFUME_UHL_M60_SENSE80GP_hTC_Asia_TW_1.30.709.1_R-1.21.709.2_R2_release_477314i6fyk64xlvy886ba.zip
You just add it to this link: http://fotadl-az.htc.com/secure/ so that it looks like this
http://fotadl-az.htc.com/secure/OTA...1.709.2_R2_release_477314i6fyk64xlvy886ba.zip
and you can download it on the computer.
I still can't find where the update was downloaded, the logcat instructions seem to just point to the same folder.
Hello Guys,
i opened the thread in the Question&Answer Forum but somehow i have an different approach now that i learned how to rollback an firmware version with an locked bootloader. i dont know if it is possible, i more want to open like a discussion about it if this would be an thing someone could possibly do (and thats the reason im opening another thread for it, since it is not the same question anymore as in the other thread).
well, you can flash an image like EML-L29 8.1.0.129 to the device via the dload method. this image installs just fine, great. but now.. in my understanding the interesting part is this update.app. this update.app as far as my knowledge goes contains all this img files. you know, kernel system boot recovery etc.. wouldnt it be possible to simply replace the recovery.img with an twrp recovery.img, put the update.app back together, zip it in the necessary update_sdcard file and try to install it? i read about the tool "HuaweiUpdateExtractor", and this handy nice tool is showing the files.
another thought of me is: the installer is *verifying* the update.app somehow. but if it is verifying this file, there must be like a crc-file, some way of telling "this file is original" or "this file is okay". so maybe this is another part of the problem that i would have to take care of. but still i would need to know a lot more about the way the eRecovery works.
my ultimate goal is to solve the bootloader code problem since tackling it with dc-unlock and hcu wont work cause the security patch level seems already too high in the first versions of this phone. im basically search now ways around it - i know, there is actually no way to do it, but this is the reason why im opening this thread in hope to get some clues or ideas - and telling my own. oh and im pretty sorry if this is maybe annoying, i surely dont have any intention of spam the forums or stress too much on this topic (but it got me very interested).
Edit: i read in another board that it is nearly Impossible to switch the img files because they are encrypted. I guess it is not possible with this method so basically.. just ignore this thread. I guess there is really no way.
Also I think they have to do some checksum when flashing, so it's really impossible to just switch files...
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
bender8125 said:
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
Click to expand...
Click to collapse
well the biggest problem may be the image itself that you are trying to flash. if you take it from firmwarefinder, you will get most likely absolutely no success. you need to take one from androidhost.ru, the ones there worked for me. there you just put everything in the dload folder on your USB-Stick. oh and better use an full-OTA, not just an simple ota update, because that wont work (you cant just update a few files when you are already on EMUI 9). and on top of that: backup your phone first, because it is possible that after your downgrade you lose all data on your phone.
oh and another thing if you just want to get back to EMUI 8.1 (not a specific version you wish for), just use hisuite, because they are allowing the downgrade even more easily. the method i mentioned above is if you try to flash a specific version like i did with 8.1.0.120