Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6 Support Thread. - Google Pixel 6

This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img to the phone in /storage/emulated/0/Download ...
ERROR: Encountered an error.
adb.exe: unrecognized option '-'
Aborting ...
Click to expand...
Click to collapse
I'm getting this on Pixel 6. Any idea what am I doing wrong?

dilruk said:
I'm getting this on Pixel 6. Any idea what am I doing wrong?
Click to expand...
Click to collapse
What is your Android platform tools version?
Also can you please share PixelFlasher log? Or everything displayed in the console when you encountered the error.
You should redact your device ID for privacy.

badabing2003 said:
What is your Android platform tools version?
Also can you please share PixelFlasher log? Or everything displayed in the console when you encountered the error.
You should redact your device ID for privacy.
Click to expand...
Click to collapse
==============================================================================
Preparing Package
==============================================================================
Found a previous package oriole-sp2a.220305.013.a3 deleting ...
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: D:\Android\Devices\oriole\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\onedrive\Desktop ...
Unzip time1: 42.51156783103943
Unzipped into oriole-sp2a.220305.013.a3 folder.
Extracting boot.img from image-oriole-sp2a.220305.013.a3.zip ...
Unzip time2: 0.8888261318206787
Deleting boot.img from phone in /storage/emulated/0/Download ...
Making sure boot.img is not on the phone in /storage/emulated/0/Download ...
Deleting magisk_patched.img from phone in /storage/emulated/0/Download ...
Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img to the phone in /storage/emulated/0/Download ...
ERROR: Encountered an error.
adb.exe: unrecognized option '-'
Aborting ...
There you go...

badabing2003 said:
What is your Android platform tools version?
Also can you please share PixelFlasher log? Or everything displayed in the console when you encountered the error.
You should redact your device ID for privacy.
Click to expand...
Click to collapse
From what I see, it fails when trying to copy the boot.img to the phone. Also, how do I see the log file? The one I see is empty

dilruk said:
From what I see, it fails when trying to copy the boot.img to the phone. Also, how do I see the log file? The one I see is empty
Click to expand...
Click to collapse
I see that you have the tool running from one drive folder with spaces.
Maybe that is the issue, please move the tool to a path that does not include spaces or weird characters, see if that resolves the issue, if it does I'll fix it in the next version.
Also see when you do that if the log file gets filled

badabing2003 said:
I see that you have the tool running from one drive folder with spaces.
Maybe that is the issue, please move the tool to a path that does not include spaces or weird characters, see if that resolves the issue, if it does I'll fix it in the next version.
Also see when you do that if the log file gets filled
Click to expand...
Click to collapse
Cool let me try that.
EDIT: Works now. Still nothing in the log though

dilruk said:
Cool let me try that.
EDIT: Works now. Still nothing in the log though
Click to expand...
Click to collapse
OK Thanks for reporting back.
I'll make a fix later today for the path issue.
I'll have to figure out why the log file is empty.

worked flawlessly for me, making the monthly update while keeping root a breeze. THANK YOU

Not sure what I'm doing wrong, but it can't seem to find the unzipped image folder. I even tried manually unzipping it, but the app detects and deletes it. Run as administrator and using version 1.1.3:
==============================================================================
Preparing Package
==============================================================================
Found a previous package oriole-sp2a.220305.013.a3 deleting ...
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
Unzip time1: 0.5752615928649902
ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.
Aborting ...

New release:
March 22, 2022 v1.1.4-alpha release.
Bug Fix: Handle space characters in paths.

thekdub said:
Not sure what I'm doing wrong, but it can't seem to find the unzipped image folder. I even tried manually unzipping it, but the app detects and deletes it. Run as administrator and using version 1.1.3:
==============================================================================
Preparing Package
==============================================================================
Found a previous package oriole-sp2a.220305.013.a3 deleting ...
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
Unzip time1: 0.5752615928649902
ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.
Aborting ...
Click to expand...
Click to collapse
Can you please try with v1.1.4-alph and report back?

badabing2003 said:
Can you please try with v1.1.4-alph and report back
Click to expand...
Click to collapse
Unfortunately, same thing:
==============================================================================
Preparing Package
==============================================================================
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
Unzip time1: 0.08989071846008301
ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.
Aborting ...

thekdub said:
Unfortunately, same thing:
==============================================================================
Preparing Package
==============================================================================
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
Unzip time1: 0.08989071846008301
ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.
Aborting ...
Click to expand...
Click to collapse
If you're willing to help out, I'll give you a build that would try few things to determine the cause of the issue and output more verbose messages.
It won't be the final build, but would help me figure out the issue as I cannot reproduce it.

badabing2003 said:
If you're willing to help out, I'll give you a build that would try few things to determine the cause of the issue and output more verbose messages.
It won't be the final build, but would help me figure out the issue as I cannot reproduce it.
Click to expand...
Click to collapse
That would be great.

thekdub said:
That would be great.
Click to expand...
Click to collapse
Try this one, let's see what output you get.
When you paste the console output, please keep everything intact and just redact the device id.

=============================================================================
Preparing Package
==============================================================================
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
debug: "C:\Users\Kirk\AppData\Local\Temp\_MEI127842\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"
Unzip time1: 0.12499141693115234
Unzipped into oriole-sp2a.220305.013.a3 folder.
Traceback (most recent call last):
File "Main.py", line 422, in on_prepare
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Apps\\PixelFlasher\\oriole-sp2a.220305.013.a3\\flash-all.sh'

thekdub said:
=============================================================================
Preparing Package
==============================================================================
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
debug: "C:\Users\Kirk\AppData\Local\Temp\_MEI127842\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"
Unzip time1: 0.12499141693115234
Unzipped into oriole-sp2a.220305.013.a3 folder.
Traceback (most recent call last):
File "Main.py", line 422, in on_prepare
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Apps\\PixelFlasher\\oriole-sp2a.220305.013.a3\\flash-all.sh'
Click to expand...
Click to collapse
sorry @thekdub
In order to test the app before giving it to you, I had added a line to negate a result, but unfortunately I forgot to remove it before building and giving you a copy.
Please try this one.

Looks like it worked was just waiting on python libraries.
Connect your device
==============================================================================
Preparing Package
==============================================================================
Found a previous package oriole-sp2a.220305.013.a3 deleting ...
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...
debug: "C:\Users\Kirk\AppData\Local\Temp\_MEI51122\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"
Unzip time1: 0.10936474800109863
ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.
Disabling bundled 7zip ...
Trying unzip again with python libraries ...
Unzip time1.1: 49.77444267272949
Unzipped into oriole-sp2a.220305.013.a3 folder.
Extracting image-oriole-sp2a.220305.013.a3.zip ...
Unzipped into C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\image-oriole-sp2a.220305.013.a3 folder.
Unzip time2: 108.96331071853638
Deleting boot.img from phone in /storage/emulated/0/Download ...
Making sure boot.img is not on the phone in /storage/emulated/0/Download ...
Deleting magisk_patched.img from phone in /storage/emulated/0/Download ...
Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img to the phone in /storage/emulated/0/Download ...
debug: "C:\Users\Kirk\Desktop\platform-tools\adb.exe" -s 1A061FDF600H0X push "C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\boot.img" /storage/emulated/0/Download/boot.img
C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\boot.img: 1 file pushed, 0 skipped. 13.5 MB/s (67108864 bytes in 4.749s)
Making sure boot.img is found on the phone in /storage/emulated/0/Download ...
Magisk Tools not found on the phone
Looking for Magisk app ...
Unable to find magisk on the phone, perhaps it is hidden?
User pressed cancel.
Aborting ...

@thekdub
Yes it worked, but it would be slow because it won't be able to use the bundled 7zip.
I'd be curious as to why 7zip is failing on your system, if we figure that out you'd get it to work much faster.
Can you try these steps.
1- Quit the App
2- Launch the APP
3- repeat the package step, you can abort it when it reaches the magisk step
4- But do NOT quit the app, that's because the packaged 7zip gets unpacked into a temporary folder, and each time it is different, so we want to keep the app running, and then look at the logs of the first unzip command.
it would be something similar to this, but the part after the Temp would be different (look for the first debug message)
Code:
"C:\Users\Kirk\AppData\Local\Temp\_MEI51122\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"
You want to remove the debug part, and copy the rest (quotes included, similar to the sample above)
Open a windows command shell and paste it and execute
Tell me what it responds with.

Related

[Q] 7zip for Android?

have anyone seen 7zip for Android?
AndroZip handels 7zip
Sent from my GT-I9000 using XDA App
MiMikri said:
AndroZip handels 7zip
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Unless it is pw-protected.
AllGamer said:
have anyone seen 7zip for Android?
Click to expand...
Click to collapse
I've just compiled p7zip-9.20.1, it's the command line version of 7zip, if you still want it, you can download it from here:
http://dl.dbank.com/c0mtm6i3wa
(sorry, it's a file share site provided by Huawei company in Chinese language, outseas file share sites are blocked by "opening" China government)
Code:
$ uname -a
uname -a
Linux localhost 2.6.35.7-perf #1 PREEMPT Sat Dec 3 17:57:38 CST 2011 armv7l GNU/Linux
$ ls -l /system/bin/7z /data/local/bin/7za-9.20
ls -l /system/bin/7z /data/local/bin/7za-9.20
-rwxr-xr-x 1 2000 2000 1702540 Dec 26 03:37 /data/local/bin/7za-9.20
lrwxrwxrwx 1 0 0 24 Dec 26 03:03 /system/bin/7z -> /data/local/bin/7za-9.20
$ 7z
7z
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=C,Utf16=off,HugeFiles=on,1 CPU)
Usage: 7za <command> [<switches>...] <archive_name> [<file_names>...]
[<@listfiles...>]
<Commands>
a: Add files to archive
b: Benchmark
d: Delete files from archive
e: Extract files from archive (without using directory names)
l: List contents of archive
t: Test integrity of archive
u: Update files to archive
x: eXtract files with full paths
<Switches>
-ai[r[-|0]]{@listfile|!wildcard}: Include archives
-ax[r[-|0]]{@listfile|!wildcard}: eXclude archives
-bd: Disable percentage indicator
-i[r[-|0]]{@listfile|!wildcard}: Include filenames
-m{Parameters}: set compression Method
-o{Directory}: set Output directory
-p{Password}: set Password
-r[-|0]: Recurse subdirectories
-scs{UTF-8 | WIN | DOS}: set charset for list files
-sfx[{name}]: Create SFX archive
-si[{name}]: read data from stdin
-slt: show technical information for l (List) command
-so: write data to stdout
-ssc[-]: set sensitive case mode
-t{Type}: Set type of archive
-u[-][p#][q#][r#][x#][y#][z#][!newArchiveName]: Update options
-v{Size}[b|k|m|g]: Create volumes
-w[{path}]: assign Work directory. Empty path means a temporary directory
-x[r[-|0]]]{@listfile|!wildcard}: eXclude filenames
-y: assume Yes on all queries
Hi lovetide. What kind of compression did you use?
I can't find a way to open it :/
Guys I found another working port of p7zip for android.
I Tried to post a link but becouse i'm a 'noob' here i'm not allowed to.
So you can search for "port2android" at google and you will find it
ilbolza said:
Hi lovetide. What kind of compression did you use?
I can't find a way to open it :/
Click to expand...
Click to collapse
It's not an archive file, it's an executable file, you can execute it directly. It's static linked, so it should work on most Android phones.
lovetide said:
I've just compiled p7zip-9.20.1, it's the command line version of 7zip, if you still want it, you can download it from here:
http://dl.dbank.com/c0mtm6i3wa
(sorry, it's a file share site provided by Huawei company in Chinese language, outseas file share sites are blocked by "opening" China government)
Click to expand...
Click to collapse
Link does demand to pay for it. Can you upload attachment on the forum?
You have to click the link several times. It will work after some time.
But scroll down... Mirror is attached.
Here version 9.38.1 for arm-v7a, 7za is standalone, 7z needs 7z.so in /system/lib, 7zr a reduced version of 7za, Codecs must be in current dir for rar support (optional)
in the archive I've also added makefile.machine if you want to compile from source (you need to replace the one in the source directory, it needs to be edited for paths)
sherpya said:
Here version 9.38.1 for arm-v7a, 7za is standalone, 7z needs 7z.so in /system/lib, 7zr a reduced version of 7za, Codecs must be in current dir for rar support (optional)
in the archive I've also added makefile.machine if you want to compile from source (you need to replace the one in the source directory, it needs to be edited for paths)
Click to expand...
Click to collapse
Thank you very much for this indeed. XDA won't let it download no matter how many times I try, would it be possible for you to post it in a mirror somewhere ?
Edit : Never mind, finally got it. XDA glitch.
Edit 2 : Shoot, this will not run in Android 5 and newer systems... ( Error: only position independent executables (PIE) are supported. )
sorry but I didn't have an arm android 5.x to test it, I'm attaching pie build, I think it should work also on android < 5, but anyway there is still the old attachment in previous post
Hey...
I think the Zarchiver app from the play store would just work.
Hit thanks if I helped you!
ClawSpark said:
Hey...
I think the Zarchiver app from the play store would just work.
Click to expand...
Click to collapse
Does it support being called via command line, from eg a bash script?
To the rest: did the PIE build work fine?
p7zip 16.02 stand-alone attached.
help needed. anybody know how to set HugeFiles=on? compiling with -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE does not give expected result
- - -
edit: many thanks to superbeef150 @ XDA for solution!
aIecxs said:
p7zip 16.02 stand-alone attached.
help needed. anybody know how to set HugeFiles=on? compiling with -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE does not give expected result
Click to expand...
Click to collapse
Does this work on Android 6.0?
aIecxs said:
p7zip 16.02 stand-alone attached.
Click to expand...
Click to collapse
Thanks for sharing! I'm able to get this to run on several devices, but for some reason it errors out when running it in TWRP (which is coincidentally where I hope to run it):
Code:
~ # chmod 777 /data/local/tmp/p7zip
~ # /data/local/tmp/p7zip
/sbin/sh: /data/local/tmp/p7zip: not found
~ # sh /data/local/tmp/p7zip
/data/local/tmp/p7zip: line 1: syntax error: unexpected word (expecting ")")
Has anyone observed this different behavior between TWRP and the normal OS occur with 7zip or any other terminal/shell/CLI apps?
superbeef150 said:
Has anyone observed this different behavior between TWRP and the normal OS occur with 7zip or any other terminal/shell/CLI apps?
Click to expand...
Click to collapse
I got this figured out in case anyone stumbles across this in the future.
The default shell in TWRP (in my case) is at /sbin/sh . From what I've read, it sounds like this is the one that is supplied with BusyBox rather than the normal one. When I ran 7z using /system/bin/sh I had a lot better luck.
I'm now running into issues with larger ISO files. It seems like ones over 2GB are the problematic ones, I can't extract, test, or list contents on them, instead I always get an "E_FAIL" error message.
Googling that in the context of 7z seems to indicate a space issue, but testing and listing contents should make that irrelevant. For the sake of trying I attempted this with the ISOs on an exFAT usb flash drive as well as an NTFS usb hard drive with the same results.
I suspect that the HugeFiles=off setting that @aIecxs mentioned earlier may be related, but unfortunately the only information on the topic I could find were on one of his posts on p7zip's SourceForge forum where someone suggested a few different compile flags that didn't seem to make a difference for him or myself.
If anyone has any thoughts on this I'd really appreciate it! Thanks!
maybe compiling on 64-bit machine will support Hugefiles
aIecxs said:
maybe compiling on 64-bit machine will support Hugefiles
Click to expand...
Click to collapse
I'm doing that currently, but unfortunately HugeFiles is still showing up as off :/

What are data.img system.img boot.img files

Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
http://stackoverflow.com/questions/3879717/what-is-purpose-of-using-system-img-in-android
http://en.wikipedia.org/wiki/Disk_image
http://en.wikipedia.org/wiki/Boot_image
these may help, or may not. But hopefully so, if not try looking around stackoverflow a bit more.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Thanks guys
ip2op01 said:
Thanks guys
Click to expand...
Click to collapse
My English is poor,it's my pleasure,you can understand it.
enyblock said:
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Click to expand...
Click to collapse
So, if I have a ROM with the .img file extension I should flash it as "System" (In TWRP)???

how to add directory to include_paths?

I have multiple errors like this
frameworks/av/media/libstagefright/ACodec.cpp:39:24: fatal error: QCMetaData.h: No such file or directory
this file located in hardware/qcom/media/mm-core/inc/ directory
how i can add this directory to include_paths?
if it is to a linux computer, you would add this to your /home/user/.bashrc file <- notice the dot.
export PATH=$PATH:/path/to/whatever/file/you/need
you can add this line below the same line, if you have one like this already.
to test, youc an also type it on the CLI, if it works, and you needed it permanent, then add it to the file mentioned.
no. it not about PATH variable
on UT compilation i have multiple errors like this
frameworks/av/media/libstagefright/ACodec.cpp:39:24: fatal error: QCMetaData.h: No such file or directory
becouce including header file QCMetaData.h locating in hardware/qcom/media/mm-core/inc/ directory that was not in <<includes_directories>>
how i can add this includes directory to each project which include files from it?
i dont want to catch all dependencies. how get it automatics?
ah I see. that's beyond my sys admin knowledge. someone with programming (gcc) skills can help you. Sorry
Hi Maybe this can help http://stackoverflow.com/questions/...odec-cpp-in-android-sources-in-libstagefright
gazhead said:
Hi Maybe this can help http://stackoverflow.com/questions/...odec-cpp-in-android-sources-in-libstagefright
Click to expand...
Click to collapse
nope

[Q] how extract an *.ab file (Helium Backup)

Hi,
I've backup a few apps from my Nexus 5 (Unrooted),
I've copied the .ab file to my PC and I wondered how can I extract it to edit some file and then repack it again.
I've already tried to extract it using DroidExplorer but I'm getting an un-openable tar file.
Can someone please point me how to can I do it right? and how can I repack it again,
Thanks in advance!
Gilco:good:
There is a sweet guide here
UltraWelfare said:
There is a sweet guide here
Click to expand...
Click to collapse
Thanks man, I tried but I get an error while trying to extract the tar file,
also I saw this warning at the end of the guide:
Warning about Helium (Carbon): helium backups are just android adb backups that are not compressed with Java Deflater. It means they were created with the option static final boolean COMPRESS_FULL_BACKUPS = false.
A normal adb restore should work.
see log from first step:
C:\Users\Gil\Desktop\BandR>java -jar abe.jar unpack com.gameinsight.airport.ab A
C.tar
Strong AES encryption enabled
Magic: ANDROID BACKUP
Version: 1
Compressed: 1
Algorithm: none
20664320 bytes read
gilc8 said:
Thanks man, I tried but I get an error while trying to extract the tar file,
also I saw this warning at the end of the guide: ...
Click to expand...
Click to collapse
Hi all, I play a bit with the conversion from Helium backups. Here is the utility:
xaos.ic.cz/Helium_ab2tar.zip . Still don't know what are the last four bytes in the Helium .ab file. Is that some checksum or what? Anyone knows?
xaos.cz said:
Hi all, I play a bit with the conversion from Helium backups. Here is the utility:
xaos.ic.cz/Helium_ab2tar.zip . Still don't know what are the last four bytes in the Helium .ab file. Is that some checksum or what? Anyone knows?
Click to expand...
Click to collapse
Thank you so much! It's working. I was able to extract my (unencrypted) Helium backup. Did you publish the code somewhere else? Here's a Makefile in case someone wants to build it for Linux. (Just remove .txt before running make or make extract)
Archived utility on Github
Hey everyone,
since the original utility has vanished and is somewhat hard to find, I've archived it at Github for convenience: github.com/floe/helium_ab2tar
If the original author wishes, I can transfer the repo to their ownership.
Best, Floe
floemuc said:
Hey everyone,
since the original utility has vanished and is somewhat hard to find, I've archived it at Github for convenience: github.com/floe/helium_ab2tar
If the original author wishes, I can transfer the repo to their ownership.
Best, Floe
Click to expand...
Click to collapse
Hi, the "helium_ab2tar" finally helped me. Good work!
I was running Win7 and didn't have any C compiler installed, so here is what I found:
• from the link above, extract helium_ab2tar-master.zip to a new directory
• from http://gnuwin32.sourceforge.net/packages/make.htm download Binaries and Dependencies and extract files make.exe, libintl3.dll, libiconv2.dll to your helium_ab2tar-master directory
• from https://bellard.org/tcc/ download a recent TinyCC build and extract the whole zip into your helium_ab2tar-master directory
• edit the makefile and change "CC=gcc" to "CC=tcc\tcc.exe"
• change "-o ab2tar_cut" to "-o ab2tar_cut.exe", "-o ab2tar_corr" to "-o ab2tar_corr.exe", "-o tar2ab_cut" to "-o tar2ab_cut.exe", "-o tar2ab_corr" to "-o tar2ab_corr.exe"
• finally run make.exe
How to use:
ab2tar_cut [.ab file] [temporary file]
ab2tar_corr [temporary file] [.tar file]
Thanks Commander!
It doesn't work for me =(
That's what I'm getting while trying to start it thru terminal
make: *** No targets specified and no makefile found. Stop.
download https://github.com/floe/helium_ab2tar, unzip, run make.exe from helium_ab2tar-master folder
aIecxs said:
download "https://github.com/floe/helium_ab2tar"]https://github.com/floe/helium_ab2tar, unzip, run make.exe from helium_ab2tar-master folder
Click to expand...
Click to collapse
there is no such file as make.exe.
of course, you must follow the steps in Post #7
or use linux. you can use Unetbootin and install Xubuntu to usb flash drive
aIecxs said:
of course, you must follow the steps in Post #7
or use linux. you can use Unetbootin and install Xubuntu to usb flash drive
Click to expand...
Click to collapse
I did so and it gives me another error
Code:
tcc\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe
process_begin: CreateProcess(NULL, tcc\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [ab2tar_cut] Error 2
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
aIecxs said:
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
Click to expand...
Click to collapse
ok it seems to work,
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master> C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\make.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe ab2tar_corr.c -o ab2tar_corr.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe tar2ab_corr.c -o tar2ab_corr.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe tar2ab_cut.c -o tar2ab_cut.exe
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
Click to expand...
Click to collapse
what's next ?
---------- Post added at 01:52 PM ---------- Previous post was at 01:47 PM ----------
aIecxs said:
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
Click to expand...
Click to collapse
what should be instead of [temporary file] ?
backup.ab.tmp (or any other name)
aIecxs said:
backup.ab.tmp (or any other name)
Click to expand...
Click to collapse
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
>> ab2tar_cut backup.ab backup.ab.tmp
ab2tar_cut : The term 'ab2tar_cut' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:1
+ ab2tar_cut backup.ab backup.ab.tmp
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (ab2tar_cut:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command ab2tar_cut was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\ab2tar_cut". See "get-help about_Command_Precedence" for more details.
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
Sorry I was using powershell for it, it doesn't work in PS but it works in CMD
Hello, I am feeling as dumb as a caveman right now because I could not figure out how to decompress and .ab file created with an old version of Helium which pretty much screw me over this.
I'm pretty much an illiterate with command lines in general. I tried cygwin but can't manage to find the right command combo, also android backup extractor doesn't even work despite I've installed the Java SE SDK etc (running Win10 x64). Can someone tell me step by step how I can decompress this hellish .ab file once for all? Thank you in advance.
P.s.= And yes, I also tryied using the method described on these last 2 pages and I get this:
C:\Users\Dingo Dash>"C:\Users\Dingo Dash\Desktop\helium_ab2tar-master\bin\make.exe" ab2tar_cut "C:\Users\Dingo Dash\Downloads\com.koushikdutta.backup\SM-G900F - 353687063301086\backup.ab" xxx.tmp
make: *** No rule to make target `ab2tar_cut'. Stop.
Click to expand...
Click to collapse
- download and edit makefile from post #5
- compile the binaries (.exe files)
- unpack backup + convert to tar
- unpack tar file
aIecxs said:
- download and edit makefile from post #5
- compile the binaries (.exe files)
- unpack backup + convert to tar
- unpack tar file
Click to expand...
Click to collapse
Thank you but I wanted to know what I was doing wrong on the prompt because I had already compiled the binaries aka followed the whole procedure.
Anyway, I managed to extract the whole damn file on another device. I don't have an explaination of why helium behaved this way but it actually worked on a more recent device instead of the original one, were the backup was created, also using a 2015 or so old version of the app, which should be the one the file came from.

[SOLVED] Installing WebView (rooted Stock ROM)

I am trying to install a clean Android System WebView (packagename: com.android.webview) onto stock LG G5 RS988 RS98821d Android 7.0 that is rooted.
I downloaded an arm64 WebView APK from the Bromite Releases GitHub page:
https://github.com/bromite/bromite/releases
I tried installing the Bromite WebView APK to "/system/app/webview/" (0644 permissions) and rebooted, but the WebView implementation could not be used.
There are instructions regarding installing Bromite System WebView available:
https://github.com/bromite/bromite/wiki/Installing-SystemWebView
From my reading of the installation instructions, "res/xml/config_webview_packages.xml" from "/system/framework/framework-res.apk" must contain the an entry for the package with the particular package name ("com.android.webview" in this case).
After examining the stock "config_webview_packages.xml" member file, it appears that a reference to "com.android.webview" is not present. The "config_webview_packages.xml" XML file also appears to not be easily readable in a text editor. My guess is that it has some kind of signing.
What must be done to get the system to allow the newly installed WebView? My impression is that the "config_webview_packages.xml" XML file must be edited, but it is not clear how to do so, given that it does not appear to be just plain text.
I have attached a copy of the "config_webview_packages.xml" XML member file and the original framework-res.apk file zipped into a ZIP 2.0 archive.
XML files inside apks are compressed, you should unpack the framework-res.apk using a tool for apk editing, not just a zip archiver program. On Android, you can use APK Editor Pro, for example.
By the way, have you already uninstalled Chrome? If Chrome is installed, it will be forced as the standard WebView provider.
tremalnaik said:
XML files inside apks are compressed, you should unpack the framework-res.apk using a tool for apk editing, not just a zip archiver program. On Android, you can use APK Editor Pro, for example.
Click to expand...
Click to collapse
It was my impression that the APK files were zip files with a particular signature block. I shall try a tool like APK Editor Pro and report back.
tremalnaik said:
have you already uninstalled Chrome? If Chrome is installed, it will be forced as the standard WebView provider.
Click to expand...
Click to collapse
I have uninstalled/removed both Chrome and the Android System WebView (Google Apps version).
Ascii3 said:
It was my impression that the APK files were zip files with a particular signature block. I shall try a tool like APK Editor Pro and report back.
Click to expand...
Click to collapse
Now I'm on PC and I remember the name of the tool I use sometimes on PC: APKChanger. It's very complete, although very heavy (about 650MB with my current configuration);
If you have platform tools installed on your pc, or the whole Android Studio, you can also use
Code:
aapt d xmltree framework-res.apk res/xml/config_webview_packages.xml
to see the list of allowed webview packages.
Ascii3 said:
I have uninstalled/removed both Chrome and the Android System WebView (Google Apps version).
Click to expand...
Click to collapse
So we can be sure the problem is not the system forcing Chrome as default WebView provider. So, as Bromite's wiki states, "Changing the package name does not make installation easier/possible;", so the only solution is to add com.android.webview to config_webview_packages.xml, or, if it is already there, remove the requirement for Google's signature on the webview package. EDIT: I checked, on your file com.android.webview is missing, you just need to add it:
Code:
E: webviewproviders (line=20)
E: webviewprovider (line=21)
A: description="Chrome Stable" (Raw: "Chrome Stable")
A: packageName="com.android.chrome" (Raw: "com.android.chrome")
A: availableByDefault=(type 0x12)0xffffffff (Raw: "true")
E: webviewprovider (line=24)
A: description="Google WebView" (Raw: "Google WebView")
A: packageName="com.google.android.webview" (Raw: "com.google.android.webview")
A: availableByDefault=(type 0x12)0xffffffff (Raw: "true")
A: isFallback=(type 0x12)0xffffffff (Raw: "true")
E: webviewprovider (line=27)
A: description="Chrome Beta" (Raw: "Chrome Beta")
A: packageName="com.chrome.beta" (Raw: "com.chrome.beta")
E: signature (line=28)
C: "MIIDwzCCAqugAwIBAgIJAOoj9MXoVhH6MA0GCSqGSIb3DQEBBQUAMHgxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKDAtHb29nbGUgSW5jLjEQMA4GA1UECwwHQW5kcm9pZDEUMBIGA1UEAwwLY2hyb21lX2JldGEwHhcNMTYwMjI5MTUxNTIzWhcNNDMwNzE3MTUxNTIzWjB4MQswCQYDVQQGEwJVUzETMBEGA1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNTW91bnRhaW4gVmlldzEUMBIGA1UECgwLR29vZ2xlIEluYy4xEDAOBgNVBAsMB0FuZHJvaWQxFDASBgNVBAMMC2Nocm9tZV9iZXRhMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAo/wW27nRxVqGbFOyXr8jtv2pc2Ke8XMr6Sfs+3JK2licVaAljGFpLtWH4wUdb50w/QQSPALNLSSyuK/94rtp5Jjs4RSJI+whuewV/R6El+mFXBO3Ek5/op4UrOsR91IM4emvS67Ji2u8gp5EmttVgJtllFZCbtZLPmKuTaOkOB+EdWIxrYiHVEEaAcQpEHa9UgWUZ0bMfPj8j3F0w+Ak2ttmTjoFGLaZjuBAYwfdctN1b0sdLT9Lif45kMCb8QwPp0F9/ozs0rrTc+I6vnTS8kfFQfk7GIE4Hgm+cYQEHkIA6gLJxUVWvPZGdulAZw7wPt/neOkazHNZPcV4pYuNLQIDAQABo1AwTjAdBgNVHQ4EFgQU5t7dhcZfOSixRsiJ1E46JhzPlwowHwYDVR0jBBgwFoAU5t7dhcZfOSixRsiJ1E46JhzPlwowDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAZO2jB8P1d8ki3KZILvp27a2VM3DInlp8I8UgG3gh7nBQfTrnZr5M1PL8eFHqX7MEvAiGCMTcrPklEhjtcHK/c7BcdeCWq6oL56UK3JTl33RxJcjmjrz3e3VI6ehRSm1feNAkMD0Nr2RWr2LCYheAEmwTPtluLOJS+i7WhnXJzBtg5UpUFEbdFYenqUbDzya+cUVp0197k7hUTs8/Hxs0wf79o/TZXzTBq9eYQkiITonRN8+5QCBl1XmZKV0IHkzGFES1RP+fTiZpIjZT+W4tasHgs9QTTks4CCpyHBAy+uy7tApe1AxCzihgecCfUN1hWIltKwGZS6EE0bu0OXPzaQ=="
E: webviewprovider (line=30)
A: description="Chrome Dev" (Raw: "Chrome Dev")
A: packageName="com.chrome.dev" (Raw: "com.chrome.dev")
E: signature (line=31)
C: "MIIDwTCCAqmgAwIBAgIJAOSN+O0cdii5MA0GCSqGSIb3DQEBBQUAMHcxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKDAtHb29nbGUgSW5jLjEQMA4GA1UECwwHQW5kcm9pZDETMBEGA1UEAwwKY2hyb21lX2RldjAeFw0xNjAyMjkxNzUwMDdaFw00MzA3MTcxNzUwMDdaMHcxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKDAtHb29nbGUgSW5jLjEQMA4GA1UECwwHQW5kcm9pZDETMBEGA1UEAwwKY2hyb21lX2RldjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANOYPj6Y9rVt8xizSHDYjDEkDfFZAgSiZ9T6tevkQXsFyfaq3Gk3h2qssi29G6cTPJ2VXFKlVB71wSXv5p9/LEcDQPWQiO3Q2cLmgUXxyhJWXI3g96tPAhZQX2q6SC37ZQdiBR/raMO70DAkvCyBGtNplsvutzSE3oZ7LYfzB8vTbe7zCh3fDYSS/7xb3ZVvFqydHS40uVq1qqg1S80Pge7tW3pDGsPMZN7yA4yfmsvA1rbHm9N8t3Rc9hqzh6OxNAAgRB535YcsWL7iF+mpdFILXk3jLYT0nMvMnB83rsdgnRREjlGQYHl2mh8+6CqujsW/eICDq/LR6BYDyqHhk0ECAwEAAaNQME4wHQYDVR0OBBYEFKzsl07JglgpbeYDYGqsgqRDo+01MB8GA1UdIwQYMBaAFKzsl07JglgpbeYDYGqsgqRDo+01MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBACka6SFF6xAcj8L8O6R36++E09DTiGZEjvKT8eIycgcQQ+p1WUmPb6M2EJpN6zvvSE62ussmXdzf8rIyc0JXA8jbViZt62Y39epNENFxPTLN9QzXlT+w8AW73Ka3cnbOuL5EgoDl8fM79WVlARY3X+wB/jGNrkiGIdRm2IZIeAodWgC2mtXMiferyYBKz2/F2bhnU6DwgCbegS8trFjEWviijWdJ+lBdobn7LRc3orZCtHl8UyvRDi7cye3sK9y3BM39k0g20F21wTNHAonnvL6zbuNgpd+UEsVxDpOeWrEdBFN7Md0CI2wnu8eA8ljJD45v0WWMEoxsIi131g5piNM="
E: webviewprovider (line=33)
A: description="Chrome Canary" (Raw: "Chrome Canary")
A: packageName="com.chrome.canary" (Raw: "com.chrome.canary")
E: signature (line=34)
C: "MIIDxzCCAq+gAwIBAgIJAML7APITsgV7MA0GCSqGSIb3DQEBBQUAMHoxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKDAtHb29nbGUgSW5jLjEQMA4GA1UECwwHQW5kcm9pZDEWMBQGA1UEAwwNY2hyb21lX2NhbmFyeTAeFw0xNjAyMjkxOTA5MDdaFw00MzA3MTcxOTA5MDdaMHoxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKDAtHb29nbGUgSW5jLjEQMA4GA1UECwwHQW5kcm9pZDEWMBQGA1UEAwwNY2hyb21lX2NhbmFyeTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANXfeAoZlr0ya1HBzIfAz/nLLjpPJeAPvuX5dueaxmiQgv2hNG22acriFuiiJI6TU0t8AIVJD5Ifbc4OOuA0zeFhdzWWGnmTRH6x27WI7bzOKnAqOvv21ZBmE9i8Vo++K13xWdTs3qVn1bn9oUONxFu0wKDzXYZhoj1Jom0RZGjXm16xuPlEuOzMcjiNBDoYuxPAXkMcK/G1gP4P4nAV8Rd/GGIjKRS/SUtcShhoAMOQhs4WIEkUrvEVRwhBDIbpM87oFbCVdBH38r0XS6F6CdhPJsKFhoEfq4c01HZqNmDpCPA8AAcCuSWqmXoTIqs7OqkWgduE2bInbWU7WMaTl+kCAwEAAaNQME4wHQYDVR0OBBYEFB/AsC4iPAqaLoNytNSx29qByI7+MB8GA1UdIwQYMBaAFB/AsC4iPAqaLoNytNSx29qByI7+MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAMb2Td3ro/+MGVnCPAbwBSOZMVLUKGqt6zr8CShW9mtFHnmy29EaWSYYAj1M4+6Vpkq85NsgBEck7rnUjV8A3Q0NKdTys1KRKJqVvQRBN6SwqQenSf/abxQCa8Z+69rh+3BkIU1HLtu5lrMDZwon5H91L5mpORn6vItd20uW132lwSDeUEW2CHslTrodoFuTUcSUlRiq/URfUH3baO1QHXkxpQwrBPKL5deJfcZnxh5MAtAGSQL7gHvayEFlDppETXdDO7vgGTH2dEK2TjKWALbGiKkxSqjRyTNt4/FOj10TqNRdUamj+ydVJgzGQ8bki4Vc6NnKm/r4asusxapkVR4="
E: webviewprovider (line=36)
A: description="Chrome Debug" (Raw: "Chrome Debug")
A: packageName="com.google.android.apps.chrome" (Raw: "com.google.android.apps.chrome")
On Android, I used APK Editor Pro 1.10.0 to modify res/xml/config_webview_packages.xml of /system/framework/framework-res.apk. A new APK with a generic signature was generated with the modification. I used the XML file editing option to select and modify the config_webview_packages.xml. The XML file editing functionality is given to be in beta and appears buggy.
I replaced the original /system/framework/framework-res.apk file with the patched one using the TWRP 3.2.3-0 file manager and attempted to boot to system. The system would start, but get stuck at the LG logo screen. I tried wiping data, and cache in recovery and booting again, but received the same result. I note that adb was available and usable after the boot process got stuck on the LG Logo screen.
My impression is that the patched framework-res.apk file is incompatible or defective. Perhaps APK Editor Pro 1.10.0 malformed the output APK (the XML editing feature appeared unfinished) or that the LG stock ROM expects framework-res.apk to have have a particular signature.
Perhaps a different APK editing tool should be tried. What could the problem be?
I have attached a ZIP archive containing the APK Editor Pro 1.10.0 modified framework-res.apk.
EDIT: Attachment has been removed; the file was defective and should not be used. Attachment is no longer necessary.
I have now patched framewor-res.apk successfully, and Bromite System WebView is working.
Did you use again APk Editor Pro or a PC tool?
The tools I used were Windows tools (and with a Java dependency in the case of Apktool) and were: Apktool 2.3.1 and WinRAR 5.6.1. I found that it is best to avoid newer versions of the tool unless trying to manipulate Android 9 Pie or newer resources.
Ascii3 said:
I have now patched framewor-res.apk successfully, and Bromite System WebView is working.
Click to expand...
Click to collapse
I know this is an old post, but how did you get it to boot?
I'm using apktool 2.5 and seems to be stuck on the boot screen as you were
burny02 said:
I know this is an old post, but how did you get it to boot?
I'm using apktool 2.5 and seems to be stuck on the boot screen as you were
Click to expand...
Click to collapse
From somewhere else it seems that you are now using Apktool 2.3.1.
After comparing my notes, my impression on what you are missing and some related notes:
The modified framework-res.apk should use the unmodified APK file's "AndroidManifest.xml" root file and META-INF directory contents. It is not sufficient for any of the content to be the same after decompiling.
Copy "AndroidManifest.xml" and META-INF directory from original framework-res.apk to modified framework-res.apk using zip program, if contents are different.
v2 APK signing scheme (which includes the APK file itself in validation), if present, would be broken, but the scheme's enforcement is not enforced on /system; v1 APK signing scheme (on APK contents ("AndroidManifest.xml" file and META-INF directory contents)) is still enforced.
I zipaligned output/modified framework-res.apk prior to transferring original "AndroidManifest.xml" file and META-INF directory contents, but I do not believe it matters for the purposes of getting a functional framework-res.apk.
EDIT: Some added things to keep in mind:
Sometimes clearing system cache and the runtimes cache is also necessary before system will boot after framework-res.apk replacement. Also make sure that the permissions of the replaced framework-res.apk file are at minimum whatever the original file permissions were. Depending on what software you use to replace the framework-res.apk file, the permissions set may be different.
I really appreciate the help, still does not work unfortunately.
Here is what I do:
adb pull framework-res.apk
apktool d framework-res.apk (tried most versions, mainly now 2.3.1)
Edit framework-res/res/xml/config-webview-packages.xml to:
Code:
<webviewproviders>
<webviewprovider description="Bromite WebView" packageName="com.android.webview" availableByDefault="true" isFallback="true" />
</webviewproviders>
Removing other dev versions with signatures etc
apktool b framework-res
zipalign -v 4 framework-res.apk framework-res-new.apk
Move META-INF and AndroidManifest.xml from the 1st original framework-res.apk > framework-res-new.apk (Have also tried moving res & resources from the new to the original...7Zip, WinRAR, CLI - Linux)
adb push framework-res-new.apk /system/framwork-res.apk
Modify permissions in TWRP > 0644
Move framework-res.apk from /system/ to /system/framework/framwork-res.apk (I read somewhere this is better than pushing directly. Neither worked)
Clear Davlik & Cache
Reboot
Hangs on boot screen
Any ideas if I am missing something important?
@burny02 - Please clarify whether the framework-res.apk you are trying to modify is for LG G5 stock ROM Android Nougat.
I note that you are using the "isFallback="true"" flag with the webviewprovider tag. The purpose of the isFallback attribute set to true (its default is false) is to specify that the WebView provider should be disabled by deault and should only become available when allow other WebView providers are disabled. Using the attribute with the true value with only a single WebView provider seems improper. I do not know if boot should fail if the attribute is present in the way that it is, but in both scenarios I would recommend its omission.
It has also been a while since I used Apktool versions and do not exactly remember the command lines. Do not take my not pointing to an issue with it as there necessarily not being an issue. One thing I would mention is that one typically first install a frameworks before decompiling and building. For the LG G5 RS988 Android Nougat, I believe installing the framework-res.apk as a framework was sufficient. You would specify on command line "apktool if framework-res.apk" and any tags you wish to explicitly specify, if any.
The moving of framework-res.apk to /system/ before /system/framework/ is oftentimes done by people to try to install a modified framework-res.apk with proper permissions and on a live system before the system crashes and reboots. Once framework-res.apk is copied to /system , but does not replace the framework-res.apk file, proper permissions can be set prior to using that file to replace the live framework-res.apk. It is still important to note that some software disregards permissions set when a file is relocated or copied, so this could be an issue if framework-res.apk is replaced with more restrictive permissions than the original framework-res.apk (less restrictive permissions should not usually be a problem for the app to be used). I particularity do not like the idea of the system crashing and prefer to make such changes offline (such as via the aid of a custom recovery).
Sorted. Got it working. Really appreciate the help, Ascii3
For anyone looking at this in the future, the isFallback back seems to stop booting, regardless of whether it is the only entry or not.
The procedure then works as above:
adb pull framework-res.apk
apktool d framework-res.apk (2.3.4 worked for me - SDK 24 Android 7.1 (LGG5))
Edit framework-res/res/xml/config-webview-packages.xml to:
Code:
<webviewproviders>
<webviewprovider description="Bromite WebView" packageName="com.android.webview" availableByDefault="true" />
</webviewproviders>
apktool b framework-res
Move META-INF and AndroidManifest.xml from the 1st original framework-res.apk > new framework-res-new.apk (Used 7Zip drag & drop)
adb push framework-res-new.apk /system/framework/framwork-res.apk
Modify permissions in TWRP > 0644
Clear Davlik & Cache
Reboot
I found the following unnecessary :
Installing framework (apktool if)
Zip-aligning
Moving to /system prior to /system/framework/ (Using TWRP, live system; it might be necessary)
burny02 said:
Sorted. Got it working. Really appreciate the help, Ascii3
Click to expand...
Click to collapse
Sure.
burny02 said:
For anyone looking at this in the future, the isFallback back seems to stop booting, regardless of whether it is the only entry or not.
Click to expand...
Click to collapse
The isFallback attribute is supposed to only be set to true for no more than one webviewprovider. Explicitly setting it to false (its default) should not be problematic (but does result in a larger config-webview-packages.xml file generated). Setting isFallback to true on the only webviewprovider item is not an intended use and apparently results in no boot.
burny02 said:
I found the following unnecessary :
Zip-aligning
Click to expand...
Click to collapse
I do not think zip-aligning apps is necessary generally . My understanding around the reason to do so is to try to optimize the packaged data to be more efficiently fetched in the manner which Android fetches the data.
@Ascii3 @burny02
Hello guys, sorry to exhume this post but I'm struggling and all other threads are maybe ten years old...
So I'm struggling to replicate what you did! I'm no expert but I can follow basic instructions.
So I do as you say, decompile framework-res.apk, modify the xml file (I just add the line). This step seems okay since I did some errors while editing the file and apktool would not recompile properly. Now this goes fine.
Then I got my freshly recompiled framework-res.apk, but 7zip on linux won't let me insert META-INF and AndroidManifest.xml. So I had to rename the extension .zip, do it, then rename in apk. Could this be an issue? It looks dirty.
Anyway, after this you didn't had to resign the apk? I read everywhere you had to, so I did. I did not zipaligned it since I used a resign tool I found on xda and I could not tell if I had to do it before or after resigning, but since you said you didn't zipalign it I thought whatever.
The problem is the following: after replacing framework-res.apk in /system/framework, the phone won't start, I get stuck on the starting screen and I could extract the following from logging:
01-24 04:15:17.470 +0000 4042 4042 I PackageManager: /system/framework/framework-res.apk changed; collecting certs
01-24 04:15:17.749 +0000 4042 4042 W PackageManager: Failed to scan /system/framework/framework-res.apk: Failed to collect certificates from /system/framework/framework-res.apk
Have you got any ideas of what I did wrong? It's my fourth soft-brick today, I'm getting a bit annoyed.
Thanks in advance
@LeSplendide did you ever get this working? Not sure if I'm having the same trouble, but I followed burny's instructions and my phone fails to boot. I checked logcat but I don't see anything relating to framework-res. I'm using magisk to overlay it because if I touch the /system partition for real, VoLTE stops working on my phone (known issue for this phone). I'm successfully overlaying stuff in /system/app and /system/priv-app so I do have overlaying generally working, though this is the first apk in the framework directory I've tried to overlay. Boy do I want to get this working. I've extensively degoogled and debloated this phone and the only glaring thing that remains is chrome handling webview.
TheShanMan said:
@LeSplendide did you ever get this working? Not sure if I'm having the same trouble, but I followed burny's instructions and my phone fails to boot. I checked logcat but I don't see anything relating to framework-res. I'm using magisk to overlay it because if I touch the /system partition for real, VoLTE stops working on my phone (known issue for this phone). I'm successfully overlaying stuff in /system/app and /system/priv-app so I do have overlaying generally working, though this is the first apk in the framework directory I've tried to overlay. Boy do I want to get this working. I've extensively degoogled and debloated this phone and the only glaring thing that remains is chrome handling webview.
Click to expand...
Click to collapse
I'm sorry I have no idea, rn Webview Implementation says I have Android System Webvew 102.0.5005 so I assume this is chrome webview? But I have no clue what I did or not but I know for sure I fixed my problem which was that Webview would crash when trying to sign in a google account on my MicroG'd LEAOS. Now this works so I guess I did make it work. All I found that could be a clue is a update.zip containing instructions and the webview in question. Iirc, the issue was that the zip needed to be signed so that twrp could flash it, so I think I just signed my zip and it worked but can"t tell for sure.

Categories

Resources