Hi,
I have asus transformer infinity tf700t and a stock blob of JB. I used blobtools to unpack and repack the blob.
STOCK blob - blob
Repacked stock blob after unpacking - blob_new
I did this just to test the integrity of blobtools. However to my surprise I found that blob and blob_new differ in binary mode. They have exact same size
(du <filename>) but when I open them in binary mode, the files differ a lot.
Is this expected behavior?
I did not change anything in the extracted files after unpacking the original blob.
Please suggest.
regards
shivanand
Related
Hi, i'm trying to flash my custom kernel with CWM recovery. I've seen some zip to update TF's kernel that use a kernelblob but i didn't realized how to create this binary file.
I've compiled kernel from source code from AsusTek files (Eee Pad Kernel Code for Android 3.2 OS (V8.6.5.7)) and i have zImage and modules (.ko).
Someone know how can i pack this things to flash my kernel with CWM?
Coniglioz said:
Hi, i'm trying to flash my custom kernel with CWM recovery. I've seen some zip to update TF's kernel that use a kernelblob but i didn't realized how to create this binary file.
I've compiled kernel from source code from AsusTek files (Eee Pad Kernel Code for Android 3.2 OS (V8.6.5.7)) and i have zImage and modules (.ko).
Someone know how can i pack this things to flash my kernel with CWM?
Click to expand...
Click to collapse
Just to create a CWM compatible kernel zip , it's a combination of the things below:
1) Fetch one of the many kernel zip files like from Roach or Clemsyn that are in the development forum to use as a template. Unzip it somewhere in a clean folder and you'll just be replacing modules & zImage (or whatever it is called, almost certainly *blob* something) then next step.
2) Most of what you need to create the insecure boot image is in here:
http://forum.xda-developers.com/showthread.php?t=1193737
3) Most of what you need to create the new blob is in here:
http://forum.xda-developers.com/showthread.php?t=1068548&highlight=blobpack
4) Now move your new modules from your freshly built custom kernel (do a $find {kerneldir} -iname '*.ko' ). Copy them over /system/lib/modules/* in the unzipped template zip from 1) and get rid of any that you didn't create yourself as well.
4.5) copy the blobpack'd file you created from zImage to whatever it was called in the unzipped zip template (say, boot.img to blob or kernelblob or whatever it was called so the script in the zip works).
5) zip the entire contents making sure you're starting at the right base directory into a new customized zip file. That's it you're done. If it doesn't work you might just have created a bum kernel.
Theory of this in a nutshell. There is no way to do the anykernel.zip method because the tf101 will only accept a blob on those encoded partitions so you have to get the blob and boot tools and use them and since all of the kernel zipfiles use it, you've got easy templates.
I'm not mentioning CWM in here because you would just have to create a bigger blob which is I think covered in any thread you search out that has 'blobpack' in it, like Rayman's. The catch-22 of doing recovery + kernel in one blob is that you have no way to boot the thing should things go haywire, unless you're just talking about CWM and it's kernel.
Good luck -
Hashi
Thanks, I blobbed my custom zImage.
I used this zip update as template: http://forum.xda-developers.com/showthread.php?t=1226717
I'll post this kernel with raw hid input support after testing all the functionalities!
I'm currently looking at the latest firmware update zip file (WW_epad_user_10_4_4_18_UpdateLauncher.zip), hoping it contains driver binaries etc. that could be reused in a custom rom (a script that downloads the latest official firmware and extracts needed bits is legal -- just distributing the drivers and all might not be).
The content is another zip file, that in turn contains a META-INF directory with information and an updater, and one huge file called "blob" that probably contains all we care about.
Has anyone investigated that "blob" file yet?
Unfortunately it doesn't seem to be an ext4 image like what you'd flash with "fastboot flash system"...
If nobody else has done it, I'll look into this more myself, but obviously if it's already been done, no need to start over.
The blob can be unpacked using BlobTools (https://github.com/AndroidRoot/BlobTools). It contains partition images:
PT ... Tegra Partition Table
EBT ... bootloader
SOS ... recovery kernel image
LNX ... Android kernel image
APP ... /system partition
The kernel images can again be split into the kernel itself and the initramfs image, and APP is an ext4 image.
Hi All,
I have just created a flashable file that takes the 10.4.4.25 bootloader and _that's latest kernel packed into one blob
The bootloader is in blob.EBT
The kernel is in blob.LNX
using blobtools
Code:
blobpack -s blob EBT blob.EBT LNX blob.LNX
creates a nice blob that when written into the staging partion updates the bootloader and kernel. 100% working fine
Now why can't I take the latest 2.4.4.0 TWRP or any custom recovery - unpack it to blob.SOS and then
Code:
blobpack -s blob EBT blob.EBT LNX blob.LNX SOS blob.SOS
into one blob and install using the same method.
BTW the updater-script command I am using is this:
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
So can TWRP be 'flashed' from recovery or not. Any pitfalls before I get 'bored' and just do it?
sbdags said:
Now why can't I take the latest 2.4.4.0 TWRP or any custom recovery - unpack it to blob.SOS and then
Code:
blobpack -s blob EBT blob.EBT LNX blob.LNX SOS blob.SOS
into one blob and install using the same method.
Click to expand...
Click to collapse
If you do it correctly, that should work.
I don't understand what you mean exactly with "unpack it to blob.SOS" - you need the recovery in its raw boot image format (starting with "ANDROID!") for the above command.
_that said:
If you do it correctly, that should work.
I don't understand what you mean exactly with "unpack it to blob.SOS" - you need the recovery in its raw boot image format (starting with "ANDROID!") for the above command.
Click to expand...
Click to collapse
Ok i'll have to have a look, But what I meant was that I took the latest twrp.blob and blob unpacked it to give an SOS file.
Code:
blobunpack twrp.blob
results in twrp.blob.SOS
Looking inside that file gives the first part as
ANDROID!
:victory:
Update - it works!
That means I can offer a better upgrade path for when 4.2.1 arrives by making sure that the bootloader and TWRP and stock kernel are all flashed on the first time upgrade
sbdags said:
Update - it works!
That means I can offer a better upgrade path for when 4.2.1 arrives by making sure that the bootloader and TWRP and stock kernel are all flashed on the first time upgrade
Click to expand...
Click to collapse
Damn fine job sir!
Would've hit the thanks button...thanksed out for today though.
Seriously, great work Darren.
sbdags said:
Update - it works!
That means I can offer a better upgrade path for when 4.2.1 arrives by making sure that the bootloader and TWRP and stock kernel are all flashed on the first time upgrade
Click to expand...
Click to collapse
Beautiful work! I can only imagine how much easier it will make it in the future when 4.2.x comes out.
Both for you and for us.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: Cyanogen Nightlies 10.1 or CleanRom 3.4.4 - Depends on the mood .
I have got a properly working stock recovery.img of my Poco X2. Its size on disk is 134mb. But when I unpack and repack it without changing a single thing, repacked image becomes smaller... precisely less than half of original size which is 47mb. Why? I tried carliv image and AIK in windows, mkboot and AIK in ubuntu 20.04. Result was same.
Another issue is that I compiled an ofrp for my device without any error. But the compiled image size is 54 mb. It flashes successfully but doesn't boot (goes to fastboot mode). I had a twrp.img also. It was the same size as of my stock recovery which is 134mb. I just unpacked repacked it like above, its size became smaller to 55mb... then I flashed and it didn't boot to recovery. But the 134mb size twrp.img booted successfully. So what is this problem? How can I keep my recovery image size 134 mb?
@Koken2003
Ask it in AIK thread.
@HemanthJabalpuri
Its not about AIK. Its how can i unpack and repack recovery.img without changing the size. Thanks
Koken2003 said:
@HemanthJabalpuri
Its not about AIK. Its how can i unpack and repack recovery.img without changing the size. Thanks
Click to expand...
Click to collapse
Its not about size that makes it not bootable.
It may strip some bytes of important data(maybe signature) when repacking.
If you ask about this in AIK thread osm0sis(developer of AIK) will observe your recovery.img.
Thanks
Hello,
I have an ASUS K01A tablet with a blank system partition and unusable recovery. I can flash img files to their respective partitions just fine (boot.img, droidboot.img) in fastboot, but 'system' in the stock firmware zip is a directory instead of a flashable image. Of course, this (and other reasons) means I can't just flash the stock firmware in fastboot, nor flash over the entire 'system' directory.
I need a system.img to recover my tablet from softbrick, but I can't for the life of me compile one. I've exhausted every method and tool I could find in both Windows and Ubuntu.
I beseech the community; if there is anyone reading this who could build such a file for me, I would be eternally grateful. I believe I only need the system.img to recover the tablet.
The stock firmware is at the ASUS website. Here is the download link: UL-K01A-WW-12.8.1.41-user.zip.
Thanks in advance!
Why not extract the system folder of the ZIP linked to, then pack it into a ZIP what you then convert to IMG using an online-convertor that does the job?
jwoegerbauer said:
Why not extract the system folder of the ZIP linked to, then pack it into a ZIP what you then convert to IMG using an online-convertor that does the job?
Click to expand...
Click to collapse
"Why not" indeed; that sounds like it would more than suffice. Can you please recommend one?
Anyone? I have been unable to find this "online-converter" despite days of searching; still at square one.
Only as example ( found via Google search !!! )
Archive Converter - Convert your a7z, rar, zip, gzip, bzip2, tar archives to another format online
Free Archive Converter. Convert your archive files to a7z, rar, zip, gzip, bzip2, tar format online for free using OnlineConvertFree.
onlineconvertfree.com
jwoegerbauer said:
Only as example ( found via Google search !!! )
Archive Converter - Convert your a7z, rar, zip, gzip, bzip2, tar archives to another format online
Free Archive Converter. Convert your archive files to a7z, rar, zip, gzip, bzip2, tar format online for free using OnlineConvertFree.
onlineconvertfree.com
Click to expand...
Click to collapse
Thank you, but I've tried this one and all the others on Google, and none will handle the filesize (~650 MB). It must be purpose-made for Android .img files it seems, which I've been unable to find.
Kehkou said:
Hello,
I have an ASUS K01A tablet with a blank system partition and unusable recovery. I can flash img files to their respective partitions just fine (boot.img, droidboot.img) in fastboot, but 'system' in the stock firmware zip is a directory instead of a flashable image. Of course, this (and other reasons) means I can't just flash the stock firmware in fastboot, nor flash over the entire 'system' directory.
I need a system.img to recover my tablet from softbrick, but I can't for the life of me compile one. I've exhausted every method and tool I could find in both Windows and Ubuntu.
I beseech the community; if there is anyone reading this who could build such a file for me, I would be eternally grateful. I believe I only need the system.img to recover the tablet.
The stock firmware is at the ASUS website. Here is the download link: UL-K01A-WW-12.8.1.41-user.zip.
Thanks in advance!
Click to expand...
Click to collapse
maybe that video helps you...
good luck
solong
speedson
I built it finally using IMGBurn to create the raw img and Sparse Converter to convert it to sparse img fragments.
But now the tab has formatting error, and with -u option, flashing errors (all partitions and imgs now). Ah, well.
Thank you to everyone! Hopefully someone else reading this will have better luck than me.
Kehkou said:
I built it finally using IMGBurn to create the raw img and Sparse Converter to convert it to sparse img fragments.
But now the tab has formatting error, and with -u option, flashing errors (all partitions and imgs now). Ah, well.
Thank you to everyone! Hopefully someone else reading this will have better luck than me.
Click to expand...
Click to collapse
Download the attached file from the link at the bottom of this post and unzip it somewhere on your PC. It is a temporary recovery launcher. We'll come back to it in a moment. Based on your original post I'm assuming you already have your stock firmware downloaded as well as ADB and Fastboot setup. From your stock firmware unpack the following files: fastboot.img, splashscreen.img, and boot.img and place them in your ADB/Fastboot folder. Copy the stock firmware to your sd card (in its original, unzipped form...the way it was when you first downloaded it). Put the tablet in fastboot mode. Run the following fastboot commands from a command prompt.
- fastboot flash fastboot fastboot.img
- fastboot flash boot boot.img
- fastboot flash splashscreen splashscreen.img
Reboot back to fastboot mode. Go to wherever you unzipped the temp recovery that you downloaded earlier. Double click on launcher.bat. Type accept in the window, then type T2 and your device should boot into CWM recovery. Now choose install zip>install from se card>and choose the stock firmware.zip that you previously copied to your sd card then let it do its thing. Once its finished go back to the first page of the CWM recovery that you're in and select reboot system now>no>no. You should be golden now. Post back if you have any issues.
Download Disposable Recovery