Mod Edit: closed per OP request
I'M NOT RESPONSIBLE FOR ANY DAMAGE AND/OR DATA LOSS AS A RESULT OF FLASHING THIS ROM !!!
PLEASE PERFORM FULL BACKUP IN THE MICRO SD CARD OR IN AN EXTERNAL STORAGE BEFORE YOU TRY !!!
Do you need reliability and predictability? Then better stay with THIS ROM
I have decided to create a separate thread because:
- I would like to distinguish PIE BETA bug reports from my normal (OREO stable) thread, mentioned above
- It is normal that there will be definitely much more "bad reports" here, because most of them will be "beta related"
This thread will be closed when Samsung will release stable Android Pie (One UI)
Everything you will need to know about DevBase ROM in general - you will find in my stable thread (mentioned above)
Differences comparing to stable Oreo DevBase ROM:
- No AppLock (yet)
- No Xposed (we need to wait for rovo89)
S9 (SM-G960F/DS/FD):
>> G960FXXU2ZRLF_DevBase_v6.0.RC8.zip << (updated Dec-19, more info in post #49)
Click to expand...
Click to collapse
S9+ (SM-G965F/DS/FD):
>> G965FXXU2ZRLF_DevBase_v6.0.RC8.zip << (updated Dec-19, more info in post #49)
Click to expand...
Click to collapse
Dirty flash over my Oreo DevBase ROM SHOULD WORK WITHOUT ISSUES but before you try - I would highly recommend you to set default (stock) theme and default (stock) icons !!! However - I would recommend you clean install (Wipe -> Swipe to Factory Reset is enough)
Known issues:
- [CLEAN INSTALL] Magisk Manager may not appear after clean install despite Magisk has been installed without errors during install - if you notice that there is no Magisk Manager - DO NOT flash Magisk, it is enough to (re)install Magisk Manager as normall app - use ATTACHMENT (it is original apk from Magisk v17.3)
- OEM unlock toggle seems to be disabled in the Developer Options but it is not true (otherwise you would not be able to use TWRP and this ROM). It is side effect of protection I put in the kernel against "KG State: Prenormal" in the DM mode. It is not real issue, just ignore it.
Thanks to:
- all users mentioned in my main thread
- @ASHLEY117 for G960F dumps
- @geiti94 who first provided me update.zip and dump for G965F
- @SoLdieR9312 for ZRKA update.zip for G960F containing BL/CP
I know nothing
Got no stones lol
Great work to you as well! ??
Just flashed the rom , clean install. Does not let me finish the setup screen because it is stating that a file has been removed ( regarding security or health ) in an unauthorized way . Not able to access anything after the setup screen only an option of emergency call is available.
bobandar said:
Just flashed the rom , clean install. Does not let me finish the setup screen because it is stating that a file has been removed ( regarding security or health ) in an unauthorized way . Not able to access anything after the setup screen only an option of emergency call is available.
Click to expand...
Click to collapse
No problem here (according to screenshots), but I have an idea... Please place attached options.prop file (decompress zip first) in the root directory of /sdcard or /external_sd and then try again
EDIT: Attachment removed! Please try updated ROM (r2) available in post #1. Please remove previously shared options.prop from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
_alexndr said:
No problem here (according to screenshots), but I have an idea... Please place attached options.prop file (decompress zip first) in the root directory of /sdcard or /external_sd and then try again
Click to expand...
Click to collapse
Will surely do and let you know.
This is what I had got earlier. Will try flashing now with the solution you gave.
nah mate, still getting the same problem
bobandar said:
nah mate, still getting the same problem
Click to expand...
Click to collapse
Still wondering how it is possible that for me it works...
Is there a person who managed it to work after clean install?
Thread has been updated. If you used options.prop file from post #4 - please remove it from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
Dirty flash. Working fine.
mevorach said:
Dirty flash. Working fine.
Click to expand...
Click to collapse
Which rom?
saxena1 said:
Which rom?
Click to expand...
Click to collapse
Coming from 5.9 j8 g965f
Samsung thems not working
mevorach said:
Coming from 5.9 j8 g965f
Samsung thems not working
Click to expand...
Click to collapse
They won't yet as its a Beta ROM. Stuff like that will be sorted out of Beta.
Hi,
I use ledcover, is it working with the beta ?
Thank you for your work.
Maglisr
Sent from my SM-G965F using XDA Labs
Gallery dose not present the photos from camera on sd card.
mevorach said:
Gallery dose not present the photos from camera on sd card.
Click to expand...
Click to collapse
Again, known bug in Samsung software. I'm running stock beta and have this problem
Due to the fact that I am still reading here and there with a high risk of FRP/RMM lock in Pie, the precise circumstances of which are still unknown - I have decided to upload v5.9_r3 which still contains Pie modem but does NOT contain Pie BL anymore.
Precise circumstances of FRP/RMM lock in Pie are unknown, but I believe that probability will be significantly reduced with Oreo BL (at least for those people who never flashed Pie BL yet) especially, that Pie beta seems to work well with Oreo bootloader & Pie modem.
>> G965FXXU2ZRKA_DevBase_v5.9_r3.zip << (updated Nov-22)
Click to expand...
Click to collapse
Advice for those who have Pie bootloader already - DON'T mess with it - let it be still Pie !!! Also - I would NOT recommend you to jump beetween Pie -> Oreo if it is not absolutely necessary! After several attempts of restoring Oreo ROM & BL, which passed successfully, then updating again to Pie ROM & BL, then restoring again... - unexpectedly, the problem has become to me (my device is RMM locked - I lost OEM unlock toggle for 7 days, I hope...)
At the moment we can confirm only 2 scenarios which should end without problems:
- Dirty flash Pie DevBase over Oreo DevBase (thanks to @mevorach for the try & report), but I would highly recommend you to set default (stock) theme and default (stock) icons before you try
- Clean flash (tested personally) but only if you never jumped beetween Pie -> Oreo in the past (no matter if it was clean downgrade or restoring Oreo backup)
IMO you should also assume following scenarios as risky:
- Jumping from Pie DevBase ROM -> SoLdieR9312's Pie ROM
- Jumping from SoLdieR9312's Pie ROM -> Pie DevBase ROM
EDIT: Vaultkeeper service has been removed from the kernel (starting from v5.9_r4). Should be more safe now, despite BL/CP are flashed again
So you don't suggest to switch over from SoLdieR9312's Pie ROM v1.1 to yours(dirty flash) & sdcard problem fixed v r3? I am on at
SoLdieR9312's Pie ROM v1.1.
saxena1 said:
So you don't suggest to switch over from SoLdieR9312's Pie ROM v1.1 to yours(dirty flash) & sdcard problem fixed v r3? I am on at
SoLdieR9312's Pie ROM v1.1.
Click to expand...
Click to collapse
Nothing has been changed in sdcard support comparing to stock beta - such kind of issues should be solved by Samsung.
IMHO if you are still on Oreo BL (never flashed Pie bootloader in the meantime) and never jumped Pie -> Oreo then should be OK after flashing r3 (r3 also does not contain Pie BL)
Please let us know if you decide to try
Flashing your 5.9 r2 , from oreo(j8) did not include the pie BL ?
Related
This will be for the SM-G935J/SCV33/hero2qltekdi Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767132875 (SCV33KDU1APK2)
Unofficial TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747133
Rooted Rom: https://www.androidfilehost.com/?fid=529152257862698453
HKernel Beta 2 for hero2qltekdi: https://www.androidfilehost.com/?fid=745425885120706414
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/and...commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Nice!
kernel error Status 7 . Please fix !
depzai125 said:
kernel error Status 7 . Please fix !
Click to expand...
Click to collapse
Depzai,
Please be more specific, type out entire or post photo of TWRP log people can see the error in full and help you the best we can.
For the time being try this. Do an ext4 format in TWRP, then wipe /data /internal storage /dalvikART /cache - be sure you do this or else you will not be able to boot due to Samsung's encryption. Flash rooted rom provided by Travis via TWRP. After flashing rooted rom, do not reboot, proceed to flash HKernel provided by Travis. Wipe /dalvik and reboot. It will take a couple of minutes for the whole thing to reboot - let your phone sit and do its thing. Check your kernel and build# under settings and post back with results.
I know for a fact what Travis provided works, since hes fixed TWRP and the HKernel for the SCV33 variant recently.
HKernel Beta 2: https://www.androidfilehost.com/?fid=745425885120706414
Changes:
CVE 2016-8403,5346,9806,cve-2017-0451
iosched bfq,sio,fiops
removed tima rkp
more misc changes
Great Perfect Wonderful before after root my phone running lag unstable.After i flashed rom from travis82 have a root and TWRP. I removed all apps from AU.My phone have running smooth burt have still errors and limited from carrier AU and Japan phone.Like exsample : " the front camera after capture picture have a black , When make a call always popup "Call without country code ; Call to (JPN) if you want make a call you have must choose Call without country code ".....
change apn settings seems to be your issue or re-flash your csc with odin. I can't guarantee the jap versions will be 100% perfect, if you want this, someone needs to donate me a s7 edge docomo.
alibabahp said:
Great Perfect Wonderful before after root my phone running lag unstable.After i flashed rom from travis82 have a root and TWRP. I removed all apps from AU.My phone have running smooth burt have still errors and limited from carrier AU and Japan phone.Like exsample : " the front camera after capture picture have a black , When make a call always popup "Call without country code ; Call to (JPN) if you want make a call you have must choose Call without country code ".....
Click to expand...
Click to collapse
Alibabahp,
Try and do as Travis has stated, if no luck.
Redo your install. Not sure how you got these errors. My front cam works as it should, and all calls out of JPN and in JPN work with country codes.
Jayres said:
Alibabahp,
Try and do as Travis has stated, if no luck.
Redo your install. Not sure how you got these errors. My front cam works as it should, and all calls out of JPN and in JPN work with country codes.
Click to expand...
Click to collapse
i have see 2 S7 edge AU phone from JP after root or flash TWRP knox warranty void : 0x1(0x303).The front camera will work with black picture.Try this if you want see black picture.About " "Call without country code ; Call to (JPN) ". I have turnoff by phone settings - roaming settings - off Automatic conversion.Done
alibabahp said:
i have see 2 S7 edge AU phone from JP after root or flash TWRP knox warranty void : 0x1(0x303).The front camera will work with black picture.Try this if you want see black picture.About " "Call without country code ; Call to (JPN) ". I have turnoff by phone settings - roaming settings - off Automatic conversion.Done
Click to expand...
Click to collapse
Alibabahp,
Sorry - please clarify.
As you've mentioned from other post.
Using SCV33 Rom/HKernel provided in this post.
1. Lose WiFi/Cellular Data capabilities, such as calling?
2. Front camera is not working properly? Using front camera you only see a black screen?
Regards
travis82 said:
HKernel Beta 2: https://www.androidfilehost.com/?fid=745425885120706414
Changes:
CVE 2016-8403,5346,9806,cve-2017-0451
iosched bfq,sio,fiops
removed tima rkp
more misc changes
Click to expand...
Click to collapse
Travis,
Working great on my end.
Some photos for all too see benchmark. Received about a 3k point boost with Beta 2.
Jayres said:
Travis,
Working great on my end.
Some photos for all too see benchmark. Received about a 3k point boost with Beta 2.
Click to expand...
Click to collapse
:angel::good:
I'll get twrp updated for the other 2 variants this weekend also.
First I installed TWRP via ODIN
Then I installed the SU from the memory card
I rebooted the phone, no internet and no cellular network
I read somewhere that needed another kernel I installed what is in the link of this post
In log appeared error messages: could not mount ... (I forgot the characters here sorry ) but in the end appeared sucess
I just installed and restarted, message on display: KERNEL IS NOT SEANDROID ENFORCING
WARRANTY BIT: KERNEL
Stopped in the galaxy logo
I read more posts that I needed to do wipe
Dalvik / ART Cashe and Cache
But messaging appeared: Failed (same as above process)
So I decided to use the FORMAT DAT option
The phone started again and all functions ok.
Now comes the bad part
Wanted to see what the error that appeared in the log
But this time there is no error
But in rebbot the message appears: NO OS INSTALLED
And now how do I solve this? please :crying:
Sorry bad english
twrp via odin, boot twrp and format data, install kernel, done
travis82 said:
twrp via odin, boot twrp and format data, install kernel, done
Click to expand...
Click to collapse
Performed but does not start
Always returns to TWRP
what about previous kernel? Odd some are saying no problem, some are saying errors, how do I know what is what when I do not have the device in my physical possession?
If you all seriously want support like on SM-G9350 I really do need the device to run debugs and get kernel logs so I can do fast builds to troubleshoot. It's very difficult building blindly ya know? So as of now I will not update the Doco variants any longer until I am able to have a hands on experience with it. Sorry about that but I think its best for now.
Jayres said:
Alibabahp,
Sorry - please clarify.
As you've mentioned from other post.
Using SCV33 Rom/HKernel provided in this post.
1. Lose WiFi/Cellular Data capabilities, such as calling?
2. Front camera is not working properly? Using front camera you only see a black screen?
Regards
Click to expand...
Click to collapse
The main reasons of my phone before unlocked with modify firmware Docomo..If i have try reflash with firmware stock SCV33 => My phone lose all WIFI/Cellular .When i try flash firmware docomo my phone have working again.WIFI & Cellular working.
travis82 said:
what about previous kernel? Odd some are saying no problem, some are saying errors, how do I know what is what when I do not have the device in my physical possession?
If you all seriously want support like on SM-G9350 I really do need the device to run debugs and get kernel logs so I can do fast builds to troubleshoot. It's very difficult building blindly ya know? So as of now I will not update the Doco variants any longer until I am able to have a hands on experience with it. Sorry about that but I think its best for now.
Click to expand...
Click to collapse
Dear @travis82 can you port your room SM-G9350 for S7 edge Japan?Or can you upload only system.zip of you i will try update my phone.Thanks so much.
no more docomo updates until I get a docomo somehow someway, its too difficult to know rom error or user error since i do not have the device.
I think I deleted the OS somehow
So I installed the rooted room and the kernel beta 2
Everything works but with a lot of lag
Should I Try Another Version Of The Kernel?
Please do not abandon this version
Only you are giving support
Updating
After installation of Rooted Rom the device was showing a lot of lag
I uninstalled the apps that did not interest me and I rebooted the device by entering TWRP
I reinstalled Kernel Beta 2, after the installation I clicked the option WIPE CACHE / DALVIK, after complete reboot
On restart it appeared the message ANDROID IS OPTIMIZING APPS
After this the system became perfect without lag
Everything running internet, cel calls ... and root
its great , I am very happy
[ROM/Kernel] Stock 7.1.1 B02 based for A2017G. The "We can do it better than zte" ed.
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootstack. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
davidroid1 said:
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
For me TWRP 3.1 did its job.
tron1 said:
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootloader. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
Click to expand...
Click to collapse
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
sToRm1nG said:
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
Click to expand...
Click to collapse
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
tron1 said:
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
Click to expand...
Click to collapse
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
sToRm1nG said:
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
Click to expand...
Click to collapse
It's just a "click" in the SuperRs kitchen boot image config menu.
Anyone who has U model tried?
WesTD said:
Anyone who has U model tried?
Click to expand...
Click to collapse
I'm not sure if the U model contains the Tencent Network Location app (AFAIK it is not).
Pin Input necessary after installation ....
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Snoopy2006 said:
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Click to expand...
Click to collapse
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
From MM B08 to Nougat 7.1.1 B02
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with
Click to expand...
Click to collapse
At the Moment I`m back to MM B08 on the Axon 7 2017 G !
What should I flash ?
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
Click to expand...
Click to collapse
In my Systemfolder I find gatekeeper.password.key and gatekeeper.pattern.key. Should I remove these 2 Files ?
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
can we select the apps which we want and which we do not want while installing ?
sendem said:
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
Click to expand...
Click to collapse
Tried it with Sigic and GPS test tool, no problem here
I flashed the kernel now the gps its ok(so no problems for me) .dont use the latest twrp 3.1 it has some bugs.
best regards.
I understand you kept this close to stock, but I have 3 questions.
Does it support Live Wallpaper? (stock B02 doesn't)
Can you turn off the lock screen 'None'?
Does it run Daydream smoothly?
You need to put it in the viewer to really tell. I tried on other ROMS, but it was super choppy and jittery to the point of nausea.
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
HuKu52 said:
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
Click to expand...
Click to collapse
No problem here. Check bootstack/modem
Pixel platformOEM software redesigned to be closer towards Android's default interface with inspiration from Pixel
Huawei P Smart 2018 - FIG-LX1 Models supported C432 | C782 | C106
Pixel platform for the Huawei P Smart is a version of Huawei's EMUI based on Android 8.0 that has been modified to look and feel more like a pure Android/Pixel experience by:
replacing the default EMUI skin with a custom skin created by Livitech specifically for EMUI 8.0 that resembles Android 9.0
removing 98% of Huawei applications and replacing them with Google alternatives
Adding extra Google apps such as Wallpapers and Live wallpapers
Usually switching to a custom ROM to get a more pure Android or pixel like experience means sacrificing optimisations made by the manufacturer for your device ranging from display drivers to camera sensors, by building on top of the default OEM software all of this is kept:
The default Camera app so you don't miss a shot
Device specific features like double touch to turn screen on/off
Battery life settings tuned for your device
Best performance to provide efficient and fast work
Latest version
Pixel platform: 2.4.1
Released: April 14th 2019
If you are not running Pixel Platform then follow instructions on this page
Instructions
If you are running Pixel Platform 2.3.x then follow update instructions on this page
Instructions
If you are running Pixel platform 2.4 already then there is no need to update
Learn more
cool !! so how do we install this??
looks interesting ..gonna give it a shot ...just a question ..womt replacing stock gallery cause problems with intergrated camera functions
Hello! Could you please provide some install instructions? Can it be installed on a device that hasn't been unlocked yet. Thanks
the download is 2GB so I'm pretty certain it is a stock system.img file that you can flash with .img compatible recovery or with fastboot ...
you would need to be on stock ...unrooted ...i imagine if you are rooted you should flash stock boot.img and then flash system ..then reflash magisk if you want root ..
I'm just guessing here since I haven't downloaded it yet cos 2GB is big and I'm already on stock rooted that I modded myself using magisk & twrp ...
i think he too a stock system.img that he made the modifications he lists ..
problem is he should indicate build number and security patch so people can ensure they are on the same security patch EDIT HE LISTS JANUARY , radio ( baseband) , region , build number to avoid problems with imei or cellular reception or boot looping due to a newer version of stock rom installed ...
the OP doesn't say much though and his website looks a site where he sells IT services ...
KevMetal said:
the download is 2GB so I'm pretty certain it is a stock system.img file that you can flash with .img compatible recovery or with fastboot ...
you would need to be on stock ...unrooted ...i imagine if you are rooted you should flash stock boot.img and then flash system ..then reflash magisk if you want root ..
I'm just guessing here since I haven't downloaded it yet cos 2GB is big and I'm already on stock rooted that I modded myself using magisk & twrp ...
i think he too a stock system.img that he made the modifications he lists ..
problem is he should indicate build number and security patch so people can ensure they are on the same security patch EDIT HE LISTS JANUARY , radio ( baseband) , region , build number to avoid problems with imei or cellular reception or boot looping due to a newer version of stock rom installed ...
the OP doesn't say much though and his website looks a site where he sells IT services ...
Click to expand...
Click to collapse
Download zip file and flash with TWRP
KevMetal said:
the download is 2GB so I'm pretty certain it is a stock system.img file that you can flash with .img compatible recovery or with fastboot ...
you would need to be on stock ...unrooted ...i imagine if you are rooted you should flash stock boot.img and then flash system ..then reflash magisk if you want root ..
I'm just guessing here since I haven't downloaded it yet cos 2GB is big and I'm already on stock rooted that I modded myself using magisk & twrp ...
i think he too a stock system.img that he made the modifications he lists ..
problem is he should indicate build number and security patch so people can ensure they are on the same security patch EDIT HE LISTS JANUARY , radio ( baseband) , region , build number to avoid problems with imei or cellular reception or boot looping due to a newer version of stock rom installed ...
the OP doesn't say much though and his website looks a site where he sells IT services ...
Click to expand...
Click to collapse
Download EMUI Pixelized from bottom of website
www.livitech-development.co.uk/pixelized-platform-huawei
Flash file with TWRP
Bootloader must be unlocked
Models supported are C782, C432, C16B
No need to format or erase data as the TWRP zip file does it for you without deleting content on internal storage
Security patch ( Google ) is January 2019
Kernel security patches do not change as TWRP does not like the kernel IMG being flashed through a zip file otherwise I would have included an updated kernel as well.
The only two partitions on the phone changed are
/System
/Version
These two partitions do not cause any problems with basebands, region, IMEI numbers since the files and coding are in their own separate partitions
KevMetal said:
looks interesting ..gonna give it a shot ...just a question ..womt replacing stock gallery cause problems with intergrated camera functions
Click to expand...
Click to collapse
Download EMUI Pixelized from bottom of website
www.livitech-development.co.uk/pixelized-platform-huawei
Flash file with TWRP
Bootloader must be unlocked
Models supported are C782, C432, C16B
lfom said:
Hello! Could you please provide some install instructions? Can it be installed on a device that hasn't been unlocked yet. Thanks
Click to expand...
Click to collapse
Download EMUI Pixelized from bottom of website
www.livitech-development.co.uk/pixelized-platform-huawei
Flash file with TWRP
Bootloader must be unlocked
Models supported are C782, C432, C16B
No need to format or erase data as the TWRP zip file does it for you without deleting content on internal storage
Security patch ( Google ) is January 2019
Kernel security patches do not change as TWRP does not like the kernel IMG being flashed through a zip file otherwise I would have included an updated kernel as well.
The only two partitions on the phone changed are
/System
/Version
These two partitions do not cause any problems with basebands, region, IMEI numbers since the files and coding are in their own separate partitions
going to try this and give feedback soon
installed succesfully and have not experinced any issues so far, but the system is prerooted.
so don't use if you don't want root.
enjac said:
going to try this and give feedback soon
installed succesfully and have not experinced any issues so far, but the system is prerooted.
so don't use if you don't want root.
Click to expand...
Click to collapse
Could you take a screenshot of the:
Homescreen
App drawer
Lockscreen
Thanks, just want to confirm it is working as it should
The rooted problem is due to Huawei not giving the option to decrypt the phone in the settings
If I try with encrypted folders, everything doesn't install as it should
Livi-Tech said:
Could you take a screenshot of the:
Homescreen
App drawer
Lockscreen
Thanks, just want to confirm it is working as it should
The rooted problem is due to Huawei not giving the option to decrypt the phone in the settings
If I try with encrypted folders, everything doesn't install as it should
Click to expand...
Click to collapse
sorry am back to stock
enjac said:
sorry am back to stock
Click to expand...
Click to collapse
Okay
Was magazine unlock working ( changing lockscreen wallpaper )
And was pixel launcher ( homescreen ) working?
Livi-Tech said:
Okay
Was magazine unlock working ( changing lockscreen wallpaper )
And was pixel launcher ( homescreen ) working?
Click to expand...
Click to collapse
everything was fine. only changed to stock because of root,
you did a great job :good:
enjac said:
everything was fine. only changed to stock because of root,
you did a great job :good:
Click to expand...
Click to collapse
i'm looking into a way around the root issue
This software was ready 6 months ago under the name EMUI-Pixelized
The reason it was pulled/discontinued was because I created the software on the C782 model P smart so when flashed on another model
the Wallpaper would reset
Google apps would get removed
Pixel launcher would switch back to EMUI's launcher
Working with this user who had the C432 model for the first half of those 6 months we were able to find the files responsible for these compatibility issues, The second half of those 6 months, this user had been given 3 updates to update security patches ( all created from scratch ) and the compatibility issue is no longer anywhere to be found and is confirmed working for C782, C432 and my cousin has the C16B model which also works
If another model was to be added, in the past the software had to be recreated from scratch but certain modifications were made to allow new model support to only require a small change to one file ( other models apart from C782, C432 and C16B should still work anyway without needing to have official support added )
Livi-Tech said:
i'm looking into a way around the root issue
This software was ready 6 months ago under the name EMUI-Pixelized
The reason it was pulled/discontinued was because I created the software on the C782 model P smart so when flashed on another model
the Wallpaper would reset
Google apps would get removed
Pixel launcher would switch back to EMUI's launcher
Working with this user who had the C432 model for the first half of those 6 months we were able to find the files responsible for these compatibility issues, The second half of those 6 months, this user had been given 3 updates to update security patches ( all created from scratch ) and the compatibility issue is no longer anywhere to be found and is confirmed working for C782, C432 and my cousin has the C16B model which also works
If another model was to be added, in the past the software had to be recreated from scratch but certain modifications were made to allow new model support to only require a small change to one file ( other models apart from C782, C432 and C16B should still work anyway without needing to have official support added )
Click to expand...
Click to collapse
would be glad to have this Rom witout root. hope you find a way to fix it.looking forward to next update. :good:
enjac said:
would be glad to have this Rom witout root. hope you find a way to fix it.looking forward to next update. :good:
Click to expand...
Click to collapse
i've had a look into it, The device isn't actually rooted like I suspected ( I got a 2nd opinion ) the message pops up when the boot file has been modified ( even if decompiled and recompiled with no actual modifications )
The boot file is modified by the decrypt.zip file to prevent files on phone storage getting encrypted
When I was updating to a newer version of this software before or switching from full stock EMUI, all my folders and file would encrypt and become random letters and numbers making accessing them impossible
Currently looking into a way around this
enjac said:
would be glad to have this Rom witout root. hope you find a way to fix it.looking forward to next update. :good:
Click to expand...
Click to collapse
Found the root issue and fixed it
Phone isn't actually rooted like I suspected
Huawei looks for a certain line of code in the /version partition
If this line is taken out then Huawei's services detect the phone as modified
Issue is no longer appearing and currently rebuilding the software with the fix intact
Livi-Tech said:
Found the root issue and fixed it
Phone isn't actually rooted like I suspected
Huawei looks for a certain line of code in the /version partition
If this line is taken out then Huawei's services detect the phone as modified
Issue is no longer appearing and currently rebuilding the software with the fix intact
Click to expand...
Click to collapse
Yeah good to know . Waiting for the update
enjac said:
Yeah good to know . Waiting for the update
Click to expand...
Click to collapse
Here you go
https://drive.google.com/file/d/1VRm0aUgdwtjk_TQxLhxbMoYCvhrWIs7S/view?usp=sharing
Backup any important files on internal storage
Flash TWRP
Install rom
Install decrypt.zip file ( placed in internal storage after installing rom )
Wipe internal storage
Reboot
NcX 2.5 A71 ROMPretty straight forward, I took OneUI 2.5 firmware, debloated it and added a few features which can be found here: Link to MODs
My plan is to make this the best version of OneUI 2.5 with more features and fixed things (my mission is to fix Secure Folder in the near future) Fixed
Anyway, let's get started.
Code:
Your warranty is now void.
* 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 flashing 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. HARD!
Features!
TWRP Included
Full OneUI 2.5 features
Debloated
Added camera features
Dolby Atmos without earphones
Optimized
Edge Lighting fully enabled
Secure Folder fixed
Smart View fixed
Samsung Health fixed
Samsung OCR service
Bugs!
Secure Folder broken (will try to fix later) Fixed on 2.5.1
Samsung Pass broken (because of knox 0x1, duh) Removed from ROM, it will never work.
Bug with AOD brightness when you use fingerprint unlock method. This bug happens when you have AOD to always show. If AOD is showing, then you turn the screen on to only show lockscreen clock and then turn the screen off for AOD to show, the brightness of AOD will reduce to the most minimal and it will be hard to see, regardless of what brightness you set up. There are 2 ways to getting rid of this bug:
Disable unlocking phone with fingerprint
Unlocking your phone and then locking it again. This will only fix it until you trigger the bug again
Fixed, clock animation removed.
You tell me
Changelog!
25/Oct/2020 (NcX 2.5.2):
Added 60 fps recording on selfie cam
Added wide selfies. (a biiiiit buggy, but serviceable)
Added 24 fps recording modes on pro video mode
Fixed Samsung Health
Added Samsung OCR Service for better text extraction
12/Oct/2020 (NcX 2.5.1):
Secure Folder fixed
Smart View fixed
AOD bug fixed
Removed Samsung Pass
Removed Samsung Daily
Removed "Tips" app
Removed Bixby
Added camera features
08/Oct/2020: Release
Links!
(V2.5.2)Google Drive
(V2.5.1)Google Drive
(V2.5)Google Drive
PrequisitesMANDATORY ALWAYS: SD Card. It IS possible to have it on internal storage but ONLY if you are not encrypted. If you are encrypted, then you will need to FORMAT DATA and that will delete everything in your internal storage and you won't be able to add it back to internal storage with TWRP because MTP is broken.For installing 2.5.1/2.5.2:
Installing and following NcX 2.5 installation steps, as well as its prequesites
TWRP Installed (included in NcX 2.5)
Download multidisabler.zip (link: From Telegram Group (also attached on this thread) and add to SD Card or internal storage
Download Magisk zip installer to your SD Card or internal storage
For installing 2.5:
Update to bootloader U3 (either install OneUI 2.1 or OneUI 2.5 fully with Odin), otherwise you will have problems with camera
Fully unlock bootloader. I don't mean just turning OEM unlock on in developer settings , I mean FULLY unlock. If you didn't know, Samsung changed up how you unlock the bootloader on newer devices like this one. @topjohnwu gets a little more specific here: Explanation but I'm going to quote the important stuff to FULLY unlock bootloader:
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
Download Magisk zip installer to your SD Card or internal storage
Download multidisabler.zip (link: From Telegram Group and also attached in this thread) and add to SD Card or internal storage
Instructions!For installing 2.5.1/2.5.2:
Reboot to TWRP
Flash NcX 2.5.1.img or NcX 2.5.2 as "super" image in TWRP
Reboot to Recovery
Format data if you are coming from Stock ROM. If you are coming from NcX 2.5 then you don't need to wipe or format, you can just skip this step.
Flash multidisabler (this is required always)
Flash Magisk zip (optional)
Reboot and wait patiently
For installing 2.5:
Reboot to download mode and add AP_NcX 2.5 A71 in AP on Odin
Uncheck the Auto reboot option in Odin
Flash
When it is finished, force a manual reboot (keep pressing VOL - and Power buttons together)
Immediately when phone reboots, boot to recovery mode (VOL + and Power button)
If your phone was unencrypted before, just do a normal wipe. If your phone was not unencrypted before, do a full data format (Go to WIPE option in TWRP, select FORMAT DATA button at the bottom and they type yes on the keyboard. This will completely wipe your internal storage so be sure to backup and photos, music, etc... you have in internal media.)
Flash multidisabler to ensure you do not get encrypted
Flash magisk (I don't know if this is mandatory, I would fully recommend it though)
Reboot and wait patiently
Credits! @ananjaser1211 for all your help and always willing to lend a helping hand
@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@sac23 for his tutorial on how to fix Secure Folder which you can find here: https://forum.xda-developers.com/showpost.php?p=82978861&postcount=1522
@Belco02 for the extra camera modes and features
@ianmacd in Telegram group TWRP/Root Samsung Android Devices for compiling TWRP for us
@ Samsung for the firmware
@ Team TWRP for their amazing recovery
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
XDA:DevDB Information
NcX 2.5 for A71, ROM for the Samsung Galaxy A71
Contributors
ShaDisNX255, Ian Macdonald
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: OneUI 2.5
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2020-10-08
Created 2020-10-08
Last Updated 2020-10-08
Join our Telegram group
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Discord group
Code:
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Discord
Android group in spanish
Link: Grupo Android
FAQ
[Q] My phone is stuck in bootloop/infinite boot, what should I do?
[A] It is normal for first instalation to take aprox 10-20 minutes on first boot, let it sit for a little bit
[Q] Even after 20 minutes, my phone is still in a bootloop/infinite boot, what can I do?
[A] It is possible that your previoius Android setup is conflicting with this new setup. Please, do the following:
1. FORMAT DATA (not WIPE, FORMAT!)
2. Try the instalation of NcX again
[Q] I've found a bug, what should I do
[A] Please read the "Bugs" section of the thread to see if your bug has been reported, if it hasn't, please let me know exactly what the problem is so I can take a look
[Q] I flashed magisk on TWRP but no apps are asking for SU Permission
[A] Make sure you have the Magisk Manager app installed
[Q] I don't see Magisk Manager in my apps
[A] You need to download the manager from the official source: https://github.com/topjohnwu/Magisk
[Q] Something bothers me and I want it fixed/changed
[A] Please, kindly make a request and if it's within my grasp, I'll try to fix it. Just, don't be rude and demand something. Either that or return to stock, your choice
How to report a bug/Ask for a change
Over the small amount of time I've been doing my edits and shared them with the community, I've noticed something that seems to irritate me. I can't speak for all the developers on this forum, but I do edits/ROMs/PORTs/etc... to what I like. I don't work for anybody else but me. I share my work because it may have something of value to other people and/or some people may share the same taste as me on regards to what they want on a ROM.
That being said, that doesn't mean I will completely ignore what the community has to say.
First and foremost, it must be said, I am merely a beginner. I do not claim to be a professional developer that knows how to add everything, I am nowhere close and I learn as I go.
There are ways to ask for something and/or report a bug when it comes to ROMs, and this post is my attempt to try to explain how to (and how not to) report a bug in order to help me out as much as possible to try to fix something
You can also ask for something to be added, but there are also ways to ask for something
So, here we go
Keep in mind:
I do not add stuff that can easily be downloaded from the Playstore
I, myself, don't do kernel edits
I COULD remove stuff if NOBODY uses it
---REPORTING BUGS---
How NOT to report a bug:
"SystemUI (or any app)is crashing, please help!"
"Instagram doesn't allow me to edit my post, what could be wrong?"
"My bank account app is not letting me do such thing"
These posts are sort of pointless as they only state something but I have no context on what could be causing it. Also, I can't really control (for the most part) third-party apps, so if you're going to ask about them this way, don't even bother
A slightly better way to report a bug:
"I clean installed the ROM and was working fine, after I installed Facebook and logged in, I immediately uploaded a photo and SystemUI started to crash. Can you look in to it?"
"I tried to install Black Neon theme (a link to it would work as well) and it was working fine until I tried to activate AOD (or anything else for some reason) and SystemUI (or any other app) is crashing, could you look in to it?"
"My bank account app doesn't let me take a screenshot of my accounts. I get a toast notification saying "Can't take screenshot due to security policy"
As you can see, this provides a bit more context and explanation on your current situation. This gives me a little more detail on trying to replicate the problem and hopefully could fix it by replicating it. Well, except for point #3 which is out of my hands for the most part (I think). If you include what kernel you're using would make everything better! Also any significant change that would require root (like xposed and or anything that modifies /system also needs to be informed for better results)
The BEST way to report a bug:
LOGCAT!!!!!!!!!!!!!!!!!!
Please learn the ins and outs of a logcat, this really helps a lot on finding what the problem is. Also, please give a brief explanation as the above examples when providing a log cat
---ASKING FOR STUFF TO BE ADDED---
How NOT to ask for stuff:
On your next update, add iris scanner
You should add (app) on your next update
Hey, please add (app or feature) on your next update
No, I do not work for you. Even if you say please like the third example, that doesn't mean you're being polite. It still sounds like an order lol so you should probably rephrase your request.
How to ask for stuff to be added to my work:
Would you be so kind to add (feature) to your ROM, if possible?
Would it be possible to add this app to your ROM?
Please, can you add (feature) to your ROM, if it isn't much to ask?
See how politeness makes everything better? You're not demanding it, you're just politely asking to see if maybe it is within my grasp to add something. And if all request would be like this, I can assure you I'd try my best to add said feature
I hope this is useful to you or I at least hope that some people read it.
If not, I can just tell you to return to stock ROM, probably better than any ROM I put out anyway
Enjoy guys, keep on the lookout for updates. I plan on adding more MODs and fixes
Attach the singletake .xml also here
sankhauaa said:
Attach the singletake .xml also here
Click to expand...
Click to collapse
I'll hold it off.
Plan on adding a future update with this and more stuff included
Good mod! Downloading...
well done mate, nice to see
New update hopefully tomorrow.
What's new?
-Fix Secure Folder, now working
-Fix Smart View mirroring, now working
-Adding CSC features, in progress
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
hans3103 said:
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
Click to expand...
Click to collapse
If you've already rooted, that means you have fully unlocked bootloader and it means that you can now freely install my ROM.
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
hans3103 said:
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
Click to expand...
Click to collapse
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
ShaDisNX255 said:
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
Click to expand...
Click to collapse
I will try it for sure, can I do an update or do I have to make a clean install?
hans3103 said:
I will try it for sure, can I do an update or do I have to make a clean install?
Click to expand...
Click to collapse
It can be installed with current version so no need to wipe data
ShaDisNX255 said:
It can be installed with current version so no need to wipe data
Click to expand...
Click to collapse
Very nice....many thanks!
nice business friend
Even if resizing in vendor, it will be nice because it will be very possible to make mod and custom kernel
No idea
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
zorexblade said:
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
Click to expand...
Click to collapse
Are you getting to boot animation?
Were there any red messages in TWRP when you were installing?
Newest 4.8 Page 4
Newest 4.7.5 Page 4
Newest 4.7 page 2
Hi guys
I've left pulkits lineage in case of big problem with Bluetooth car connection (I've tried some different fw and clean flash.... But no success) and screenshot edit.
With cherish out of the box Bluetooth is stable and screenshot edit is working.
It looks stable, good customizable and very good bb (more experience later)
CherishOS v4.6.1 - OFFICIAL | Android 13
: Redmi Note 10 Pro (sweet)
: Mar-30-2023
: @JYR_RC
Changelog HOTFIX:
Fixed minor bugs
Leica Camera it's Default
Enjoy CherishOS
Download:
Gapps
https://sourceforge.net/projects/cherish-os/files/device/sweet/Cherish-OS-v4.6.1-20230330-2002-HOTFIX-sweet-OFFICIAL-GApps.zip/download
Vanilla
https://sourceforge.net/projects/cherish-os/files/device/sweet/Cherish-OS-v4.6.1-20230330-1819-HOTFIX-sweet-OFFICIAL-Vanilla.zip/download
Notes:
Clean installation recommended
(Dirty in Hotfix)
No need any firmware
In vanilla version recommend NiKGapps
Passes CTS By Default
Crédits:
@hungphan2001 For Sources
@wolfwild94 For testing And Help
@franlop77 For source Tree
@jimgsey For Help
@RooGhz720 For Kernel Source
Screenshots
can you share some bb details, screenshots, etc.
thxjxs said:
can you share some bb details, screenshots, etc.
Click to expand...
Click to collapse
Screenshots in post 2
Bb in some days
Laptapper said:
Hi guys
I've left pulkits lineage in case of big problem with Bluetooth car connection (I've tried some different fw and clean flash.... But no success) and screenshot edit.
Click to expand...
Click to collapse
Hello, did you try to downgrade bluetooth AVRCP version ? You can change it in the developer settings.
Default version is 1.5 (in Pulkit based rom) and I have problems too with my Pionner Car system.
It's working for me with 1.4 version, so you can try ;-)
Can you check the version setting in CherishOS ?
2spirit said:
Hello, did you try to downgrade bluetooth AVRCP version ? You can change it in the developer settings.
Default version is 1.5 (in Pulkit based rom) and I have problems too with my Pionner Car system.
It's working for me with 1.4 version, so you can try ;-)
Can you check the version setting in CherishOS ?
Click to expand...
Click to collapse
Yes I've tried all in developer options.
Cherish
AVRCP 1.5 (Standard)
MAP 1.2 (Standard)
Hello every one,, after clean installing this rom I have problem with contact app.. Can't import my VCF offline contacts,, message that you have disable required permission..
There is no permission disabled in permission ..
I used orange fox recovery with 13 fw..
Any suggestion?!
Thanks
Dash_k said:
Hello every one,, after clean installing this rom I have problem with contact app.. Can't import my VCF offline contacts,, message that you have disable required permission..
There is no permission disabled in permission ..
I used orange fox recovery with 13 fw..
Any suggestion?!
Thanks
Click to expand...
Click to collapse
According installation manual no fw flash is written
Try other phone book or importer app (
https://play.google.com/store/apps/details?id=com.hb.dialer.free
https://play.google.com/store/apps/details?id=vcf.file.viewer.contactimport.csv.viewer )
Laptapper said:
According installation manual no fw flash is written
Try other phone book or importer app (
https://play.google.com/store/apps/details?id=com.hb.dialer.free
https://play.google.com/store/apps/details?id=vcf.file.viewer.contactimport.csv.viewer )
Click to expand...
Click to collapse
Ok..thanks..will try to reinstall and see
Bb good (with sync back of some GB photos of Google photos unlimited storage)
Thanks Sir
Hello, total noob, where do I look to learn to install this rom? I've Unlocked the Bootloader already.
SNERTTT said:
Hello, total noob, where do I look to learn to install this rom? I've Unlocked the Bootloader already.
Click to expand...
Click to collapse
First read about TWRP and orange fox recovery. Then try to install the custom recovery. If done come back again...
So I followed the steps in the image below and It's resulted in the phone rebooting to TWRP despite having installed this rom
SNERTTT said:
So I followed the steps in the image below and It's resulted in the phone rebooting to TWRP despite having installed this rom View attachment 5880865
Click to expand...
Click to collapse
oh hang on i was installing the GAPPs, does that only include said apps?
Now it's rebooting to OrangeFox...
Edit 1: Following these steps:
At step 4 i get "unable to mount storage", then, installing CherishOS I get the same "Unable to mount storage" errror message. Notably, the phone has an SD Card in it and i was installing the .zip files from that SD, not sure if that is/isn't what you're supposed to do.
Edit 2: Ok, so TWRP it said to try formatting, this somehow resolved seemingly everything.. It just booted straight into Cherish.. Seems fishy to me, there was some skepticism in my mind as to the stuff I was selecting to wipe, so I'm still looking for comments of reassurance/advice.
SNERTTT said:
Now it's rebooting to OrangeFox...
Edit 1: Following these steps:
View attachment 5880871
At step 4 i get "unable to mount storage", then, installing CherishOS I get the same "Unable to mount storage" errror message. Notably, the phone has an SD Card in it and i was installing the .zip files from that SD, not sure if that is/isn't what you're supposed to do.
Edit 2: Ok, so TWRP it said to try formatting, this somehow resolved seemingly everything.. It just booted straight into Cherish.. Seems fishy to me, there was some skepticism in my mind as to the stuff I was selecting to wipe, so I'm still looking for comments of reassurance/advice.
Click to expand...
Click to collapse
All is ok, first you've forgot to format data.
If all is running now it's fine. Congrats to your first flash
I also left lineage OS after those weird safetynet issues and moved over to PixelOS I'm move to this but I have two questions @Laptapper
1. Are you rooted on it
2. Are there any other battery steps you took (build.prop,kernel tweaks,magisk modules)
Thanks
OFProzo said:
I also left lineage OS after those weird safetynet issues and moved over to PixelOS I'm move to this but I have two questions @Laptapper
1. Are you rooted on it
2. Are there any other battery steps you took (build.prop,kernel tweaks,magisk modules)
Thanks
Click to expand...
Click to collapse
Yes, never unrooted for me
No, not now. But I'm in tests....
Laptapper said:
All is ok, first you've forgot to format data.
If all is running now it's fine. Congrats to your first flash
Click to expand...
Click to collapse
Ah good, thanks! Glad i didn't brick my phone taking shots completely in the dark.