**** Work in progess ****
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AOSP Extended is an AOSP based rom which provides stock UI/UX with various customisations features along with the Substratum theme engine. The project has been made by cherry-picking various commits from various other projects. Being based on AOSP it provides a smooth and lag-free experience out of the box. We will constantly try to add more features and make it even better in future updates. A ROM by a user, for a user. #StayAOSP #ExtendYourDevice #BeExtended
Features
Silky smooth Android experience
Tons of customisation
Pixel-like UI (Launcher, settings, Google Now swipe...)
Full Substratum/OMS support
And much more (check official AEX website)
HW Accleration working !!!
Camera working
Kernel Features
Added IO Schedulers:Zen,Sio,Maple,Tripndroid
Added Governours:ElementalX,SmartMax,Tripndroid
Added Filesystem:SDCardFS,F2fs
Removed:EXFat causes random Bootloops and compatibility problems
Modified Dtb for faster charging (Tested around 2.4A at 5 Volt Chargepower with Anker 20W Wallcharger and 2A at 9V with Anker Power Port+1) experimental QC2.0 enabled Tests needed
Optimized for Battery:SmartmaX Cququiet:runnable Maple IO Sheduler as default
If you need performance change to Interactive and Cpuquiet:Balanced
Download
Latest release here.
https://androidfilehost.com/?w=files&flid=305454 no Zram
https://androidfilehost.com/?w=files&flid=305455 with Zram
https://androidfilehost.com/?w=files&flid=305556 DTB with QC2.0
Installation
Be on the latest firmware - if you are not, or aren't sure just flash latest stock recovery image for your device (you will lose data and TWRP so back data up and prepare to reflash TWRP)
From TWRP3.3.1 wipe Cache, Dalvik, System, Data and Internal Storage
Flash ROM
Flash ARM (not arm64!) 8.1 mini gapps
Flash DTB after all with : fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Netflix with SD:
Install latest Magisk
Download Libeoemcrypto patch and Props Fingerprint Mod
after reboot run in Terminal with Root rights Props choose 1 Edit device fingerprint
f Pick a certified fingerprint
16 Nvidia after that choose your device
Reboot and download Netflix from Store
Fixed: HW Accleration OMX works now
Camera full functional now
Kernel Bootloops/Random reboots
LTE Fix no Sim Card detected
Bugs
Netflix HD still not working
Nvidia Games crashes
As Workaround you could use Moonlight Gamestream to stream PC Games
Report bugs if you find any, every opinion is welcome, try to describe problems with as much detail as possible
Thanks
AEX team, LineageOS team, and all people around this project and this device
Special thanks to Steel01 and Artemka2008 for there help with the OMX Fix
XDAevDB Information
AOSP Extended for Shield Tablet, ROM for the Nvidia Shield Tablet
Contributors
Triodexe, Steel01, Artemka2008
Source Code: https://github.com/aospextended
Kernel Source: https://github.com/Triodex/TrioX-V04-Kernel
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.x
Based On: AOSP+LineageOS
PLATFORM_SECURITY_PATCH := 2020-02-05
Version Information
Status: Testing
Current Stable Version: 5.8
Stable Release Date: 2020-02-20
Created 2020-02-20
Last Updated 2020-02-29
So, the one thing left not working is the camera? Any hope of fixing that?
Thanks for releasing this. Can't wait to give it a try. Curious about the zram vs no zram. What is that? Also, what is dtb? Thanks again.
Hi
For the Camera bug i still try to get this fixed.
@bigcletus
Rom with Zram have 510MB Compressed RamSwap that you can increase with Kernel Managers like the StockRoms
Rom without Zram didnt have this
The Dtb is needed for the correct Charging Amps and Voltage Regulation so if you notice after flash the Rom that Quickcharge isnt working flash the Dtb again with Fastboot.
Greats Triodexe
I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.
bigcletus said:
I tried to install ROM (no Zram), but got stuck on Nvidia logo bootloop. Came from LOS 14.1 ROM, wiped everything mentioned except internal storage.
Click to expand...
Click to collapse
Hi
Did u use the Latest Twrp 3.3.1 to flash the Rom ?
For the Bootloop i dont know yet why it happens sometimes have the same problems again after a few restarts device stucks at Nvidia Logo but after manualy Poweroff/On its boots most af the time .
Guess there is a problem with one of the Governours/Shedulers i added or the Exfat Kernel Support.
But curios is the same stuff works in the Aosp4.6 Roms.
Could be that the Old Nvidia Vendor Blobs arent so good for Oreo based Roms but the newer ones from Shield Tv have no Hardware Accleration yet
But Dmesg didnt help me for this when i boot into recovery device always boots
You could try flash another Kernel the K1 Nougat from bleeblob or Bitos Kernel Version 10 should work better
So i reflashed the nozram over my Rom again and got no bootloop only wiped cache and dalvik
Could you look Into your Internal storage if there is some stuft left Form the Old Rom Apps and Magisk
Stores the Data there.
Greats Triodexe
I am using TWRP 3.2.3. I have flashed LOS 14.1 and 15.1 with this version of TWRP but maybe this rom needs the newer version?
I will try again when I have more time and I'll wipe the internal storage as well. Thanks.
Install and boots OK. I can't get Netflix to work.
Darkside281 said:
Install and boots OK. I can't get Netflix to work.
Click to expand...
Click to collapse
Hi yep Netflix is a beast cause it didnt accept the Widewine Version we got
Solution i used is Downloaded Netflix over ApkPure and use the Netflix Magisk OemCrypto patch.
Only in SD Quality then but for me its ok
Maybe with other Widewine Files we got Netflix in HD
Greats Triodexe
First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?
xconwayx said:
First off, thank you!
Will we need to flash this DTB with QC2.0 after every update or a one time deal?
Click to expand...
Click to collapse
Hi
No normaly the Dtb is inside the Kernel you only need to reflash it when Qc2.0 not working you can see it when dmesg kernel and look at the Bq2419-st8 message if it shows Qc2.0 Charger.
Or easier use ampere App when your charge mA goes around 2500 then QC works.
Qc2.0 charge takes then around 45 Minutes from 15% to 90% the last percents from 90-100% charges a liitle bit slower i wouldnt stress our Batterys to much
Greats Triodexe
So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.
I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?
Kf_Umbra said:
So flashing the dtb file using fastboot caused my Shield K1 to lock up completely, recovery and system were both bootlooping.
I was able to fix this by flashing the dtb located in this XDA thread with fastboot and wiping data, system, and cache, again using fastboot, afterwards. I was then able to boot into TWRP 3.3.1 normally and flash the ROM without the new dtb and it worked fine.
Maybe this new dtb needs more testing? Or maybe my shield is weird. Anyway just posting this here in case anyone else has this problem.
Click to expand...
Click to collapse
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe
Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?
bigcletus said:
I was able to get the rom to boot after updating TWRP to the latest version. Haven't had much time to check it out yet. I tried to get the Nvidia Games app to run a game but it force closes when selecting a game. Has this worked for anyone else?
Click to expand...
Click to collapse
Hi
Nvidia Games didnt work for me too i can open it and register but when i start to stream a game it crashes
With the newer Vendor Files it works but then the HW Accleration is broken.
Try to get this fixed together with the no working Camera but this crappy Logs in Logcat from Nvidia didnt show the reason why it crashes.
Only for the Camera i know that it happens after Jpeg creation that it crashes
Greats Triodexe
Triodexe said:
Hi
Never had this problem with the dtb can you post your Bootloader Version
Needed for this rom and Dtb are the Latest bootloader=4.00.2016.04-8b2413b7
Greats Triodexe
Click to expand...
Click to collapse
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.
Kf_Umbra said:
My bootloader is version 4.00.2016.04-8b2413b7, the latest one. I'm not sure why the dtb caused this to happen either. I even flashed NVIDIA's last recovery image before flashing this ROM, so I can't see where anything could go wrong.
Click to expand...
Click to collapse
I tryed the Dtb again flashed with Fastboot and no bootloop dont know why it didnt work for you.
Did Quickcharge works when you only flash the Rom ?
Greats Triodexe
bigcletus said:
Well, I thought i solved the booting problem with updating TRWP but it started to only boot 1 out of three times. Now it stopped booting completely so I restored my backup of LOS 14.1. How can I check the bootloader version?
Click to expand...
Click to collapse
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe
Triodexe said:
Hi
To see Bootloaderversion boot into bootloader with volume down and Power On.
You have the Shield K1 without Lte or the normal Shield with Lte ?
Greats Triodexe
Click to expand...
Click to collapse
I have the original LTE model.
Related
The last thing I remember flashing was Clockword Mod 11 last year, ever since then I have been running Firmware build 18.3.1.C.1.15. Upon seeing an update for my phone for Firmware build 18.3.1.C.1.17 I attemted to download it and kept getting the message "Cannot Verify" so after trying this out on PC Companion and relocking my bootloader I was still running into problems. So the simplest thing I could think of is to use Flashtool and flash the latest ftf from there (Firmware 18.6.A.0.182 - obtained from XperiFirm), at first I didnt think it was a problem to not wipe USER_DATA as I just thought of it as an upgrade, if that failed I persumed I would have to wipe everything (this didnt matter much anyway). So I went ahead and flashed the rom however when I went to boot my mobile I got a bootloop "Android is optimising apps xxx of xxx" this went on forever untill I cut the power using a pin. So I tried it again this time wiping everything and still the same problem :crying: . Then I came across people on the forums to use the older FlashTool verison 0.9.18.6 since the new FSC feature can cause probelms, this time I tried it again however I used the older Firmware 18.6.A.0.172 just to be failsafe. Still the same problem. Right then I was thinking Emma would save my phone so I went and applied the 4.4.4 Firmware 18.3.1.C.1.15 service (Which I had to begin with) but for some reason this seemed to have little effect despite trying it twice and reciving a "Sucessful Flash" message. Now I am left very confused as it is still booting in the lollipop style (optimising apps loop) even though I flashed a KitKat rom. I have been left without my phone all day because of this, any help would be STRONGLY APPRICIATED! . Thanks for your time
#1 Open your bootloader again
#2 Install TWRP (See 5.1.1 root topic for installation/guide)
#3 Open TWRP Wipe all data
#4 Reboot into recovery
#5 Flash any custom rom like Cyanogenmod through TWRP
Post results please this is fixable It's seems It's a soft brick which is an easy fix
What i think is you had corrupt data/left over data and after you relocked bootloader something went wrong after flashing. Though flashing should wipe all data let's see
Re-flash ftf wiping data and caches, you must do this if going from 4.4.4 to 5.1 and From 5.1 to 4.4.4 due to changes in runtime from dalvik to art and other changes.
How to get near enough stock?
Thanks for your replies, when I flashed the ftf's I did tick all the boxes under 'Wipe' on FlashTool, when that failed so did emma. I can try flashing CWM however the main purpose of this was for me to upgrade to Lollipop as I wanted a near enough stock experiance (Considering Z5 Rom) with root. When I tried CWM before there were a few things that I just coulnt get used to. Is there any way that I could use recovery to flash a stock rom with the lastest Lollipop releese or Z5 experiance as I have backups on PCC that I have to restore (Important contacts, media etc...) and I dont really want to use a CWM based rom . I wouldnt mind to flash Z5 however I dont know if this is possiable could you guys comfirm this? Thanks for your time .
[Update] TWRP recovery is working!
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Zane Finch said:
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Click to expand...
Click to collapse
Don't worry you're android is not messed up, let's do this to fix it back to regular :-
Before starting i highly recommend you charge your phone to have atleast 50+% battery and use the official cable provided also make sure the cable is firmly inplace,
#1 Enter Recovery, wipe all data
#2 Download Stock 5.1.1 i think you like that so get that (Make sure it is for your D2303 or whatever your model is)
#3 Install latest flashtools with latest patch (Or later versions if you don't want to risk it)
#4 Go to the location of flashtools (installation directory) for me it is C:\Flashtool\drivers Open the exe file there, select the 2 Flashmode and Fastboot drivers install them.
#5 Flash the ftf using flashtools
Post results
Somehow...
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Zane Finch said:
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Click to expand...
Click to collapse
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Optimising
ARandomIndian said:
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Click to expand...
Click to collapse
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Zane Finch said:
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Click to expand...
Click to collapse
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
ARandomIndian said:
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
Click to expand...
Click to collapse
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Zane Finch said:
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
Click to expand...
Click to collapse
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
[email protected] said:
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Click to expand...
Click to collapse
ARandomIndian said:
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
Click to expand...
Click to collapse
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Zane Finch said:
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Click to expand...
Click to collapse
Okay nice post the results
ARandomIndian said:
Okay nice post the results
Click to expand...
Click to collapse
I flashed that very bootloder before I flashed the Lollipop ftf I booted my phone and the same thing happend, so I tried it again this time flashing afterwards an still booting with the same damn screen . Was I definatly using the correct bootloader or am I missing out anything when flashing? My phones rebooted like 5 times now for the 'optimisation' and its getting nowhere .
Shall I fire up my classic Nokia 5230 with custom Symbian to record a video so you guys can see what happens when it boots?
Did you wipe user data and cache when flashing the ftf
[email protected] said:
Did you wipe user data and cache when flashing the ftf
Click to expand...
Click to collapse
Yes, everything in the 'Wipe' section was ticked, infact before I flashed it again I also wiped Dalvik, cache, data and system in TWRP.
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay flash this version of Cyanogen http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 choose the latest one
We'll see what the issue can be any ideas @linuxtt
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
Zane Finch said:
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
Click to expand...
Click to collapse
Okay can you please flash another FTF? First try a new 5.1.1 ftf from another source for your model and then try older versions like Kitkat and post results please
Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17
Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP
Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!
e6833
thank you.
is it working for z5p Dual?
faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?
e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?
faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?
e6683能用吗，或者说e6653
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz
WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1
OP Updated with rev7 for both e6853 & e6883
enjoy
Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse
CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
DOWNLOAD Official
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS
MAJOR BUGS:
huh ?
Minor bugs:
flash on your own risk.
FLASHING
First Time:
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
reboot
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS 10
Version Information
Status: Stable
Created 2019-10-02
Last Updated 2019-11-19
amazing , thanks
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Gordietm said:
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Click to expand...
Click to collapse
That should be ob obvious, but i will add it
[ROM][BETA] Omnirom for Oneplus7pro [10]
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Click to expand...
Click to collapse
Always nano
paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Read OP : flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
[ROM][BETA] Omnirom for Oneplus7pro [10]
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Sent from my iPad using Tapatalk Pro
paatha13 said:
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Click to expand...
Click to collapse
Yes
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Good luck
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Probably you missed something, skipped one step etc.
B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
No, oos camera also works fine
I have no idea what it is. Had to boot a fastboot rom just to get back up and running after that last crashdump. going to go back to OOS for a little I think. I have never had a rom do this but this one has done it every time I have tried. Thing is I love Omni so I hope one day i can get it running properly.
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
Don't worry i didn't forget lol. That's why i'm going to keep trying after every release. It will work for me one day.
[ROM][BETA] Omnirom for Oneplus7pro [10]
Everything fine with installations no had any issue with first attempt.
Installing nano gapps not had any issue too this time at opposite with weekend build.
Seems this build more stable and I'm now charging the phone,download my usual staff from play store,will setup my device and will start to work on it later when phone full charge.
Thanks @darkobas.
darkobas said:
No, oos camera also works fine
Click to expand...
Click to collapse
Yes I can confirm OOS camera working fine.
Sent from my iPad using Tapatalk Pro
Does anyone know of an app or mod that allows the navigation buttons to be inverted? The custom navbar app doesn't work on 10 yet and that isn't integrated into the rom yet. I'll live but it is tough to try to retrain the brain, ha!
First impressions using couple of hours is solid.
Battery life look promising and satisfactory.
Very smooth experience so far.
Speaker loudness and quality is on par with oxygen just like with Pie version.
Brightness level seems on par with high oxygen levels although I haven't test it in sunlight, will do tomorrow [emoji14]
Stock(android 10) gesture navigation works great but prefer oxygen one and since using nova launcher I'm with vivid gesture navigation app since when using third-party launcher automatically stock gesture navigation are disabled.
There's dark mode but I'm not fan of it since it's dark gray and not black that prefer (will use substratum to apply truly black theme almost everywhere)
Vast majority Omni features working fine so far.
Wi-Fi, mobile data, so far all excellent, BT will test tomorrow intensively.
Almost all oxygen features are present and worked fine, except vibration need some tuning but that also appy to stable OOS 10 version.
On Pie vibration was better both Omni and OOS.
High brightness level is still present
I found some bugs though like dt2w not such reliable almost half of the attempts needed 2 and rare 3 times to wake up screen or even press the power button at end because not responding at all.
Aldo digital wellbeing to me every time try to open I'm getting fc.
Safety net not passing through magisk also.
I assume will improve in future build don't forget it's still beta.
More observations and safe conclusions will have after couple of days of using the new rom.
But so far general impressions after few hours is at good and satisfactory level and the build is safe to be daily driver for sure.
Sent from my GM1913 using Tapatalk
Just wondering why I can't download the Samsung wearable app in the Google Play Store on this. When I get it from the APK it tells me that this software which is on my phone is not compatible with the watch is there a way to fix this so I can connect my Galaxy watch to this amazing ROM this happens to me on every single ROM except CR Droid 9.0 don't know why:crying:
This is a pic of what the Samsung wearable app said
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your zeroltexx, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
voLTE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- enesuzun2002
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
XDA:DevDB Information
crdroid zerolte, ROM for the Samsung Galaxy S6 Edge
Contributors
SimurgAnka, Enesuzun2002
Source Code: https://github.com/Exynos7420
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-04-16
Last Updated 2020-04-16
Reserved 1
Reserved 2
No Sim
No sim detected on s6E G925i
zerofltexx:crying:?
does this rom get updated monthly just like other Android 10 roms?
i just flashed this rom. thanks.
Thanks for the work of my favorite CrDroid rom, I hope and you can fix the problem of the sim, it does not detect it and you cannot make calls or browse with data. I have a G925i
the camera does not focus
is it possible to use the rom even without the gapps?
Thanks
Any reason why this wouldn't work with the tmobile variant (and other american carriers)? Just curious.
Any issues on G925i?
areyouanand said:
Any issues on G925i?
Click to expand...
Click to collapse
Sim card keeps turning on and off.
flip cover support
Installed this ROM on my girls S6 Edge and it runs great so far. So thanks for your effort.
Is there any chance to get the official flip cover working again? Currently it doesn't lock/unlock the phone when closing/opening the cover.
Alphalife said:
Sim card keeps turning on and off.
Click to expand...
Click to collapse
Am running Samsung Galaxy s6 edge sm-g925t
But my SIM card is not detected
Great ROM!
I just installed the latest rom, everything is fine! (g925f)... even bluetooth works! which was the reason i tested this rom, because all the other rom's i tested crashed my bluetooth-carradio, this rom works perfekt! GPS, cam, wifi, mobile data, all working fine... :good: very great rom! thanks a lot to the developers!!!!!
Awesome Rom. Everything working perfectly. No issue at all.
I flashed magisk and installed Servicely., the battery backup is now excellent specially when the phone is idle.
Thanks for this awesome rom.
I had the same issue as the other guys. I received my first call on the phone and since then the signal keeps appearing and disappearing, and no reboot fixed it. It's a shame since everything else, from camera, mobile data, bt, ringtones, works, and works well. It's a great rom if it wasn't for that issue makes a great daily driver rom. I have a SM-G925I, and somehow the rom says it's a G925F.
Great rom on 925f
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
redfox64 said:
.......I have a SM-G925I, and somehow the rom says it's a G925F.
Click to expand...
Click to collapse
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
buddy_67 said:
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
Click to expand...
Click to collapse
I dont know why but the issue with the signal solved itself. The only other bug I found was with screen casting. When it's connecting with wireless screen option enabled (without it, no tv is seen by the phone) the phone restarts itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer
Reserved
Screenshots by Android 10 ????
I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
@justasic What version of the camera program?
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,
Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data
muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.
Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.
ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.
Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11