I have flogged 20 times already and I can't get out of the bootloop. I have the problem of touch, and sometimes I flick the Apollo-v8 after userdata.img. Other times I flick the boot, vendor, vmeta that indicates in Ghitub. But I don't get the functional rom.
Can you please tell me the steps clearly when it is a dual sim xz2c with touch problem?
Thank you very much and excuse my translation.
Thank you. Some doubts, due to my little English, I find it hard to find the right addresses.
Yes, it is sad.
Or you wait for LineageOS 17.1
I always recommend a fullwipe before switching from Android X to Android Y
I use migrate (needs twrp, which I will look into after LineageOS is ready for public testing/usage) and titanium backup (needs only root) as backup & restore solutions
Thanks for answering, but I don't understand.
When it indicates twrp flash twrp and for other system: for twrp which one do I use? the twrp apollo_v8? And for the system, which one should I use?
Most importantly, I don't understand the right steps.
First I made the manual:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem _ *. img (Tama (latest) -> https://developer.sony.com/file/down...rnel-4-9-tama/
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG
Here, I don't know how I should do:
- Should I flash Apollo_v8?
- Should I flash fastboot flash boot boot.img and fastboot flash vendor vendor.img from Testbuild folder?
- Should I flash other things?
(SORRY, I always VMETA)
I have tried a multitude of options, with Twrp_v8, with boot and vendor, and bootloop, and with different twrp that do not work the touch and I can not continue ...
I strongly urge you to indicate the steps please.
You mean there will be a support for LineageOS 17.1 ?
And those backups would be compatible from OmniROM 9 to AOSP 10 ? (And I guess there is no way to recover my OmniROM customisation, UI changes and ringtones for instance, correct ?)
Instead of a backup, what could be the risk if I only boot to the image (and not flash it) to see if everything goes well ?
Thanks for your anwserYes, at the moment compiled for the XZ2 on my local machine to test in my next free time.
Migrate and Titanium only backup your apps, so you can restore them on every phone/rom.
About the customizations -> Google backup did backup some at my side, but make sure you don't make a new google backup on a different rom.
I don't know which issues may occur if you don't wipe your userdata.
Switching between ROMs/android versions may cause issues.
Thanks for your anwser
Ok, that would be great, AOSP is a bit… basic ^^
Apps and their content I guess ? (such as message history and so on)
Including system settings ?
After a wipe, will I have to root my phone again ?
Is there a way to do a full backup (including the system ?) just in case something goes wrong and I want to restore it ? (in its initial state before migrating)
I'm not using Google backup (or any Google stuff) so no issue here.
Switching may cause issue, only if I flash it or even with a simple boot ?
#include <std_disclaimer.h> /* * * We are 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 features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
jerpelea said:for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
i thought pushing a maintenance update would be a good idea.
Sadly it wasn't achievable.
I tried to simply rebuild the old sodp sync with the newest omnirom, also synced the newest sodp stuff wit the newest omnirom.
But that every time resulted into
1. Installing gapps on a fresh system let the device crash into twrp with the message "set_policy_failed:/data/cache/"
2. Upgrading from the previous version resulted into "no web views detected". The webview is needed for some apps to render their content. Without that they would simply crash.
Regardless if the gapps, aosp or bromite webview was installed, none was listed and the logcat throws errors.
3. The audio doesn't route anymore to a connected usb audio 3.5mm adapter.
4. There may be more bugs, but i am too frustrated to with the already occurring bugs and invested hours/days.
Lets look optimistically into the future of android 10.0, kernel 4.14 and which custom roms can be build on it.
omnirom 9 may be deprecated, but it seems that they backport security fixes.
Soooo, we get still security updates.
On the other side i got insulted (called a stupid idiot), warned, kicked and banned at once for asking about the security commits and saying that the insulter has a low emphatic intelligence.
I look if i will continue distributing stuff for this toxic community administration.
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
fastboot flash boot boot.img fastboot flash vendor vendor.img fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast omnirom switches to q.)
omnirom with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
attached oemv8 images at the post
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled after i released the oemv8 sonyaosp builds.
bug & feature tracker