got myself a XQ-AS52 xperia 5 II for cheap to use as a permanent car navigation system.
is there any full custom rom's for this device?
taking a look around and it seems a tad more confusing than other phone's?
usually it's just flash TWRP. erase system. flash rom+gapps+magisk and done.
but i see weird mentions of having to flash ontop of stock? and use multiple TWRP versions?
not sure what's up. is there any clean rom out there that i can use to fully replace the stock sony software?
I recommend to check out lineage os as they provide a step by step installation guide in their wiki.
Install LineageOS on pdx206 | LineageOS Wiki
wiki.lineageos.org
Lineage doesn't work for me, but voidui seems pretty stable to be so far and has everything built in
Related
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
Some background: I'm coming from an OP3 which did not have this Slot A/B thing and you could easily just flash firmware going forward. I'm currently confused as to how custom roms will update firmware and such going forward.
I noticed there's 'systemless' roms now (like NoLimits), I don't really understand what the advantages/disadvantages vs something like Havoc OS are.
If I go with a custom rom, will I need to flash to OOS to update firmware then reflash back to the custom rom in the future?
I apologize if these are really newb questions, trying to find specific details with some of these keywords makes it really hard to find relevant information (and I've tried).
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Link above is some info on A/B partitioning.
The benefit of systemless ROMs are that they are just Magisk Modules so installing and uninstalling is very easy. You don't need to boot into recovery or wipe anything.
Havoc is a full ROM and based on AOSP so wiping is needed, especially when security patches are different. Some people are decrypting their phones with the no verity zip but I won't say too much about that to keep things as simple as possible.
You don't need to flash any OOS firmware when on Havoc, and I think it's because custom ROMs have their own vendor image. More advanced users feel free to correct me if I'm wrong about this.
Flashing isn't really too different and I personally don't even think about A/B slots. You just need to remember to flash the TWRP zip file after a ROM flash to keep TWRP. And you also need to reboot back into recovery to install Google apps, rather than just after the ROM flash.
Custom kernels are now flashed last (after TWRP and Magisk).
This is how I've done it and have been issue-free.
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
EDIT: Join telegram group @clarkdev for beta testing or see development
Hi, i'm in!
DarkDroidDev said:
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
Click to expand...
Click to collapse
Link?
i 'm in too..
Link?
@DarkDroidDev already sent the DM from telegram
Выложите пожалуйста √17
Development resumed, who want to see progress or help with testing, feel free to join telegram group
@clarkdev
Any chance you could provide links without telegram?
Not looking to add another messenger that I'll forget I have in 6 months lol
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
I'd also be interested but don't use Telegram
ac2323 said:
I'd also be interested but don't use Telegram
Click to expand...
Click to collapse
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Nice.
Wheels564 said:
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Click to expand...
Click to collapse
Yes, working nice.
@DarkDroidDev Hey, how did you extract the proprietary blobs? The instruction says that one needs to have an installable zip of LineageOS for clark, or already have the device runnning the LOS. I tried to extract it just from my stock Moto X Style with the script and it did something, but I'm not sure if it's going to work.
Edit: I'm also interested in testing the 17.1 build, since the one I'm trying to build following the instruction is 14.1 and actually it fails because of lack of some vendor files :/ But I'm also not interested in joining Telegram
Edit: Oh, I missed the @chrmhoffmann post!
hi, chrmhoffmann. thank you for your work.
chrmhoffmann said:
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
Click to expand...
Click to collapse
Hi, chrmhoffmann. Thank you for your work. I previously tested your 20200718 upgrade. I have installed the same date recovery and the latest magisk20.4. Unfortunately the system will not start. I also tried wipe system wipe cache wipe data and reinstalled it again, but it still didn't work.
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
kb8no said:
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
Click to expand...
Click to collapse
From what I've seed Darkdroiddev removed Clark from his Github so I assume he is no longer working on this phone and this thread is probably dead. Randomblame hasn't posted since February. chrmhoffmann's thread https://forum.xda-developers.com/mo...opment/unofficial-lineage-17-1-clark-t4123077 actually has a link to official Lineage gerrit which means we are well on our way to becoming official Lineage again. Meanwhile I'll keep posting LOS 14.1 for MMBL until we get there.
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
magermerch said:
So I'm pretty new on the whole android customization scene and I've been really wanting to install Android Open Source Project on my Android 10 phone for a while. I've found a video detailing how to go about it, but my problem is that there's not a version of TWRP for my specific phone yet (I have a Blackview BL6000 pro). For the purposes of making a recovery and installing AOSP, I'm wondering if there's another good app that could replace TWRP that functionally does the same things (Or if someone has a TWRP version somehow) that lets me install AOSP.
The video in question I was using as a guide was this one:
Any help would be hugely appreciated!
Click to expand...
Click to collapse
You not need TWRP for flash GSI (Custom ROMs). You need stock firmware of your device from company or you should make that your self about any problem with your actions.
After you can know how to do have GSI in your device with commands fastbootd: Installing GSI with fastbootd
and/or using this software: Treble Toolkit [A and A/B]
Ofcourse if yourr device is A/B so you need flash the GSI.img in the system_a or system_b so need know what slot is able to that.