When I try to unpack payload.bin it results in a tz.img. does anyone have any idea what might be the problem or am I just missing a step or something.
Seriousfreedom said:
When I try to unpack payload.bin it results in a tz.img. does anyone have any idea what might be the problem or am I just missing a step or something.
Click to expand...
Click to collapse
OK I'm not sure but are you just using the payload dumper file by itself? Or are you using python program with the payload dumper file? Because I've tried to use just the payload dumper file and it didn't work. I had to install python along with the payload dumper file to get all the files.
Payload dumper with python
Same problem here
Mr Hassan said:
Same problem here
Click to expand...
Click to collapse
Well at least I know it's not me now....lol
Seriousfreedom said:
When I try to unpack payload.bin it results in a tz.img. does anyone have any idea what might be the problem or am I just missing a step or something.
Click to expand...
Click to collapse
Try
1.84 MB file on MEGA
mega.nz
just use fastboot enhance https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/
Or just dual boot windows and stop the faffing about with python
Well it won't do it on windows or linux
I managed to get the enhanced fastboot tool to work( well at least it says it is anyway)
It works perfectly on windows
1. Open the firmware zip with WinRAR
2. Copy out the payload.bin
3. Open fastboot enhance and load the payload.bin file.
4. Click extract on any part of the image.
I just got to this config file figured out and see if I can do something...lol
I only had problem with C.20,
python payload_dumper just working fine and I used it for extracting C.21 boot.img
I meant that I couldn't get any of the payload dumpers to work on either one
I got the fastboot tool to work
Seriousfreedom said:
I meant that I couldn't get any of the payload dumpers to work on either one
I got the fastboot tool to work
Click to expand...
Click to collapse
Payload dumper won't work on newer android firmwares, not since android 12
11 was the last version it worked on.
dladz said:
Payload dumper won't work on newer android firmwares, not since android 11
Click to expand...
Click to collapse
I've used it just the other day to get the boot.img to root my phone
Seriousfreedom said:
I've used it just the other day to get the boot.img to root my phone
Click to expand...
Click to collapse
Stopped for me after 11. Simply extracted nothing..
Windows based.
Will the fastboot enhanced tool pull a boot.img from the phone??
Seriousfreedom said:
Will the fastboot enhanced tool pull a boot.img from the phone??
Click to expand...
Click to collapse
No
dladz said:
Payload dumper won't work on newer android firmwares, not since android 12
11 was the last version it worked on.
Click to expand...
Click to collapse
Are you saying fastboot enhance payload dumper doesn’t work? It does work, you just need to tick the box that’s says allow incremental.
It won’t work on ota zips.
Related
I see here and there requests about re-packing boot.img for ZF2.
Here are tools i'm using to re-pack my images for ZF2. This is for Linux. Just unpack attached archive to some directory. Put boot.img (or recovery.img renamed to boot.img) to the same directory and run extract_boot. Everything will be unpacked to boot sub-directory. Then you can modify boot/ramdisk directory as much as you want. When you finish, run make_boot and you will get boot.img ready to flash to ZF2.
Note1:
Generated boot.img set SELinux mode to permissive. This is better mode for modified boot/ROM. It will solve most problems you may encounter on custom ROMs.
Note2:
You HAVE to have unlocked bootloder in order to be able to boot the boot.img.
Note3:
Do not flash modified droidboot.img to ZF2! If somehow your bootloader will re-lock, you won't be able to boot anywhere if all three bootable partitions (boot.img, recovery.img, droidboot.img) will be modified. So, you will get bricked ZF2.
sorg said:
I see here and there requests about re-packing boot.img for ZF2.
Here are tools i'm using to re-pack my images for ZF2. This is for Linux. Just unpack attached archive to some directory. Put boot.img (or recovery.img renamed to boot.img) to the same directory and run extract_boot. Everything will be unpacked to boot sub-directory. Then you can modify boot/ramdisk directory as much as you want. When you finish, run make_boot and you will get boot.img ready to flash to ZF2.
Note1:
Generated boot.img set SELinux mode to permissive. This is better mode for modified boot/ROM. It will solve most problems you may encounter on custom ROMs.
Note2:
You HAVE to have unlocked bootloder in order to be able to boot the boot.img.
Note3:
Do not flash modified droidboot.img to ZF2! If somehow your bootloader will re-lock, you won't be able to boot anywhere if all three bootable partitions (boot.img, recovery.img, droidboot.img) will be modified. So, you will get bricked ZF2.
Click to expand...
Click to collapse
nice..thank you @sorg.. eventho I dont know on how to develop custom kernel..
can only wait for developers to release their custom kernel tester..
<deleted>
Great tool.
+1
Btw can you create same program for Windows?
can i use this to my asus ze500cl?
themonyo666 said:
can i use this to my asus ze500cl?
Click to expand...
Click to collapse
Maybe yes.
Try it.
Any love for windows?
S#@DY said:
Any love for windows?
Click to expand...
Click to collapse
mr_gourav2000 said:
Click to expand...
Click to collapse
Irrelevant reply, but I've got it. Thanks to @cieffe54
S#@DY said:
Irrelevant reply, but I've got it. Thanks to @cieffe54
Click to expand...
Click to collapse
Please share with us.
mr_gourav2000 said:
Please share with us.
Click to expand...
Click to collapse
Check your pm
S#@DY said:
Check your pm
Click to expand...
Click to collapse
Wow
I found this tool that runs under Windows for extracting the Oreo system.img. Just put the system image into the program folder and run the convert.bat. The result is a system.ext4.img with could be opened and extracted with 7zip. You could also convert every other image like cust.img, boot.img, etc. But you have to rename every image to system.img. The convert.bat only works with this name.
Regards
You can just open a command prompt in the same folder as simg2img.exe and run:
simg2img.exe input_sparse.img raw_output.img
Then you can either use the included Ext2Explorer, or extract it using 7zip (this will not keep permissions/ownership).
You can not convert boot/recovery/ramdisk using this. Use Android Image Kitchen for that.
ante0 said:
You can just open a command prompt in the same folder as simg2img.exe and run:
simg2img.exe input_sparse.img raw_output.img
Then you can either use the included Ext2Explorer, or extract it using 7zip (this will not keep permissions/ownership).
You can not convert boot/recovery/ramdisk using this. Use Android Image Kitchen for that.
Click to expand...
Click to collapse
But cust.img worked without problems. Thought it works for every image from the firmware.
Coredown said:
But cust.img worked without problems. Thought it works for every image from the firmware.
Click to expand...
Click to collapse
system, vendor, cust, product, odm and version will convert fine.
For ramdisk/kernel/recovery partitions you need to use Android Image Kitchen as they're not sparse images.
ante0 said:
system, vendor, cust, product, odm and version will convert fine.
For ramdisk/kernel/recovery partitions you need to use Android Image Kitchen as they're not sparse images.
Click to expand...
Click to collapse
Alright, thanks for the information. I will give it a try.
It doesn't work for android 9 .img
D:\convert>simg2img.exe system.img raw_output.img
Bad magic
Edit: I've just extracted system.img with 7 zip
It Finally worked
other methods only extracted apps!
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
stevedat said:
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
Click to expand...
Click to collapse
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Identity77 said:
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Click to expand...
Click to collapse
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
stevedat said:
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
Click to expand...
Click to collapse
I Didnt try with other rom. It has the a and b thing. I got problem with ota because im rooted with magisk. Got into bootlloop. This fastboot thing saves me. And i was able to upgrade to latest.
Can anyone help me here, my phone security patch showing June 5th, how to update it?
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
DanXbix said:
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
Click to expand...
Click to collapse
thx for the step by step, and will this wipe all my data?
edit:i found some guide mention that i need unlock the bootloader, do i need do this first?
Yes you also need to unlock first and will wipe data
DanXbix said:
Download latest ww ota from Asus website. Download payload dumper and extract payload.bin from that downloaded ota.
After payload.bin extracted put phone in fastboot plug typec into side plug of phone and to your PC.
CMD prompt
Fastboot flash boot boot.img
Fastboot xxx xxx.img (xxx change to all img names example above)
Flash all 21 files
Click to expand...
Click to collapse
It worked but during the process, while flashing system and vendor file I got Invalid sparse file format at header magic
Is it normal? The phone is working fine but checking whether it's normal or anything else needs to be done?
It would be very helpful. Thanks
iamgulshan said:
It worked but during the process, while flashing system and vendor file I got Invalid sparse file format at header magic
Is it normal? The phone is working fine but checking whether it's normal or anything else needs to be done?
It would be very helpful. Thanks
Click to expand...
Click to collapse
yes got same issue but there is a raw of this update now in other guide cn to ww thread flash raw you don't need to unlock
hashcheck said:
yes got same issue but there is a raw of this update now in other guide cn to ww thread flash raw you don't need to unlock
Click to expand...
Click to collapse
That one I had with security patch of June 5th and after flashing now I have July 5th security patch.
Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''
SOLVED
dadu1257 said:
Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
What the heck, this one was tuff. There were really less documentation and disinformation around.
So the situation is: How do I get Magisk Root on LineageOS 17?
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
- To get the right boot.img check your LIneageOS installation folder, unzip and look for ''payload.bin''.
- Extracting payload.bin to get boot.img doesnt work with 7zip. For me these steps worked well. When you have the right boot.img you can just follow the guide on magisk for your phone.
Get Payloader Dumber (github)
Get/Install Python (customize installation folder to an accessible place)
Extract Payload Dumper to Python Folder
Copy Payload.bin File from your CustomROM to Python Folder
Open Command Prompt there
Run "python -m pip install -r requirements.txt"
Run "python payload_dumper.py payload.bin"
Voila
(taken from https://www.youtube.com/watch?v=L4AGMqJStEI)
Hope this helps
dadu1257 said:
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
Click to expand...
Click to collapse
Great that you got it solved, but I just want to add a clarification:
The "stock" boot image file that the instructions talk about is simply the untouched (stock) boot image of whatever ROM you are currently using. The instructions even mention that you should extract it from your ROM zip if using a custom ROM...
:good: