I'm having troubles getting the payload_dumper to work. If anybody has an image that isn't de2117_c.16 i'd appreciate it!
Fixed by downgrading by installing protobuf 3.20.*
pip install protobuf 3.20.*
Related
So, like an idiot I wiped/data/system to install a new Rom and didn't double check to make sure the file was good. I can get into ClockworkMod no problem but I have my nandroid and various other downloaded Roms on my microsd card. I'm trying to adb push a Rom while in Clockwork but it keeps failing. What am I doing wrong? Tips please? Thanks much!
Bump, Bump
What I'm getting is "Protocol Failure" every time I try to push a Rom zip to my sdcard. Thoughts?
Is it the size of the file? I just successfully pushed a smaller image file.
After much frustration and trial and error, I got this fixed and back up and running. Ended up having a driver issue with ADB. Master Zen's flash script came in real handy and I highly recommend it if any of you run into a similar problem!
Hello,
I use the rooted system.img which is provided in
http://forum.xda-developers.com/wat...everything-urbane-root-how-tos-files-t3243975
But I then get error on doing su from "adb shell" :
Error: only position independent executables (PIE) are supported.
So, I wander if it's becuase I did not program boot.img too ?
On trying to flash boot.img (or recovery.img) both fail to start on my watch. Not sure yet why.
I should also mention that also with system.img I had to manipulate so that the same size of image will be left and I just replaced the files with rsync (not sure if it is the simplest way to do that, but it worked )
So, not the only problem is the error on doing su (from adb shell).
Can anyone help ?
Regards,
Ranchu
Hello guys!
I have Lenovo Tab 3 [TB3-850M], unfortuantely I am trying to deodex the ROM but both methods in SuperR Kitchen failed.
1st Method using oat2dex: It fails and not fully deodex the ROM and gives a list of failed files [look at pictures]
2nd Method using baksmali/smali: It says it "succeeded" but it doesn't as when flashing the ROM it is unbootable as I got (While deodexing) Java Exception error that it couldn't find classes.dex in all the ROM files!
Please I tried all Marshmallow deodexers available on XDA but nothing seems to work, the most about-successful attempt was with SuperR oat2dex and Fulmics Deodexer but I got com.android.phone has stopped working message error loop and other apps such as Maps and Keyboard.
Thanks in advance!
P.S: If you want the system.img.ext4 and boot.img I will upload them on request as my internet is not that fast and you most probably need one from me because the one online doesn't seem to extract [I made mine by flashing the unextractable system.img using SP Flash Tool and make System Image Backup using TWRP and copied it to my PC]
Regards!
Troubleshooting
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
addas4 said:
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
Click to expand...
Click to collapse
I can't do anything about this. You would need to create an issue on the smali/baksmali github repo. Once it is fixed there, I can compile new jar files and update them in the kitchen. Check your deodex log for the smali/baksmali errors you will need to post when you create the issue/s
Android 11 Stock Kernel with Magisk.
Based on SEA Firmware Version 59.1.A.0.485.
Download:
MEGA
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
cosmo_roel said:
Thanks! How did you make it? I did this:
* I downloaded XQ-AU52_Customized EU_59.1.A.0.485-R8B with xperifirm
* It was automatically extracted by xperifirm
* I didn't find anything looking like boot.img, but i saw boot_X-FLASH-ALL-E9C8.sin, which i unpacked with unsin
* The resulting .img (about 67.1 MB) i patched with magisk manager, logs looked positive
However, flashing that created a boot loop. I had to restore original firmware from sony's built-in recovery (back to android 10).
I tried extracting the 67.1 MB img with imjtool. Which results in 4 files: devicetree.dtb, kernelimage, kernel and ramdisk. I thought maybe I needed kernel, but that is only 15.4 MB.
Click to expand...
Click to collapse
Here:
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
Could you describe the complete procedure you did? Does this make possible to have root on stock ROM without unlocking bootloader?
Thanks in advance.
cosmo_roel said:
Ah, turns out I'm far from the first one with this issue. Thanks for the link. I also found the general guide here on xda now. Unpacking boot.img and removing the system_ext did the trick.
Click to expand...
Click to collapse
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Supercharlie25 said:
hi, i actually got the procedure myself. However, when editing the boot img in Android Kitchen, i can´t find the file "fstab.qcom". I have two fstab files, fstab.default and fstab.emmc.
Any suggestion?
Thanks in advance.
Click to expand...
Click to collapse
Hi,
did you find a fix or a solution?
Thanks
EDIT: The fix is to comment the system_ext line inside the two fstab files
Just for reference there are two updates to this issue:
There is this tool by @entr0pia that automatically removes system_ext from the boot image
Magisk finally fixed the issue and it is now available in the latest canary builds!
Refs: Issue on Magisk repo - Commit that fixes the issue
Note: I haven't tested them yet!
Click to expand...
Click to collapse
anyone have any idea how to install incremental updates manually? i have an ota incremental package, have even dumped the contents and have the .img files inside but not sure what to do with them as they are not full partition images just the increments(i guess just the parts that need to be changed of the actual partitions) is there any way to merge them or how else should they be used? i tried to use payload dumper with --diff but that just keeps giving me an error that boot image type isnt supported so i can get all the other files and no boot image with it. if anyone has any ideas i would greatly appreciate it. i downloaded the oneplus software updater to try the local upgrade/update and it just keeps telling to put it in the root directory and i have put the zip and the extracted contents in every directory i can think of to no avail. oxygen updater also doesnt support this device (yet)
nvm i found the answer thanks to someone on tg..
encrypt the incremental with ofpflasher and update