PixelExperience ROM 2019-12-13
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
It is recommended that you use the latest ugglite Xiaomi firmware. (2019.11.05 Global)
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery) My TWRP: LINK
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
Unfortunately all AOSP-based ROMs are still in the test phase, so we wait for a stable OS.
GAPPS included
DOWNLOAD ROM
Made at viethoang18's request. No additional support. I don't like GAPPS!
Know bugs: ?
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-13 V0 version
Last Updated 2019-12-13
______________________________________________________
Other:
RevengeOS Q10 TWRP backup downloadable in comment section #20 comment. LINK
could you please port revenge os Q
port DU-REX rom please
you need remove flash opengapps optional in pixel experience is just no needed ...
Also impossible to install magisk 20.1 its needed to install latest canary magisk for information ...
it's turn me to fastboot
also twrp not full my screen plz fix it
viethoang18 said:
also twrp not full my screen plz fix it
Click to expand...
Click to collapse
viethoang18 said:
it's turn me to fastboot
Click to expand...
Click to collapse
After I make the final version of the ROM, I install it and when it works I only upload it.
Deleting/formating partitions is important.
TWRP works perfectly for me.
It is recommended that you use the latest ugglite Xiaomi firmware.
I can deal with these after further feedback.
thanks, i will try also can you build more like Evolution X ??
viethoang18 said:
thanks, i will try also can you build more like Evolution X ??
Click to expand...
Click to collapse
These ROMs are all equally bad for the time being, faulty applications, faulty Ui, faulty settings, faulty permissions, etc.
I think unnecessary to try many BETA ROMs for now.
And a lot of unnecessary work.
alright thanks you so much
Hafitz Setya said:
port DU-REX rom please
Click to expand...
Click to collapse
I tried DU-REX.
No messenger in it, I didn't get an SMS today ...
There is no FM radio.
It has GalleryGO but cannot associate it with a contact image... I needed to install another image viewer...
The lights are not working properly. (But this is common in other ROMs.)
Alpha version. But the boot animation is cool...
viethoang18 said:
alright thanks you so much
edit: still goes to fastboot after back Miui with miflash
Click to expand...
Click to collapse
Flash back previous recovery?
szanalmas said:
I tried DU-REX.
No messenger in it, I didn't get an SMS today ...
There is no FM radio.
It has GalleryGO but cannot associate it with a contact image... I needed to install another image viewer...
The lights are not working properly. (But this is common in other ROMs.)
Alpha version. But the boot animation is cool...
Click to expand...
Click to collapse
okey, thanks for you hard work dude
yess
Hafitz Setya said:
okey, thanks for you hard work dude
Click to expand...
Click to collapse
You ask? Packaged?
With Google Photos and Textra Messages have made it quite tolerable. : D
(And with my FMradiofix.)
DU-REX OS
Hafitz Setya said:
okey, thanks for you hard work dude
Click to expand...
Click to collapse
DU-REX OS (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-14-DUREX.
Install Textra SMS messages app and Google Photos app if you want messages or contact photos.
Your welcome.
Big +1: In the ROM built-in OpenCamera!
szanalmas said:
DU-REX OS (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-14-DUREX.
Install Textra SMS messages app and Google Photos app if you want messages or contact photos.
Your welcome.
Big +1: In the ROM built-in OpenCamera!
Click to expand...
Click to collapse
thanks dude, maybe I'll try tonight, I'm busy now
Please help me, it still go to fastboot
viethoang18 said:
Please help me, it still go to fastboot
Click to expand...
Click to collapse
Which one? Pixel or Durex?
Revenge os 3.0
ahmedhelmy71 said:
could you please port revenge os Q
Click to expand...
Click to collapse
REVENGE OS 3.0 (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-16-REVENGEOS.
Install Textra SMS messages app. (Was not SMS notification for me...)
Your welcome.
Screenshots: LINK
Related
hi
here is the flashable d855 20d rom
Italy
for 16/32gb
testet
how to :
1.install latest 4.4.2
2.root then install recovery (unlock)
3.(optional , wipe cache,dalvik,system,data,internal)
4.copy to memory then flash through recovery
5.then reboot
6.go to recovery and flash super su
all partitions are stock
rom:
Code:
http://uptobox.com/znwrofiifz9u
http://oceanhost.eu/aowq7vl2h57k/20d_g0dsend313v2.zip.htm
http://ul.to/631f6ec9
md5 :
067651767d3f59cc68673b9bc56a4ee0
supersu:
Code:
http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Credit:
@cybojenix
@bump! team
@thecubed
Skin1980_autobump script
if you have problem with using internal memory
in cmd type
Code:
adb shell
su
restorecon -v -R /data/media
or
adb shell
su
restorecon -FR /data/media/
It includes 20D bumped kernel or another kernel?
Thank you!
davidep85 said:
It includes 20D bumped kernel or another kernel?
Click to expand...
Click to collapse
Well, if it is Stock, then it should be the original 20D kernel. The OP did not say otherwise.
tobitege said:
Well, if it is Stock, then it should be the original 20D kernel. The OP did not say otherwise.
Click to expand...
Click to collapse
yes
all partitions are stock
mlm1102003 said:
yes
all partitions are stock
Click to expand...
Click to collapse
Can you upload the kernel please ..cos i flashed kdz rom and im not rooted ..my internet too slow to download this rom
rom is not working for me, I have problems with secure boot, like not bumped kernel. restored my backup.
davidep85 said:
rom is not working for me, I have problems with secure boot, like not bumped kernel. restored my backup.
Click to expand...
Click to collapse
tested 10 times
check md5
Code:
9e4082949fdc71da61d8254ccb8d5161
Hi, thank you for the great work! I am on AOSP liquid smooth rom. Is it possible to flash/update only the modem?
chaosnever said:
Hi, thank you for the great work! I am on AOSP liquid smooth rom. Is it possible to flash/update only the modem?
Click to expand...
Click to collapse
the best way to install it
is in first post
install 10n
then install root and recovery(unlock)
then flash the rom
mlm1102003 said:
the best way to install it
is in first post
install 10n
then install root and recovery(unlock)
then flash the rom
Click to expand...
Click to collapse
Entirely clear,
but one thing I am not clear (in general) about the internal SD memory: moving from KitKat to Lollipop ROM by using TWRP recovery should I format the internal SD (or delete all content manually)?
In generally, I didn't understand if there's an incompatibility of data applications residues coming from KitKat that might annoy Lollipop.
Thanks in advance
Romulus76 said:
Entirely clear,
but one thing I am not clear (in general) about the internal SD memory: moving from KitKat to Lollipop ROM by using TWRP recovery should I format the internal SD (or delete all content manually)?
In generally, I didn't understand if there's an incompatibility of data applications residues coming from KitKat that might annoy Lollipop.
Thanks in advance
Click to expand...
Click to collapse
/system format means your Android system is removed
/data format means your apps are erased
/cache format means.. pretty much what it says
That's all what you need for a new ROM. It's called a "clean flash"
A dirty flash would be the above, but without formatting /data. This retains the installed apps and their settings, but it might upset the new system and cause incompatibilities. It's not a recommended move.
But now, if, for some reason (like selling your phone), you'd like to "FULLY wipe" the phone
/data/media fully wipes your visible folders (not system ones, but the one where apps stores data files, photos, images, music etc)
So wiping Data is mandatory? No way to keep the apps, when coming from an older stock rom 10l?
Download link? I tried all links but only ads become in my screen...
thedoginthewok said:
So wiping Data is mandatory? No way to keep the apps, when coming from an older stock rom 10l?
Click to expand...
Click to collapse
Yes, always do when between different Android or ROM versions. Dirty flashing usually only works without issues when upgrading from a ROM version (example) 4.0 to 4.1 etc. But going from Kitkat to Lollipop it is required or the phone may not boot at all. There are obviously plenty of tools to help with backup/restore of apps+settings, but time spent on fresh install well spent compared to fixing issues or doing it all over again later.
Please anyone who downloaded this rom upload the kernel
Hi i have a few questions about this rom
1-is it necessary to install a 4.4.2 rom and then flash this rom or i can clean flash this rom over android HD 4.0 rom that i have right now ?
2-is this rom smooth or it has lags ?
3-how much screen time do u get with this rom?
Thanks in advance
Stupid quesiton, sorry, delete this post.
mlm1102003 said:
hi
rom:
Code:
updating
md5 :
Click to expand...
Click to collapse
Thanks for all, but where is the link
Edit : Link is back... You uploaded 313V2.... What's the difference between V1 and V2 ?????
TeamR said:
Thanks for all, but where is the link
Edit : Link is back... You uploaded 313V2.... What's the difference between V1 and V2 ?????
Click to expand...
Click to collapse
v1 sometime have problem with system ui (it does not load)
v2 just fix that problem
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App and data sharing?
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
Click to expand...
Click to collapse
How do I?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Just in case, if the app does not work, use the DualBootUtilities.zip from recovery to switch.
Downloads
App - https://www.androidfilehost.com/?fid=24438995911976818
Utilities - https://www.androidfilehost.com/?fid=24438995911976820
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Samsung Galaxy Star, ROM for the Samsung Galaxy Star
Contributors
corphish, chenxiaolong
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Beta
Created 2016-03-11
Last Updated 2016-03-11
Reserved
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
corphish said:
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
Click to expand...
Click to collapse
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
LahKeda said:
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
Click to expand...
Click to collapse
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
aLchiEro_06 said:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
Click to expand...
Click to collapse
App works perfectly fine on kitkat. But not in jb because it is not able to load libs, I will have a look on it.
corphish said:
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
Really ! Ok I will try it !
Click to expand...
Click to collapse
@corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
[/COLOR @corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
LahKeda said:
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
Click to expand...
Click to collapse
for primary partition its only working for KK+ right?
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
yah
duck'man said:
for primary partition its only working for KK+ right?
Click to expand...
Click to collapse
I don't think so you can flash any ROM in primary one !
LahKeda said:
I don't think so you can flash any ROM in primary one !
Click to expand...
Click to collapse
im using 4.1.2,, it cant instal dualbootpatcher.apk
duck'man said:
im using 4.1.2,, it cant instal dualbootpatcher.apk
Click to expand...
Click to collapse
this app still not usable for jb
How to delete or disable this dual boot
Any way
Hridul P.K said:
How to delete or disable this dual boot
Any way
Click to expand...
Click to collapse
by wiping system/data/cache/dalvik from recovery
Dark Knight Begins said:
by wiping system/data/cache/dalvik from recovery
Click to expand...
Click to collapse
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Hridul P.K said:
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Click to expand...
Click to collapse
to do a clean install u should wipe things first.
hit d thank button, don't say it
Help me plzzzz..........
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Mohsin Pathan said:
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Click to expand...
Click to collapse
It's not necessary just use this tool and it will patch the kernel image for you .
TWRP 3.1.0-0 for Samsung Galaxy C9 pro (SM-C900F) indian variant
This recovery is tested only on indian variant but should work on other variants too.
Code:
Flashing custom recovery and boot images will trip knox flag
and it can not be reverted. Your warranty will be void.
I am not responsible for any data loss or damage happens to device.
THIS PROCEDURE CAN CAUSE DATA LOSS . PLEASE MAKE A BACK UP BEFORE PROCEEDING.
This TWRP is built from source. It support back up of system,efs persist partitions.
As default samsung encrypts data and internal storage so by default you cannot mount data, system or internal storage.
So for removing encryption we have to format data and load decryption script given below.
Steps
1.Boot into Download mode
[Vol. Down + Home + Power]
2.Flash recovery.tar.md5 from odin [use latest 3.12 version and put tar.md5 in AP slot] and keep pressing Vol. Up + Home while flashing tar.md5 so that it will boot directly into recovery after reboot.
3. In recovery keep system read only.
4. go to backup menu and backup all partitions. Now reboot to normal OS
5. connect the phone to PC and copy the TWRP folder from storage to PC. (this is back up for restoring)
6. Back up your data, pictures, contacts, sms, whats up, telegram messages etc.
7. reboot to recovery [Vol up + Home + Power] and format data and in advanced wipe - format system,data,internal storage,cache,davlik from wipe menu.
8. connect phone to pc , now you can see internal storage.
Download & Copy
i) no-verity-no-encrypt_ashyx from https://forum.xda-developers.com/sa...wrp-3-0-2-1-samsung-galaxy-a9-pro-sm-t3426701
ii) SuperSu https://forum.xda-developers.com/showpost.php?p=55256620&postcount=1
to storage
Now copy your TWRP back up to storage.
9.Now from restore menu install the back up. > Go to install and select the above 2 zips for install.
10. after installing all this you have rooted phone with decrypted twrp . Now boot to os
Remember to make back up of this rooted configuration in TWRP so that you can always get back to this configuration when ever you want.
Download
https://forum.xda-developers.com/attachment.php?attachmentid=4104671&d=1491593451
Source
1. Manifest
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-6.0
2. Device tree
https://github.com/k2wl/c9lte-twrp
3. Kernel
built from opensource.samsung.com
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=c900f
Credits
*Samsung for kernel source.
*Omni rom and TWRP team
*@jcadduono @ashyx for dm-verity and forced encryption patcher.
*LineageOS team
*@pawitp (for being an inspiration )
*@Chainfire for supersu
things i tested
1.back up and restore
2.format data
3. wipe all mounts from advance wipe
4.language settings
5.root by supersu
6.dm-verity and encryption removal
7.MTP after data format
8.adb sideload
9.reboot to recovery, system,download,power off
10.file manager
so i think all basic things working properly if you follow the steps i listed above.
Atlast... Feeling blessed..
Thank you K2wl for working on this phone.
Will flash this TWRP & Let you know the status.
Is this TWRP version same as the one in the other thread? Because I already tested the TWRP in the other thread & posted few issues. Are they rectified?
Please let us know.
:good::laugh:
---------- Post added at 01:21 AM ---------- Previous post was at 12:40 AM ----------
K2wl,
Any chances of porting Custom Roms on C9 Pro like Cynogen Mod 6.0 or Lineage OS.
Simple roms for this beast phone would be great.
Any plans for this from your side?
Just curious.. :good:
Can we install xposed with this
Pariki said:
Atlast... Feeling blessed..
Thank you K2wl for working on this phone.
Will flash this TWRP & Let you know the status.
Is this TWRP version same as the one in the other thread? Because I already tested the TWRP in the other thread & posted few issues. Are they rectified?
Please let us know.
:good::laugh:
---------- Post added at 01:21 AM ---------- Previous post was at 12:40 AM ----------
K2wl,
Any chances of porting Custom Roms on C9 Pro like Cynogen Mod 6.0 or Lineage OS.
Simple roms for this beast phone would be great.
Any plans for this from your side?
Just curious.. :good:
Click to expand...
Click to collapse
yes ..i am planning for lineage
and if you follow my instructions this twrp works good!!!
@rajdeep312 this is recovery and not a rom so you can install xposed in your os if you want to...(i personally does not use exposed)
k2wl said:
yes ..i am planning for lineage
and if you follow my instructions this twrp works good!!!
@rajdeep312 this is recovery and not a rom so you can install xposed in your os if you want to...(i personally does not use exposed)
Click to expand...
Click to collapse
Thanx man so everything working in this recovery or somthing broken
rajdeep312 said:
Thanx man so everything working in this recovery or somthing broken
Click to expand...
Click to collapse
see post 2
k2wl said:
things i tested
1.back up and restore
2.format data
3. wipe all mounts from advance wipe
4.language settings
5.root by supersu
6.dm-verity and encryption removal
7.MTP after data format
8.adb sideload
9.reboot to recovery, system,download,power off
10.file manager
so i think all basic things working properly if you follow the steps i listed above.
Click to expand...
Click to collapse
========================
Great. Will work on the phone tomorrow & check on the TWRP & Xposed framework..
Will post updates on the new recovery & for any issues.
Eagerly waiting for K2wl to work on Lineage OS.
Thanks K2wl. :good::laugh:
I am not able to format /data & an SD card more than 8 GB is needed to backup the system.
I was able to format system.
Pariki said:
I am not able to format /data & an SD card more than 8 GB is needed to backup the system.
I was able to format system.
Click to expand...
Click to collapse
use format data from advanced wipe.
type yes for formating data
after that go back to install and install no-verity-no-encrypt script above from internal storage.
if that does not solve your problem then copy the recovery log here.
Lineage OS..
Hi Karthik ( K2wl ),
Any update or tentative date by when we can expect Lineage OS..
Please let us know about this...
:good: :good:
Pariki said:
Hi Karthik ( K2wl ),
Any update or tentative date by when we can expect Lineage OS..
Please let us know about this...
:good: :good:
Click to expand...
Click to collapse
no tentative date ...i am working on it...
Great.... :good:
Eagerly waiting to test it out...:fingers-crossed:
After format everything and restore unable to mount data and unable to see internal storage
rajdeep312 said:
After format everything and restore unable to mount data and unable to see internal storage
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71792618&postcount=10
see this post.
do this and reboot to recovery again
you should able to mount the internal storage
i am waiting for my c9p, may be china version.
can i change to india version so i can flash the above twrp?
tks.
amk said:
i am waiting for my c9p, may be china version.
can i change to india version so i can flash the above twrp?
tks.
Click to expand...
Click to collapse
i dont have china variant so i cant comment on that. but i will try to build china variant twrp.
Successfully installed Wanam Xposed..
I followed the instructions by K2wl & installed Wanam Xposed.
Format System, Data & Restoring backup worked fine.
Then installed
xposed-v87.1-sdk23-arm64-custom-build-by-wanam
XposedInstaller_3.1.1.apk
All good now.
Eagerly waiting for K2wl's Lineage OS now..
:good: :laugh:
Pariki said:
I followed the instructions by K2wl & installed Wanam Xposed.
Format System, Data & Restoring backup worked fine.
Then installed
xposed-v87.1-sdk23-arm64-custom-build-by-wanam
XposedInstaller_3.1.1.apk
All good now.
Eagerly waiting for K2wl's Lineage OS now.....but i am working on it..
:good: :laugh:
Click to expand...
Click to collapse
i know it is taking time as development on samsung is bit difficult..
Plz take your time. Will wait..
:good::good:
GooglecrDroid ROM 14-01-2020
FULL last openG(OOGLE)APPS included! (v.12-01-2020)
Last stable crDroid 6.2 based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe data, cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
I don't use this ROM, help each other who use it. Thnx.
DOWNLOAD SF
DOWNLOAD AF
Updates, previous and all ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage 17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 14-01-2020 V0 version
Last Updated 14-01-2020
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
I'd like to get feedback on whether VOLTE is working? Thanks.
wow thanks i'm gonna test now
---------- Post added at 07:26 AM ---------- Previous post was at 07:11 AM ----------
can you share device tree, kernel, vendor for android 10??
szanalmas said:
GoogleDroid ROM 2019-12-27
FULL open GOOGLE APPS included!
Last stable crDroid based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
DOWNLOAD ROM
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-27 V0 version
Last Updated 2019-12-27
Click to expand...
Click to collapse
Thanks for you great rom again, @szanalmas :good:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
I cant install magisk
please make a original TWRP 3.3.1 like 3.2.1
GonzaloxCOM said:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
Click to expand...
Click to collapse
Unfortunately, I can't test VOLTE, Hungarian Telekom is filtering phone model the use of VOLTE...
DT2W works for me, no need to fix it. (I built it into /vendor.)
Your welcome!
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Use Canary: LINK
(But i haven't tested Magisk yet.)
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
cpglbitm said:
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
Click to expand...
Click to collapse
I can't install this version either. It always ends with error 1.
Endys111 said:
I can't install this version either. It always ends with error 1.
Click to expand...
Click to collapse
Use orangefox recovery.
cpglbitm said:
Use orangefox recovery.
Click to expand...
Click to collapse
Thanks, already installed.
Can I flash this rom in Redmi Y1
arvind787 said:
Can I flash this rom in Redmi Y1
Click to expand...
Click to collapse
I do not think so.
Y1 Q10 vendor image and Y1 kernel would be nice.
But I don't know for sure.
If the kernel starts, it is possible. If the LCD and touchscreen match, then the cameras are in question.
But I know that the kernel does not have msm8940 support and Y1 uses 8940 as far as I know.
So you probably won't boot the kernel.
@Topser99 has provided us with some newly modified recoveries.
They all have TWRP 3.4 and also now 3.5
⇨NewUpdate
-update kernel
By : @physwizz
Follow : @ULtimaTe_Pie2
Follow Galaxy_A20_official
System and System_root
Twrp-sm-a20 - Google Drive
drive.google.com
Choose .img you want and flash it from your current recovery onto the recovery slot.
Then reboot into recovery.
Or choose the .tar to flash from odin
You must be aware though that your previous backups will not restore .
You should read this next section carefully.
TWRP recovery Incompatability Issue
There are 2 types of recovery:
Type 1 backs up /system
Type2 backs up /system_root but labels it "system"
Both types work well but you can't backup on one type and restore on the other
To overcome this problem, I suggest that filenames of TWRPs should either contain SYSTEM or SYSTEM_ROOT
Also.
TWRP 3.4 is incompatible with TWRP 3.3 and @Topser had modded to produce TWRP 3.4 for us to use.
So now there are 4 types:
1. TWRP 3.3 SYSTEM
2. TWRP 3.3 SYSTEM_ROOT
3. TWRP 3.4 SYSTEM
4. TWRP 3.4 SYSTEM_ROOT
A backup made with one type will not restore with any of the other 3 types.
Post 2
I can confirm TWRP 3.4 SYSTEM version works correctly (including MTP at recovery level). Funnily enough, I just finished porting the A30 version for myself and came up with an almost identical result. I remove the fstab lines for product image, vendor image and system image just to make it cleaner
Thanks for doing this for all @Topser
Whats the difference between system_root and system ?
So this can be installed over 3.3 aswell ?
Jeremy_J7 said:
Whats the difference between system_root and system ?
So this can be installed over 3.3 aswell ?
Click to expand...
Click to collapse
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
physwizz said:
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
Click to expand...
Click to collapse
I see now, its labels it differently , thanks alot, will flash it later today . Thanks Bro ?
physwizz said:
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
Click to expand...
Click to collapse
I just flashed the new recovery, I tested MTP and its working ? I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Jeremy_J7 said:
I just flashed the new recovery, I tested MTP and its working ? I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Click to expand...
Click to collapse
It's the default
Topser99 said:
It's the default
Click to expand...
Click to collapse
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Jeremy_J7 said:
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Click to expand...
Click to collapse
Should think of android 4.4 and supersu
Jeremy_J7 said:
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Click to expand...
Click to collapse
I'd leave it as it is.
Try that and then untick it and try that to see what happens
physwizz said:
I'd leave it as it is.
Try that and then untick it and try that to see what happens
Click to expand...
Click to collapse
Ain't got anything to flash at the moment thou ? Maybe will try when a new version of Edxposed comes up.
Jeremy_J7 said:
Ain't got anything to flash at the moment thou ? Maybe will try when a new version of Edxposed comes up.
Click to expand...
Click to collapse
In my understanding
Twrp_3.3 mount system before installing a zip for supersu =>> system/sbin,bin,xbin
Twrp_3.4 unmount system before installing a zip for magisk =>>/data/adb/magisk
@Topser has updated the files on post 1
You can now choose a TWRP to backup data and storage
Jeremy_J7 said:
I just flashed the new recovery, I tested MTP and its working I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Click to expand...
Click to collapse
It's disabled by default since most things using recovery work systemlessly. Most packages that use the system mount point will automatically mount system for reading and writing anyway. So there's no need to mess with the toggle.
can i flash this tar file on my a205f
A205FXXU8BTG3
shawal_islam said:
can i flash this tar file on my a205f
A205FXXU8BTG3
Click to expand...
Click to collapse
yes
K I back on the scene again and I have a Galaxy A20 I want to root with TWRP!
Heres what I need to know how to the program that installs TWRP and which 3.4 files do I need?
And how will do the install of TWRP I been off 2yrs I just coming back to the website today?
Sorry if this is hard to follow I will post now for ques and feedback. TIA!
techmanc said:
K I back on the scene again and I have a Galaxy A20 I want to root with TWRP!
Heres what I need to know how to the program that installs TWRP and which 3.4 files do I need?
And how will do the install of TWRP I been off 2yrs I just coming back to the website today?
Sorry if this is hard to follow I will post now for ques and feedback. TIA!
Click to expand...
Click to collapse
what do you want to know about Twrp3.4
Topser99 said:
what do you want to know about Twrp3.4
Click to expand...
Click to collapse
Which Odin and TWRP do I need to install my Galaxy A20 as per my sig!