Thanks to xda member @fatouraee the EVR-AL00 firmware has been posted here. I've taken the time to download and dissect it and found a few interesting tidbits.
For starters it appears to be a engineering or internal build
build.prop lists it as an August security patch, so it is old.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.001
ro.build.version.incremental=eng.root.20181019.195045
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.base_os=
config.disable_consumerir=true
ro.build.version.security_patch=2018-08-05
ro.build.version.min_supported_target_sdk=17
ro.build.date=Fri Oct 19 19:50:42 CST 2018
ro.build.date.utc=1539949842
ro.build.type=eng
ro.build.user=root
ro.build.host=sh0514826b41539948706875-7099393-jgmgb
ro.build.tags=test-keys
ro.build.system_root_image=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.product.locale=en-US
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-eng 9 PPR1.180610.001 eng.root.20181019.195045 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:9/PPR1.180610.001/root10191950:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# from device/emui/generic_a15/system.prop
#
persist.sys.cpuset.enable=1
persist.sys.cpuset.subswitch=16
persist.sys.iaware.cpuenable=true
persist.sys.fast_h_duration=2000
persist.sys.fast_h_max=50
persist.sys.max_rdh_delay=0
ro.config.enable_rcc=true
ro.config.hw_sensorhub=true
system_init.hwextdeviceservice=1
bastet.service.enable=true
dalvik.vm.boot-dex2oat-threads=4
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.control_privapp_permissions=log
ro.opa.eligible_device=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=9_201806
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
ro.kernel.android.checkjni=1
dalvik.vm.lockprof.threshold=0
dalvik.vm.image-dex2oat-filter=verify-at-runtime
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xf227db076aec861e23fda4c530f3156b69ef8804000000000000000000000000
ro.build.display.id=System-FAC 9.0.0.062(00IE)
ro.comp.sys_support_vndk=
But, here's where things get interesting!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It appears to be rooted already. Of course, with no up to date software available, you will more than likely be stuck on this build until shipping/retail firmware becomes available. Someone should take one for the team and flash it.
Join our developer telegram group here for help flashing and testing out theories so that we may soon develop a method and guide to post on XDA regarding root and/or rebrand.
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
AngelDeath said:
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
Click to expand...
Click to collapse
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
freeza said:
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
Click to expand...
Click to collapse
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
antiochasylum said:
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
Click to expand...
Click to collapse
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
freeza said:
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
Click to expand...
Click to collapse
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
AngelDeath said:
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
Click to expand...
Click to collapse
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
ajsmsg78 said:
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
Click to expand...
Click to collapse
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
All we need now is a working "TWRP"...
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
Here's a link to download the L29 9.0.0.108 system/vendor/cust that I extracted:
https://www.androidfilehost.com/?w=files&flid=285746
And here is the AL00 System:
https://www.androidfilehost.com/?fid=11410963190603853598
ajsmsg78 said:
Here's a link to download the L29 9.0.0.108 system that I extracted:
https://www.androidfilehost.com/?fid=11410963190603853592
Click to expand...
Click to collapse
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
AngelDeath said:
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
Click to expand...
Click to collapse
Sure, give me a few and I'll add them to the last post. Ok good to go, updated the link.
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
AngelDeath said:
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
Click to expand...
Click to collapse
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
mac231us said:
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
Click to expand...
Click to collapse
I have two offline programs that compare, I'll see what I find and let you know.
AngelDeath said:
I have two offline programs that compare, I'll see what I find and let you know.
Click to expand...
Click to collapse
A quick look by two different apps (Getting an update to one of them for final comparison) shows that either both the Recovery_Vendor.img and Recovery_ramdisk.img are complete different based on comparison, or because one is a internal rooted rom (AL00) and the L29 isnt, could be why there is such a massive difference in coding. Basically the whole file is different in both, My whole screen is red except the last 3 hex lines. But checking to see if updating the app makes a difference (probably not).
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
freeza said:
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
Click to expand...
Click to collapse
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
AngelDeath said:
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
Click to expand...
Click to collapse
Just PMd you
fatouraee said:
Just PMd you
Click to expand...
Click to collapse
Got it
Related
Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.
So, uhhhh . . . you gonna share that modded kernel?
utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Got overclock working fine. Great thanks Haus
Can anyone make a zip? Pretty please.
You can't make a zip. you have to mod the ko file yourself and launch it yourself.
utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.
Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.
So glad you're here haus :thumbup:
Sent from my EVO using xda premium
it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?
Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.
XDA University is Coming! Can't wait to learn more...
Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"
xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.
thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.
Hi Community,
this is a support thread for DSA Rom`s
The reason for this here is, that all DSA threads on XDA are closed and I dont know where to share experiance and bugs for the DSA Roms.
First of all, a big thanks to DSA for sharing your Roms.
I am using the 4.4 Rom, and what should I say?
Fast, stable and clean....simple perfect
I've combined the DSA Rom with Malaysk parts to get screensafer working.
What experiance do you have with DSA Roms ?
Please share it with us
Best regards
By far the best ROM's for these units in my opinion. I'm currently stripping down DSA's 4.4.4 ROM, removing all unnecessary APK's for my system and use case, completely removing Google Play, and it boots quickly and loads nav quickly as well.
I made @dsa8310 lollipop lite by unninstalling all unusefull apps and I got it usable on 1Gb ram, much better then kitkat, because the programs run better for me and everything works... (mtc-keys, mtc manager etc.)
Was planing to make the lite update.img file to install with changed logo and removed apps, but when I was building an image it gets bigger then dsa's one, don't know why... If I tried booroondoks one, it is smaller as it should be.
If anyone knows all the apps which can be removed or just the explanation of apps it will help to build an image.
Now I totally have more than 65 apps removed and the system is fully responsive with google maps and google play included (the only problem is that removing apps from folders on computer that there is not the same package names like the apps names itself.)
Johny DJ said:
I made @dsa8310 lollipop lite by unninstalling all unusefull apps and I got it usable on 1Gb ram, much better then kitkat, because the programs run better for me and everything works... (mtc-keys, mtc manager etc.)
Was planing to make the lite update.img file to install with changed logo and removed apps, but when I was building an image it gets bigger then dsa's one, don't know why... If I tried booroondoks one, it is smaller as it should be.
If anyone knows all the apps which can be removed or just the explanation of apps it will help to build an image.
Now I totally have more than 65 apps removed and the system is fully responsive with google maps and google play included (the only problem is that removing apps from folders on computer that there is not the same package names like the apps names itself.)
Click to expand...
Click to collapse
Do you have a version to share? Would love to try it out
tariqkhan.co.uk said:
Do you have a version to share? Would love to try it out
Click to expand...
Click to collapse
Not yet, I optimized car version not image one yet... I also removed all google playstore services and replaced with different ones so everything is working but faster boot and performance.
Johny DJ said:
Not yet, I optimized car version not image one yet... I also removed all google playstore services and replaced with different ones so everything is working but faster boot and performance.
Click to expand...
Click to collapse
Can't wait to give it a go... give me a shout when you have something ready?
Johny DJ said:
Not yet, I optimized car version not image one yet... I also removed all google playstore services and replaced with different ones so everything is working but faster boot and performance.
Click to expand...
Click to collapse
Will love to have it too.
Sent from my Robin using XDA-Developers Legacy app
I would like to have the DSA-ROM, but don´t know why there are two update img (part1 and part2)?
How do I install the two img? Do i need both of them?
Do anyone have some screenshots of the DSA-ROM?
My HU:
MTCB JY v.2.86, RK3188, 1024x600, Android 5.1.1
Thodai said:
I would like to have the DSA-ROM, but don´t know why there are two update img (part1 and part2)?
How do I install the two img? Do i need both of them?
Do anyone have some screenshots of the DSA-ROM?
My HU:
MTCB JY v.2.86, RK3188, 1024x600, Android 5.1.1
Click to expand...
Click to collapse
He @dsa8310) split the file in half. when you run the 1st part, it will join part1 and part2 when it makes the update.img (Use 7zip or unrar
Thank´s a lot, Oldpapa49!
Did you, or did you ever have the DSA-ROM?
How is the subjective compared to a Malaysk-ROM?
Actually, Malaysk-ROM runs on my HU quite well, but I´am too curious as the ROM of dsa8310 is
Have a nice day!
Thomas
Thodai said:
Thank´s a lot, Oldpapa49!
Did you, or did you ever have the DSA-ROM?
How is the subjective compared to a Malaysk-ROM?
Actually, Malaysk-ROM runs on my HU quite well, but I´am too curious as the ROM of dsa8310 is
Have a nice day!
Thomas
Click to expand...
Click to collapse
DSA8310 rom does very well (5.1.1) which currently I'm using now. He just makes it very basic. Boots fast and is not a FUSE type rom (FUSE uses all memory for APPs)
Malasky is a feature rom, he puts some apps in it to his liking. It is FUSE type to no limit to the amount of apps.
I like to have a speedometer on main display (mal's does this) so I install a launcher that I can put what I want on the main screen.
I have the speed I want with the weather on main.
And I like apps, so I will have to limit my apps.
One question, bevore i install it:
The ROM is named xupdateKLD....
I'm worried that the "KLD" is not compatible with my JY. The ROM is not just for Klyde Head Units and universally applicable?
Thodai said:
One question, bevore i install it:
The ROM is named xupdateKLD....
I'm worried that the "KLD" is not compatible with my JY. The ROM is not just for Klyde Head Units and universally applicable?
Click to expand...
Click to collapse
The only constrain to install DSA Rom is to have an MTCB Head unit and not MTCD or Intel! (I have a JY MTCB and this ROM is doing great)
I've tried to unzip the part2 of dsa ROM. It shows two errors. Whats wrong?
Edit:
No matter what 2nd part of any DSA-ROM I try to unpack, there are always 2 errors
I'm scared to destroy something on my Head-Unit when I'm flashing this update.img!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thodai said:
I've tried to unzip the part2 of dsa ROM. It shows two errors. Whats wrong?
Edit:
No matter what 2nd part of any DSA-ROM I try to unpack, there are always 2 errors
I'm scared to destroy something on my Head-Unit when I'm flashing this update.img!
Click to expand...
Click to collapse
I downloaded the December xupdate rar files.
I placed both files in a folder and ran 7Zip and selected the 1st file (204,800KB) and had it extract the files. 7Zip will extract both part1 and part2 at the same time.
The extracted file will be filename update.img size of 818.159KB.
If you try extracting the part2, you will get an error. The pointers are in part1.
Done.... Oldpapa49, you are my hero!
Oldpapa49 said:
I downloaded the December xupdate rar files.
Click to expand...
Click to collapse
Then you have an MTCC?
I have a MTCB and here is the last ROM from 05.08.2016.
What actually means "prerootet"?
Is the ROM now rooted or not?
Thodai said:
Done.... Oldpapa49, you are my hero!
Then you have an MTCC?
I have a MTCB and here is the last ROM from 05.08.2016.
What actually means "prerootet"?
Is the ROM now rooted or not?
Click to expand...
Click to collapse
Mine is a MTCB KLD6 800*480 that was 4.4.4....
I do on occasion, while driving or not, flash Mal ROM, DSA8310 ROM, Boonoorook ROM and factory. Was on DSA8310 until yesterday, now on latest 4.4.4 of Mal's. Who know what tomorrow will bring.
So far for flashing, I have done it all.
I have backups of the launcher that I like, (It historic where I can add my own stuff)
I want on my main page Speed, Weather and a few apps I like (Sirius is one).
I save my stuff via Titanium and recover apps that way.
I have like 20 USB Flash drives with all different update images.
I'm crazy.. Love it..
Hahah....., yes, you´re crazy!
The flashing of the DSA-ROM was not successful. For 10 minutes just black screen.
Is it the first time so long?
Thodai said:
The flashing of the DSA-ROM was not successful. For 10 minutes just black screen.
Is it the first time so long?
Click to expand...
Click to collapse
Steps are:
Flash update.img via MicroSD card in GPS slot or USB flash drive in USB slot with clear option.
After, got to second option from bottom to clear CACHE and all. The reboot unit. Should see dancing androids for a long time.
IT will the start the home screen.. Leave the unit alone, it will reboot to setup more stuff. reboot is 2 times.
Second time you should be good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes
Hello everybody!
Anybody knows how to merge these multiple {Mod edit} into one super.img file? I wanna obtain the LG Velvet's color emoji ttf file, and they're extracted from G90010s_0_user-signed-ARB0_COM1_EU_OP_1229.dz firmware file. Thanks in advance.
(BTW I don't have the LG phone )
View attachment 5513619
giant_ant_tiny_elephant said:
Hello everybody!
Anybody knows how to merge these multiple {Mod edit} into one super.img file? I wanna obtain the LG Velvet's color emoji ttf file, and they're extracted from G90010s_0_user-signed-ARB0_COM1_EU_OP_1229.dz firmware file. Thanks in advance.
(BTW I don't have the LG phone )
View attachment 5513619
Click to expand...
Click to collapse
@giant_ant_tiny_elephant
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
giant_ant_tiny_elephant said:
Hello everybody!
Anybody knows how to merge these multiple {Mod edit} into one super.img file? I wanna obtain the LG Velvet's color emoji ttf file, and they're extracted from G90010s_0_user-signed-ARB0_COM1_EU_OP_1229.dz firmware file. Thanks in advance.
(BTW I don't have the LG phone )
View attachment 5513619
Click to expand...
Click to collapse
Where the attached image went?
Anyways, you put nulls between those images. One way to do it is to minus the numbers at the end of file names and then multiply that number with block size which is in this case 4096. Like this:
super.img_0
<here (10-0)*4096 nulls>
super.img_10
<here (30-10)*4096 nulls>
super.img_30
<... and so on...>
CXZa said:
Where the attached image went?
Anyways, you put nulls between those images. One way to do it is to minus the numbers at the end of file names and then multiply that number with block size which is in this case 4096. Like this:
super.img_0
<here (10-0)*4096 nulls>
super.img_10
<here (30-10)*4096 nulls>
super.img_30
<... and so on...>
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And what is the software I must use to merge these {Mod edit} chunks?
Mod Edit: Message edited
giant_ant_tiny_elephant said:
View attachment 5514921
And what is the software I must use to merge these {Mod edit} chunks?
Click to expand...
Click to collapse
Copy will do. And there is plenty of those Python scripts out there that you probably used to get this far. Some of them might do it for you, but I don't know much about them. Some work for some and some don't.
Then you'll have to extract that super too...
Probably binwalk or something like it would be an easier or a faster approach... ?
CXZa said:
Copy will do. And there is plenty of those Python scripts out there that you probably used to get this far. Some of them might do it for you, but I don't know much about them. Some work for some and some don't.
Then you'll have to extract that super too...
Probably binwalk or something like it would be an easier or a faster approach... ?
Click to expand...
Click to collapse
I want to do it on Windows.
For example, the super chunk filename is:
super_xxx.img_yyy
Can you explain me what are the xxx and yyy numbers mean?
giant_ant_tiny_elephant said:
I want to do it on Windows.
For example, the super chunk filename is:
super_xxx.img_yyy
Can you explain me what are the xxx and yyy numbers mean?
Click to expand...
Click to collapse
Last one is probably chuck's place on the on the disk (yyy).
Python runs on Windows...
giant_ant_tiny_elephant said:
LG Velvet's color emoji ttf file, and they're extracted from G90010s_0_user-signed-ARB0_COM1_EU_OP_1229.dz
Click to expand...
Click to collapse
Hmm... depends what you're after but that G90010s firmware might be old. The new ones came with Android 11 according to this article: https://blog.emojipedia.org/lg-emojis-return-to-say-goodbye/
You might want to try with newer one. G900EM20j seems to be latest at the moment...
LG-Kdz-downloader (updated)
A small batch tool to download kdz files from LG servers. Just because I don't want use some unknown tools out there. Post at XDA: https://f...
cxzstuff.blogspot.com
Anybody has extracted/obtained that {Mod edit} emoji file from the LG Velvet phone or firmware here? Please upload the file to GDrive and send the link to me. Thank you.
It usually named *ColorEmoji.ttf and located at /system/fonts
giant_ant_tiny_elephant said:
Anybody has extracted/obtained that {Mod edit} emoji file from the LG Velvet phone or firmware here? Please upload the file to GDrive and send the link to me. Thank you.
It usually named *ColorEmoji.ttf and located at /system/fonts
Click to expand...
Click to collapse
Extracting it for you would be just a waste of time...
I did enough of that in this thread already.
Have fun!
CXZa said:
Extracting it for you would be just a waste of time...
I did enough of that in this thread already.
Have fun!
Click to expand...
Click to collapse
For those who have the LG Velvet phone, download the FX File Explorer app from Play Store. If you already have the app, you can open it. Then go to System → /system/fonts, look for a file named LGColorEmoji.ttf, copy to the internal storage and upload to GDrive, and then send the link to me through conversation.
giant_ant_tiny_elephant said:
LGColorEmoji.ttf
Click to expand...
Click to collapse
There wasn't such. All I could find was one with the name {Mod edit}ColorEmoji.ttf...
Just try to do it yourself, it's not that hard...
CXZa said:
There wasn't such. All I could find was one with the name {Mod edit}ColorEmoji.ttf...
Just try to do it yourself, it's not that hard...
Click to expand...
Click to collapse
I don't have the LG phone, but I really like that {Mod edit} emoji file (because of the flag emojis wave style are similar like Apple's) and even I'd like to replace my phone's current emoji with that one. If it's found from the LG Velvet phone, please upload that {Mod edit} to GDrive then send the link to me through conversation.
giant_ant_tiny_elephant said:
look for a file named LGColorEmoji.ttf
Click to expand...
Click to collapse
Got myself now interested in this Super of LGs, and it's "differencies". While checking them (and wasting some more time), I also extracted that newer kdz. Found just a file named "NotoColorEmoji.ttf".
Hope it's what you're looking for... (*)
Have fun!
(* edit: probably not, see the post #19 for more...)
CXZa said:
Got myself now interested in this Super of LGs, and it's "differencies". While checking them (and wasting some more time), I also extracted that newer kdz. Found just a file named "NotoColorEmoji.ttf".
Hope it's what you're looking for...
Have fun!
Click to expand...
Click to collapse
Thanks so much and sorry for wasting your time...
Have fun too!
BTW, What is the firmware version, build date, and its Android version?
Deleted the folder already. It's the one I mentioned earlier, post #8.
As you see it's Android 11 (R).
(It was put to LG's server on Tue, 14 Dec 2021)
CXZa said:
Deleted the folder already. It's the one I mentioned earlier, post #8.
As you see it's Android 11 (R).
(It was put to LG's server on Tue, 14 Dec 2021)
Click to expand...
Click to collapse
Oh sorry, I almost forget.
The emojis must look exactly like in this Emojipedia page:
LG Emoji List [Updated: September 2021]
emojipedia.org
And I Hate the Google's Stock Emoji.
giant_ant_tiny_elephant said:
Oh sorry, I almost forget.
The emojis must look exactly like in this Emojipedia page:
LG Emoji List [Updated: September 2021]
emojipedia.org
And I Hate the Google's Stock Emoji.
Click to expand...
Click to collapse
So, do they look like them then? That is the only one I found. Didn't check it or anything...
giant_ant_tiny_elephant said:
BTW, What is the firmware version, build date, and its Android version?
Click to expand...
Click to collapse
Just checked a T-mobile Velvet 5G firmware released on Monday. Found LGNotoColorEmoji.ttf in it.
Naturally I now had to extract that G900EM20j again to see if I just missed it...
Now it was in /system/system_ext/fonts/ folder.
It probably was hiding somewhere else last time... odd.
The build date was Wed Nov 17 15:46:24 IST 2021
So it took almost a month to put it to their server...
The T-mobile version is a bit bigger. I'll attach that as well.
Now enjoy!
CXZa said:
Just checked a T-mobile Velvet 5G firmware released on Monday. Found LGNotoColorEmoji.ttf in it.
Naturally I now had to extract that G900EM20j again to see if I just missed it...
Now it was in /system/system_ext/fonts/ folder.
It probably was hiding somewhere else last time... odd.
The build date was Wed Nov 17 15:46:24 IST 2021
So it took almost a month to put it to their server...
The T-mobile version is a bit bigger. I'll attach that as well.
Now enjoy!
Click to expand...
Click to collapse
T.H.A.N.K. Y.O.U. S.O. M.U.C.H. A.N.D. M.U.C.H.
I REALLY LOVE YOU AND LOVE THAT GODDAMNED EMOJI!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel Flasher is an Android app to flash, backup, and restore kernels.
Features
Flash partition images and AK3 kernel zips
Backup and Restore kernel partitions
Mount, Map, and Resize vendor_dlkm
Save dmesg, logcat, and ramoops
Check for kernel updates
Notes
When making a backup of the active slot, to save time, it is assumed that the kernel on disk is the same as the running kernel. The Check Kernel Version button can retrieve it from disk prior to backup.
Depending on the method used, the updated contents of vendor_dlkm may not be immediately available for backup after flash or restore. This can be resolved by unmounting, unmapping, then remapping it.
AK3 helper modules are not backed up.
Credits
@osm0sis for AK3, feedback, and general guidance
@eng.stk & @Freak07 for feedback, advice, and encouragement
@phhusson for lptools
@topjohnwu for Magisk and libsu
Latest Update
2023-02-20 v1.0.0-alpha13
Hi, great app!
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Nezorflame said:
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Click to expand...
Click to collapse
That is already done in my own personal test version of the app, but I haven't had a chance to clean it up and get it released. I'll make an effort to get that done this evening.
I've got several other enhancements planned, but most of my focus has been on Hashtree Patcher lately, though I think that is nearly wrapped up. I'll try to get the installation log issue fixed asap, then I'll work on the rest over the next few days.
I pushed a new build that resolves the installation log issue. Here is the full changelog:
added option to backup AK3 zips
disabled flash and restore on inactive slot
added save ramoops button
added stderr to AK3 logs
added .log file extension to log files
filtered ui_print and progress in AK3 logs
sorted backups
Click to expand...
Click to collapse
I also added a list of planned and potential features to the OP. If you've got some interest in seeing any of them or anything I may have missed in a future build, feel free to note it here. If the list gets to be too big of a pain to maintain here, I may request that they go to the issue tracker, instead. Note that I don't currently plan to add kernel tweaks to the app.
Edit: There was a bug in the v1.0.0-alpha03 build that caused it to crash frequently. This has been fixed in v1.0.0-alpha04.
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
eng.stk said:
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
Click to expand...
Click to collapse
I have that checksum too but it's not working, maybe it's minimum Android 12?
Edit: Yep! Can the minimum API be lowered to support Android 11?
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
osm0sis said:
I have that checksum too but it's not working, maybe it's minimum Android 12?
Click to expand...
Click to collapse
Yes, I was playing with the new Splashscreen API, which requires Android 12, and I don't have an Android 11 device to test on, so I just set minSdk to 31. I'll see if I can get it to build against something lower.
I pushed a new build that will hopefully work on Android 11. Here are the changes:
lowered minSdk to 30
added vbmeta to raw partition backups
fixed vendor_dlkm map and mount
Click to expand...
Click to collapse
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
capntrips said:
I pushed a new build that will hopefully work on Android 11. Here are the changes:
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
Click to expand...
Click to collapse
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
osm0sis said:
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
Click to expand...
Click to collapse
I pushed a new build that hopefully fixes the issue. It now makes it to the point where it requires root to continue on an Android 11 AVD. I assume if it makes it to that point, the rest will work as expected. Anything beyond that, and I'll have to root the AVD to test it (though I did see an article about that a few weeks back, and it seemed simple enough).
Now works on lineage 18.1 Sony xz2 slot a/b device
A few random thoughts/ideas while testing on my 8T :
Got some errors trying to backup on my 8T since there's no vendor_boot, so I guess some logic will be needed for whether they exist.
Probably the feature should be like "backup slot" and save init_boot, boot, vendor_boot, dtbo, recovery, vendor_dlkm and vbmeta from the chosen slot if any of them exist.
If vendor_dlkm doesn't exist on an older device it doesn't make sense to show "Not Found" all over the place, nor offer to allow me to map it, it should hide those messages/buttons and just only show boot or whatever other partitions exist on the device.
If the reboot button had a ... to reveal an advanced reboot menu (menu items like the Magisk app) that would be excellent!
Magisk/RebootEvent.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk/XSU.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Overall looking really good! Exciting to see a well written free alternative.
osm0sis said:
A few random thoughts/ideas while testing on my 8T
Click to expand...
Click to collapse
All good ideas. Probably good enough to check by path for the existence of a partition, rather than finding and parsing fstab. My next two weeks are brutal, but I'll see if I find some time to fiddle with it in there.
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
shoey63 said:
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
Click to expand...
Click to collapse
The backup format is very basic. You could easily drop the image you want into the backup folder and create the properties file. I'll take a look at adding something to simplify direct flashing in the next few revisions. I'm out of pocket through the weekend and will probably need a few days of catch-up when I get back.
----- posted in error ------
can I flash an uncompressed boot.img file with this app? the github only mentions flashing an AK3 zip file, so I was curious
sorry, I see the other reply. I'm hoping this app gets this feature in a future update soon. making a video about this app right now
Doesn't open up on Pixel 6. Anyone has a similar problem?
radekmazur said:
Doesn't open up on Pixel 6. Anyone has a similar problem?
Click to expand...
Click to collapse
Does it throw an error message? If not, is there anything in the logcat?