{
"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?
Related
{
"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"
}
V4.31.44.12
v4.32.44.12 applied with theme from he_stheone64.
Important note:
I create the Desire Series together with freak, and also got a lot of help from many technical experts, so, please thank them as well if you like the build.
This thread is for discussing the SD builds only.
All the releases please check: http://forum.xda-developers.com/showthread.php?t=962600.
Please discuss the NAND builds at: http://forum.xda-developers.com/showthread.php?t=913597&page=457
Before flash or install new builds:
1. DON'T expect it will work out of box.
2. DON'T expect it will be as light and fast as Gingerbread.
3. DON'T expect that some legacy problem will disappear
4. Reboot your phone at lease twice after flashing or installing, after 1st boot into setting screen, long press the right button to recall the boot menu, reboot. Can not use /Update_DL method to install app before 3rd reboot.
5. For this version, due to the base has been changed throughly, can not use previous data.img or ext4, remove existing data.img and set data_img=1 to let system generate one for you, or set format_ext4=1 to format your ext4 if you are using ext4
6. DON'T set any config for 1st installation except data_img=1(for data.img) or format_ext4=1(for ext4 user). if your have tmous phone, no need the config.txt.
7. For SD or magldr, if 1st installation failed, must delete the system.ext2 file under /Desire_DL to let system convert it again.
8. Use Windows notepad create a file named config.txt, save it under /Desire_DL, only need to put the necessary config inside it, say:
data_img=1
Important Release Note
This build is another endeavor by freak and me to improve the performance of our build, now, besides our existing optimization methods: squashfs, ext4, etc, this build has been added in the following features to improve it performance furthermore:
1. AUFS + SquashFS.
this is the 1st android version that can support the aufs+squashfs, we
even worked with the author of aufs to make it usable to android.
a lot of innovations within this build from the technical perspective,
for users, the benefit of it are:
a. high performance
b. despite of squashfs is used to reduce the size of file system, user
still be able to change any file directly with the power of aufs.
c. a lot of frequent accessed files are squashed and loaded into ram
to improve the performance.
2. RE-Odexed.
there flood a lot of misleading messages on xda of odexed, same as
squashfs. Odex can actually improve system performance, and at the
same time, reduce the whole system's size(because the odex is
optimized dex), and odex build has less chance of system crash that
lead to wipe the davlik-cache. an odex build doest not generate the
davlik-cache which is odexed.
3. Re-Engineering Sense:
All the apps and framework were re-compiled and reduced the size to get the lowest RAM consuming and Highest performance.
4. Merged DesireZ and DesireHD into one.
Merged the advantage features from both DesireZ and DesireHD into one build.
Please refer to this thread for download and detail info of v5.xx
DOWNLOAD
DL Desire v4.31.44.12
Light themed with power notification and battery percentage.
DL Desire v4.32.44.12
Themed with he_stheone64.
Converted system.ext2 for DL.Desire.v4.31.44.12, thanks mamdouhn
part 1
part 2
part 3
DL.Desire.v4.32.45.13 SD only with DLZ_update_20110307-2034
part 1
part 2
part 3
Note: you are always appreciated if you can help upload the converted system.ext2 for SD/MAGLDR, how to do:
after your system successfully boot into sense, and feel the performance is great, delete the system.img and data.img, zip the /Desire_DL folder and upload it, for some ppl have problem of converting the system.ext2 from system.img.
Click to expand...
Click to collapse
How to config SuperInit v4.4(advance user)
Bugfix and enhancement
Upgrade to v4.32.45.13 and v4.31.45.13 (yes, we upgrade the SuperInit and kernel together.)
How to ask for help:
1. First, make sure you ask at the proper place, this thread is only for ask the question related to the NAND, please ask questions related to SD or MAGLDR at http://forum.xda-developers.com/showthread.php?t=881937
2. Please indicate the following information when asking for help:
a. your phone modal: EU or TMOUS modal.
b. your loading mode: NAND, SD or MAGLDR
c. Please post the content of init.log(this file is on the root of your sdcard).
3. Please be patient and polite.
4. We(myself and freak) will only answer question that follows the above rules, thanks!!!
Naming convention
1. the 1st digit is for the build base, say DesireZ v4.xxx, is for the v4.0 base which based on the HTC RUU 1.85.
2. the 2nd field is for the subversion, normally, x.0 means the first relase which should based on a totally new base, and from x.0 till x.3, there will be a lot fix and testing, if you want a stable version, DON'T use it, and the build will be stabilized after x.4.
3. the 3rd field is for the init version, currently, our init is at v42, which is also not a stable version.
4. the 4th field will be used for the kernel, currently, freak is working on it, and will have the 1st kernel soon.
Video
v2.1
v2.6
Thanks happyendin21 for recording this wonderful video, which demonstrate my build v2.1 and v2.6
Older SD version:
DL DesireZ v1.0
DL DesireZ v0.3n
For version before v3.0
- extract "desire_z" folder on the root of your SD card
- Run "CLRCAD.exe" then "haret.exe"
[/COLOR][/B][/QUOTE]
Special thanks to
wingmann, E Lin, D69K, McNiceGuy, vlad48, RicarduZonta, akshan, Alexei, Kam,
adeeb, Shane Grosser, Kenneth Davis, Muhammad, Joe, parzifal, F-bone,
TruePlaya, Eric, kajos, b0nni....
[/SIZE]
Click to expand...
Click to collapse
Thanks to
- Cedesmith, Cotulla, ownhere, melethron, ocm, Rajko, LeTama, Hastarin, NetRipper, Markinus, gauner1986, Takaaki, iamgpc and others I may forgot.
Click to expand...
Click to collapse
Ah, fresh meat
Hmm Downloading.
all cedesmith fans must try this , please make changelog for next update
Thank you so much
its rebooting on the HTC screen
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Some screens please...
Sent from my HTC HD2 using XDA App
The Rom is excellent
really fast
so far everything is working apart from being unable to connect to WiFi ( stuck on Obtaining IP address.... )
Any Solutions ??
shahzads said:
its rebooting on the HTC screen
Click to expand...
Click to collapse
This build will not create the data.img automatically, hence, you have to supply a data.img file,recommend to use the one I listed above.
Screen Shots
WiFi do not work.
Thank you ,i like this ROM
Wow This one out of the blue
I am flabbergasted by this rom vast stable
Speechless
only minor and yes i am about to say this again Wifi doesnt work
dandiest said:
This build will not create the data.img automatically, hence, you have to supply a data.img file,recommend to use the one I listed above.
Click to expand...
Click to collapse
thanks for telling us that can you please put this info on the 1st post too
Renegade_Rulez said:
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Click to expand...
Click to collapse
same issue here, how do i set it to static ip? do we have to enter in the APN? i thought it was auto
Renegade_Rulez said:
It works but wifi DHCP is not working (setting it to static IP works just fine) and HTC twitter (peep?) is missing?
Click to expand...
Click to collapse
Yes, I removed the twitter and some other applications, if needed, I can put the pkg here, you just put it under /system/app.
ajax0666 said:
I am flabbergasted by this rom vast stable
Speechless
only minor and yes i am about to say this again Wifi doesnt work
Click to expand...
Click to collapse
Believe it's the problem for the file permission, I only managed to fix the pppd due to I don't have wifi here, maybe will try to fix it later.
I will be visiting this forum often to see the progresses of this build.
Other thing i came accros was that titanium backup cant get root permission
dandiest said:
Yes, I removed the twitter and some other applications, if needed, I can put the pkg here, you just put it under /system/app.
Click to expand...
Click to collapse
Yes, please post the twitter pkg.
Thanks
I don't always follow a new device during the troubled early days of root...
...but when I do, I'm utterly scarred by the chaos and confusion.
Since I've watched the current V20 root exploit evolve from "maybe DirtyCow would work here" into a full-blown war on Nougat's sepolicy, and finally into the emergent "Recowvery"; I thought it might be fun to get my own hands a little dirty and write some wrappers to automate the rooting process with ample error-checking along the way.
>> Please take a moment to check out @jcadduono's Recowvery thread at http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 for more information, to say "thanks," and to donate if you can afford it. <<
WARNING: ATTEMPT AT YOUR OWN RISK! THIS PACKAGE IS RELEASED AS-IS AND WITHOUT ANY WARRANTY, IMPLIED OR EXPRESSED
THIS PACKAGE MAY MAKE YOUR LIFE EASIER (or harder) BUT NOTHING CAN FULLY PROTECT YOU FROM TROUBLE WHEN ROOTING A DEVICE!
IT IS NOT MY RESPONSIBILITY IF YOU END UP WITH A BRICK IN YOUR POCKET AFTER ATTEMPTING ROOT
{
"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"
}
Current, Planned, and Not Guaranteed Features:
- Windows support, including a truly die-hard adb check
- Push, exploit, and flash all in one step
- Optional automated SuperSU installation
- Bundled adb for more predictable results
- More error checking than you think you'd need
- Auto-disable dm-verity and forced encryption
- Optional selinux permissive mode
- Restore boot and recovery to stock
- Spawn a root shell for exploration and such
- Grab any recovery.img you'd like to use from /sdcard
- Linux support (needs to be reworked )
- Ability to download latest exploit and recovery at runtime
- Extra helper commands for stuff like trying to break out of bootloops or quickly grab logs
- Basic GUI for Windows
Download:
Latest version: 1.3b3
Grab the latest zip: https://github.com/bziemek/EasyRecowvery/releases
Or browse the source: https://github.com/bziemek/EasyRecowvery
--
TWRP for the H918: in jcadduono's thread, Step 3
no-verity-opt-encrypt: also in jcadduono's thread, Step 3
SuperSU: in Chainfire's beta thread
Instructions:
https://github.com/bziemek/EasyRecowvery/blob/master/README.md
Greetz:
Huge shout out to @jcadduono for running with the DirtyCow idea and making this root possible (read more and THANK HIM HERE), Chainfire for taking some time off to do a test install of the latest SuperSU hours before we had a working TWRP, @Darriousx and @slayerh4x for all their hard work testing, and #twrp on Freenode for generally putting up with the lot of us!
Donations:
IF you feel so inclined, PayPal some coffee and beer money to [email protected], or BTC to 1bu5MMgagtbN7QVeciyWfAzRbfk8vmynM
Many thanks to @Pjs187, who furnished the first donation I've received here at XDA!
Frequently Asked Questions
Why isn't it working?
First: update your ADB. If you don't have ADB, then you'll want to fix that before you spend another second at XDA. I personally only use official releases from Google, so I might not be much help if you're using something you found at random at XDA or elsewhere on the Internet. You can download Google's latest release of their tools from the very bottom of this page. (I recommend installing or extract them to C:\Android for easy access.) Using the "SDK Manager" included in that download, choose to install "Android Platform-tools" and "Google USB drivers", and remember to run it again once in a blue moon for updates.
If ADB isn't the problem, I'm happy to offer what assistance I can. Please describe what you were trying to do and how, then attach any .log files the script created.
Where is TWRP?
The link to the latest version is linked in this thread under Step 3.
Rename the downloaded file to recovery.img and put it on your internal storage.
Does Data need to be wiped?
For everything to work properly, YES. If you don't have an inherent understanding of what will happen if you don't run a Format Data, then please do so the first time you enter TWRP. This will erase Internal Storage and remove the default encryption so that TWRP can function to the fullest. BACK UP YOUR STUFF FIRST!
Is no-verity-opt-encrypt necessary?
YES, but not totally. This ZIP makes it possible to allow system modifications, and prevents a couple easy ways to end up with corrupt data or bootloops.
Download that from Step 3 in the thread above, and put it in the folder named zips next to EasyRecowvery.
If you're going to install SuperSU right away, you shouldn't really need it.
What is selinux?
selinux is a major security feature, and also a major pain in the butt depending on who you ask.
If you don't know if you need it in "permissive" mode, just leave it be. You can always reflash later.
Why isn't TWRP showing Internal Storage?
These phones use encryption out of the box. In order for TWRP to function properly, you will need to use the Wipe Data feature after installation.
This will blow away everything on your Internal Storage, so make sure you don't have anything important in there!
Changelog
1.3b3
Add more sanity checks
Add note about formatting data
Separate log for ZIP flashing
Rename bundled adb.exe to adb-recowvery.exe (maybe)
Older Versions
1.3b
Bundle adb.exe (can be toggled in Extras menu)
Improve and fix adb and device checks
1.2b
Add experimental support for auto-rooting.
Add an extra mode to flash no-verity-opt-encrypt.
Add an extra mode just to reboot into recovery.
1.1b-hotfix
Add the "zips" folder needed by the new version.
1.1b
Skip several versions and change versioning style.
Redesign the menu system.
Auto-flash no-verity-opt-encrypt.
Update Recowvery to latest version.
Tweak prompts, formatting, and fix typos.
More aggressive connection handling.
Fix the restore feature.
Allow disabling integrity verification (untested).
Increase logging verbosity.
Fix line endings in EasyRecowvery.cmd
beta5
Take a nap.
Fix some issues with various prompts.
Adjust some formatting.
More testing.
beta4
Improve adb checking code.
Reluctantly accept that we should try recovery.img.img.
Misc. tweaks to prompts.
beta3
Fix several parentheses that might be causing trouble.
beta2
Fix a bug causing EasyRecowvery to fail when run from another directory.
beta1
Initial release.
WOW! This is what i've been waiting for. Thanks man!
Thanks for this. Will help a lot of users who are Leary about the cureent manual process
Awesome...
Awesome man, so cool to watch all this develop. Glad I could be part of it.
definitely looking forward to this. sweetness!!!!
It has been amazing watch all this develop in the past weeks. I have been flashing and rooting for about 10 years and this is the first time I've seen it all from the beginning. It is really amazing what a few of these guys are capable of...but this time for me I was left speechless. Gentlemen, (and ladies?) Thank you for all of your free time and dedication for making this possible for the average end user like me. We all don't show enough gratitude and I'm sure I'm not the only one amazed my all of your capabilities. Keep up the unbelievable work, and a nice donation is coming to everyone who contributed if I can find a way to donate to you all. Point me in the direction, and the cash flow will be on its way. Thank you again.
Sincerely,
dmoney4eal
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
whowatchlist said:
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
Click to expand...
Click to collapse
There will be some big ol' red letters in here before I attach any files - you can bet on that
pro_granade said:
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
Click to expand...
Click to collapse
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
bezeek said:
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
Click to expand...
Click to collapse
I could write it in batch and convert to exe.
pro_granade said:
I could write it in batch and convert to exe.
Click to expand...
Click to collapse
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
bezeek said:
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
Click to expand...
Click to collapse
It'd be a lot quicker if I actually had the device. I'll probably let you go for it lmao
Race, race, race!
The winner gets the most thanks??
poczynek said:
Race, race, race!
The winner gets the most thanks??
Click to expand...
Click to collapse
How about some money lol
Is this still a WIP? I don't see anything updated by the OP. I'm waiting to root and something like this would be great as I am leery of going through the regular method with ADB as I'm coming from a Samsung device.
I pledge $20!.
*** Disclaimer
Code:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about the instructions or the linked things before doing anything!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you and I promise, I will!
Introduction
I decided I wanted a more up-to-date CM11 build, so here it is, a new build of LineageOS 11, for D605!
Images
{
"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"
}
Features
* Quite default LineageOS 11 but with USB OTG and offline charging
Installation instructions
* Under construction
Changelog
* Creating once finished
Downloads
Checksums:
* Uploading once finished
Download
* Uploading once finished
Sources
* https://github.com/Avamander/android_device_lge_d605
* https://github.com/Avamander/android_kernel_lge_d605
FAQ
* Under construction
Thanks To/Credits
Code:
* Varcain
* Puresoul_CZ
So, let me know if you're even interested.
XDA:DevDB Information
LineageOS 11 for D605, ROM for all devices (see above for details)
Contributors
Avamander, Varcain, Puresoul_CZ
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-09-25
Last Updated 2020-07-04
Planned:
* Fix to reallow XPosed
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
thePanz said:
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
Click to expand...
Click to collapse
About CRACK, haven't checked, not sure a patch has been released for LOS11, if it has after the build date, let me know and I'll rebuild it.
I used the this https://wiki.lineageos.org/devices/d855/build but replaced d855 in commands with d605 and manually downloaded the sources to the according folders.
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
thePanz said:
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
Click to expand...
Click to collapse
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Avamander said:
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Click to expand...
Click to collapse
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
thePanz said:
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
Click to expand...
Click to collapse
Let me know if the latest works. If it doesn't, let me know if TWRP works
Avamander said:
Let me know if the latest works. If it doesn't, let me know if TWRP works
Click to expand...
Click to collapse
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
thePanz said:
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
Click to expand...
Click to collapse
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Avamander said:
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Click to expand...
Click to collapse
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
thePanz said:
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
Click to expand...
Click to collapse
That means it would still break the signature if I would release a signed image.
Quick update: the offline-charging is not working.
Switching off the phone and connecting the charger will boot up the phone in the default mode, not "only charging".
I know this might be a minor bug but auto brightness doesn't work.
DJ-SMOKE_300 said:
I know this might be a minor bug but auto brightness doesn't work.
Click to expand...
Click to collapse
Never has, never will, there's no brightness sensor hardware.
Avamander said:
Never has, never will, there's no brightness sensor hardware.
Click to expand...
Click to collapse
Oh. Thanks for clearing that up. All in all its mostly stable. :good:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
DJ-SMOKE_300 said:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
Click to expand...
Click to collapse
Seen that happen a few times, but without logs of the crash I can't help you.
1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?
---------- Post added at 23:26 ---------- Previous post was at 23:11 ----------
Avamander said:
(...)
Installation instructions
* Use TWRP, wipe everything, (...)
Click to expand...
Click to collapse
Is there really a reason to clean Internal storage and sdcard?
> 1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
It's more work to create the file for the recovery to verify it. The space is part of the link.
> 2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?[
Nope
> Is there really a reason to clean Internal storage and sdcard?
Internal storage? If you mean /data, yes, but /sdcard doesn't need to be wiped.
As a sidenote, I've been rebuilding the entire system today, will see if that brings back the WiFi.
MARS SOM
{
"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"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone
Reserved <3
Nice work. I'm glad to already see some custom ROMs (well, in that case, SOM).
However, this is the first time I encounter a SOM, is it just a Magisk module that can be turned on and off at will, switching between stock and Mars? Or shouldn't I do that?
Miustone said:
Welcome to MARS SOM
The first so called SOM
Systemless-On-Memory
SOM - The right naming for a new age of Android ROMs
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into two Zip Files...
Features:
Full Camera API2 Support
Full Pixel User Interface
Full Darkmode Support
Ported Pixel Apps
Ported Pixel Features
Enabled various Android Features
Enhanced Security Support
Enhanced Display 4K HDR Support
Enhanced Audio Output
Enhanced Audio Input
Enhanced Display Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Beta or Canary Channel
Android 11
A way to extract and create Zip Files
(For GitHub Zips)
Downloads:
Miustone - Overview
Founder of Dev Ice Software Technologies. Miustone has 10 repositories available. Follow their code on GitHub.
github.com
Note: Zips from GitHub can't be flashed ootb.
GitHub?!:
Extract the 2 Downloaded Zips and repack everything inside of the second "MARS_SOM_XXX" Folders to Zips
Flash these Zips with Magisk and enjoy <3
Bugs:
QuickSwitch is needed for the Pixel Launcher
Donations:
paypal.me/miustone
Click to expand...
Click to collapse
Could you please tell me where can I obtain more information about this "Mars Som" and more details instruction to install it. Thanks for your reply.
Thanks for Your Interest! I'm reconstructing the SOMs on GitHub and the ReadMe's there will be updated soon with more Infos! For now, just Check My (Discontinued) MARS-SOM Repo on GitHub...
BR
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
tonysunshine said:
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
Click to expand...
Click to collapse
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Miustone said:
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Click to expand...
Click to collapse
Hi what do you mean by use them separated? Like install/activate the base module, reboot, then do the system module?
Yep, it could be one of them or both which causes the Bootloops. I updated the Base so it might be that... The System should cause less Problems at the end... @tonysunshine
I also got a bootloop after installing the zips. I tried following the instructions on your github and was able to do the device simulation with the props config module, but can't follow the next step "Download and extract the NgaResources.apk to /MARS_SOM_SYSTEM/system/product/app/NgaResources" as there's no NgaResources.apk file anywhere on the github that I can find. Could it be this missing file that's causing issues?
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
akkk44 said:
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
Click to expand...
Click to collapse
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Miustone said:
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
akkk44 said:
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
Click to expand...
Click to collapse
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Miustone said:
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Click to expand...
Click to collapse
Understood! I will test the module out sometime……
akkk44 said:
Understood! I will test the module out sometime……
Click to expand...
Click to collapse
Great! Thanks in advance!
Miustone said:
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
tardis_42 said:
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
View attachment 5445471
Click to expand...
Click to collapse
Thanks for pointing out. I'm uploading the latest Version to this Google Drive Directory rn! Sorry for the Trouble...
Updated the Thread, MARS_SOMs and GitHub<3
HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias
The original purpose of these three apps was to help deal with the changes in Android 12 when taking an OTA. Most of the functionality has been superseded by the newest builds of Magisk.
Vbmeta Patcher is still useful when migrating from Magisk builds before 23016, and Boot Image Tool can still be used for downloading backups of newly installed boot images or restoring missing backups for Magisk.
I'll leave the links and descriptions below, but future development of these apps is unlikely.
Spoiler: Links and Descriptions
{
"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"
}
Vbmeta Patcher is an Android app that toggles the disable flags of the vbmeta partitions.
Devinfo Patcher is an Android app that marks the inactive slot as successful on devices with a valid devinfo partition.
Boot Image Tool is an Android app that helps juggle boot images for OTAs.
Spoiler: OTA Instructions for Magisk 23017+
Uninstall -> Restore Images in the Magisk app.
Take the OTA in System Update. Do NOT reboot.
Install -> Install to Inactive Slot in the Magisk app.
Reboot (NOT in System Update).
Latest Updates
2022-05-01 Boot Image Tool v1.0.0-alpha03
2021-11-19 Devinfo Patcher v1.0.0-alpha02
2021-11-19 Vbmeta Patcher v1.0.0-alpha04
Nice work and idea!
Amazing bro, thank you! So excited to see development starting off for this nice phone.
Any address to donate to?
Nice program, good job. Thanks..
Hecke92 said:
Any address to donate to?
Click to expand...
Click to collapse
I look at it as my contribution back to the community. If you really want to make a monetary contribution, I suggest Code.org or EFF.
Because of your developers, Android has become more exciting！
I
this is really cool, thank you!
hope someone make twrp for our device or find the way to flash patched_boot.img without PC
Why dont you flash the factory image to both slots directly?
I did that with the pixel 4 Xl all the time.
Someone postet the steps to flash factory images , including the commands to disable verification for vbmeta.
Whats the advantage to do it via OTA?
pa.pn2 said:
Why dont you flash the factory image to both slots directly?
Click to expand...
Click to collapse
The downside to flashing to both slots is you lose the fallback, if something goes wrong.
pa.pn2 said:
Whats the advantage to do it via OTA?
Click to expand...
Click to collapse
As long as we need another device to fastboot boot the patched image, there isn't a huge advantage to doing it this way. For me, it's just more convenient to do everything on the phone, then I can reboot to fastboot and boot the patched image the next time I'm at the computer.
If we can get flashing to the inactive slot working, then that would completely eliminate the need for another device, which is the ultimate goal here.
When Magisk installs to the inactive slot, it downloads a nearly 3 year old bootctl binary to set the inactive slot as active then to mark boot successful on the next reboot. I can't find any documentation on the source used for that binary, but I suspect that it doesn't know about the devinfo partition.
During the update process, update_engine sets various flags (including the active slot flag and the successful boot flag) via the boot control interface. The Pixel 6 has two implementations of that interface, 1.0, which sets the flags directly on the boot partitions, and 1.2, which sets the flags on the devinfo partition, with a fallback to the 1.0 method in the absence of a valid devinfo partition.
I wonder if simply replacing the bootctl binary with one built against a newer version of Android would be enough to resolve the problem.
This sounds to me like Virtual A/B devices were the reason for the removal of patching the inactive slot:
Broken display logic for "Install to Inactive Slot (After OTA)" option · Issue #3963 · topjohnwu/Magisk
mi11 miui12.5 After installing magisk22.0/22001, the "install to another slot" option disappears. Reinstall magisk and system still can't enable this feature. DEVICE DESCRIPTION Model: Mi11 Android...
github.com
Pixel 6 is Full A/B, unless I'm missing something. I wonder if the old method with a new bootctl binary would work on Pixel 6. I managed to build bootctl against the aosp_oriole-userdebug (android-12.0.0_r12) source. It at least prints the right values. I have not attempted to use it to make changes.
I made a build of the latest Magisk with bootctl built against the Pixel 5a source, enabled installing Magisk to the inactive slot on a Pixel 5a, and was able to take the November OTA on a Pixel 5a without a computer and without losing root.
The steps were
Restore boot in the Magisk app.
Restore vbmeta in Vbmeta Patcher.
Take the OTA in System Update. Do NOT reboot.
Patch vbmeta in Vbmeta Patcher.
Install Magisk to the Inactive Slot in the Magisk App.
Until a few other people have tested it, this process should be considered experimental. Should anyone attempt it, I would suggest backing up any critical data.
I did not test the process with the old bootctl, but that one wouldn't work for Pixel 6, anyway. I'm not yet sure if the Pixel 5a build will work for Pixel 6, either. If not, I also have a version of it built against the Pixel 6 source.
Note: Since 23016, there's no longer a need to patch the vbmeta partition.
The tests done in this post made some faulty assumptions, so I removed the results to avoid confusion.
capntrips said:
The Pixel 6 build of Magisk using the Pixel 5a version of bootctl did not work, so I pulled the download. It got stuck in a bootloop, so I had to set my slot back to B in fastboot.
I'll make another build using the Pixel 6 verson of bootctl, shortly, and try again.
Edit: As with the previous build, it got stuck in a bootloop. Unfortunately, it takes forever to run tests, since the optimizing apps step takes about an hour, but I'll continue working on it over the next few days.
Click to expand...
Click to collapse
Google released an extraordinary firmware .037
there is a good opportunity to test your program. Unfortunately, my phone is still on the way.
bzz11g said:
Google released an extraordinary firmware .037
there is a good opportunity to test your program. Unfortunately, my phone is still on the way.
Click to expand...
Click to collapse
The post you quoted are the results of testing the upgrade from .036 to .037. The steps from the OP should work fine, but the ultimate goal is to be able to take the OTA and remain rooted without the need for a computer to fastboot boot the first time.
Would this work?
- restore boot with magisk
- restore vbmeta with Vbmeta patcher
- take ota update
- use Boot Image Tool to pull boot.img from opposite slot
- patch it with magisk
- use dd command to flash back to opposite slot
- patch vbmeta on opposite slot with Vbmeta patcher
- reboot
- profit?
shoey63 said:
Would this work?
- restore boot with magisk
- restore vbmeta with Vbmeta patcher
- take ota update
- use Boot Image Tool to pull boot.img from opposite slot
- patch it with magisk
- use dd command to flash back to opposite slot
- patch vbmeta on opposite slot with Vbmeta patcher
- reboot
- profit?
Click to expand...
Click to collapse
This is effectively the same thing that Magisk does, just without the bootctl bits. I tried it anyway, just in case, and it bootlooped.
On a related note, if you let it bootloop more than 3 times, turns out it will automatically switch back to the old slot. Doesn't really save time if you're already plugged into a computer, but handy if you have something else you can be doing for those few minutes.
I manually toggled the successful bit for the inactive slot in devinfo and it booted right up.
I'll make a Devinfo Patcher to go along with Vbmeta Patcher and release it in the next few days.
Depending on what we can get the Magisk devs to support, I may make an all in one tool. I would rather not have to maintain ongoing Magisk builds, so hopefully we can at least get the option to enable flashing to the inactive slot.
Edit: I submitted my findings to the Magisk devs. We'll see what they'll be willing to support.
Are these tools only for the pixel 6 or could it work on other A/B devices?
IamTheBRAVE said:
Are these tools only for the pixel 6 or could it work on other A/B devices?
Click to expand...
Click to collapse
I made an effort to make them relatively device agnostic, but no testing has been done on anything but a Pixel 6 and to a much lesser extent, a Pixel 5a.
The only value that immediately comes to mind that may be somewhat specific to Pixel 6 is the 8192 byte vbmeta image size used to calculate the SHA1 hash, but it shouldn't affect its ability to read and patch the flags. I should probably try to figure out how to calculate the size, at some point.
All of the code for reading the data is in the DeviceState and SlotState files in each app, and I made an effort to link to the relevant code in the Android source for each function, if you want to check it against the sources for your own device.
If you try them out, let me know how it goes.
Edit: It looks like the size should be easy enough to calculate (fixed header size of 256 bytes + authentication_data_block_size + auxiliary_data_block_size). I'll make an effort to get that fixed after I release Devinfo Patcher.
Edit 2: This is done and is included in v1.0.0-alpha04.