Related
Hello,
i need ur help and advice.
since two days i dont have Access to "google play services", since i did an Update for the custom rom i had. (Victara, NIGHTLY CynogenMod or something)
So now my question is what posibilitys i have.
Can i get the Original Rom again? is it posible to have it Rooted while on Original Rom?
I have Bootloader unlocked via the Motorola page.
If i have to go with another Custom Rom, which one should i choose?
Kind regards
push pls
Bedii said:
push pls
Click to expand...
Click to collapse
Here are the full factory firmwares if you need to go back to stock:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Which Gapps did you use? You might have the wrong versions for your ROM.
Delta Gapps:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Open Gapps:
http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
You should probably clean flash your ROM, and the latest Gapps (make sure you flash MarshMallow Gapps on a MarshMallow ROM).
Gus Ghanem said:
Here are the full factory firmwares if you need to go back to stock:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Which Gapps did you use? You might have the wrong versions for your ROM.
Delta Gapps:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Open Gapps:
http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
You should probably clean flash your ROM, and the latest Gapps (make sure you flash MarshMallow Gapps on a MarshMallow ROM).
Click to expand...
Click to collapse
I did use the Standard gapps. the one that said "take this if u are not sure which version u need"
i Installed a new ROM. but it drains a lot of my Batterie... dont know why.
Also i cant really root it. Everytime i try to Update SuperSU# it fails.
Can u tell me a good ROM i could use? or can i go to original somehow while having my Phone rooted?
Bedii said:
I did use the Standard gapps. the one that said "take this if u are not sure which version u need"
i Installed a new ROM. but it drains a lot of my Batterie... dont know why.
Also i cant really root it. Everytime i try to Update SuperSU# it fails.
Can u tell me a good ROM i could use? or can i go to original somehow while having my Phone rooted?
Click to expand...
Click to collapse
If you go back to stock factory firmware, you will lose root, but I'm sure there are ways to root it, but I've never done it on stock, so I don't know what works.
But, CM based ROMs should already have root built-in, under Developer Options, Root Access for Apps and ADB.
I prefer CyanogenMod because it is always actively being developed and updated, and is well supported.
Right now CyanPop looks like a good one, although I've never tried it (should already have root)
http://forum.xda-developers.com/moto-x-2014/development/rom-cyanpop-v4-5-t3277786
Actually that is the version that i have. I installed that and Gappa "ARM" 6.0. Dont know what i choose in the last section anymore.
Since i installed it i have the problem that the Batterie gets empty pretty fast.. and also i get Errors like "Couldnt load E-mail services" or something like that.
Also i cant update SuperSU#, update always fails
I want to clean install it again, not sure tho what gapps i should use.
Gus Ghanem said:
If you go back to stock factory firmware, you will lose root, but I'm sure there are ways to root it, but I've never done it on stock, so I don't know what works.
But, CM based ROMs should already have root built-in, under Developer Options, Root Access for Apps and ADB.
I prefer CyanogenMod because it is always actively being developed and updated, and is well supported.
Right now CyanPop looks like a good one, although I've never tried it (should already have root)
http://forum.xda-developers.com/moto-x-2014/development/rom-cyanpop-v4-5-t3277786
Click to expand...
Click to collapse
Can u help me with that last post?
Bedii said:
Can u help me with that last post?
Click to expand...
Click to collapse
I'm not sure what you would like to do.
There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode.
https://dl.twrp.me/victara/
If you want to start over clean, to flash a ROM and Gapps:
THIS WILL WIPE EVERYTHING!
Boot into Recovery, and tap Wipe, then Advanced, then select:
Dalvik/ART cache
System
Data
Cache
Then swipe to wipe them.
Copy over the ROM and Gapps zip files from your computer to your internal storage, if you haven't already.
Tap Install and flash the ROM, then tap clear cache/dalvik
Tap Install again and flash Gapps, then clear cache/dalvik
Reboot system and don't install supersu
Gus Ghanem said:
I'm not sure what you would like to do.
There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode.
https://dl.twrp.me/victara/
If you want to start over clean, to flash a ROM and Gapps:
THIS WILL WIPE EVERYTHING!
Boot into Recovery, and tap Wipe, then Advanced, then select:
Dalvik/ART cache
System
Data
Cache
Then swipe to wipe them.
Copy over the ROM and Gapps zip files from your computer to your internal storage, if you haven't already.
Tap Install and flash the ROM, then tap clear cache/dalvik
Tap Install again and flash Gapps, then clear cache/dalvik
Reboot system and don't install supersu
Click to expand...
Click to collapse
i already wiped everything last time, thats why i want to do it again to be clean.
what u said here:
"There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode."
is not nessesary if i want the clean install, right?
But i still dont know which Gapps i should get. I get Errors in my Current ROM, and i think its because i choose the wrong Gapps.
Also, the TWRP 3.0.0 u recommended, is it a stable Rom?
Bedii said:
i already wiped everything last time, thats why i want to do it again to be clean.
what u said here:
"There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode."
is not nessesary if i want the clean install, right?
But i still dont know which Gapps i should get. I get Errors in my Current ROM, and i think its because i choose the wrong Gapps.
Also, the TWRP 3.0.0 u recommended, is it a stable Rom?
Click to expand...
Click to collapse
TWRP is a custom recovery not a ROM, it allows you to flash ROMs and Gapps.
Right now, the only Gapps that are being constantly updated are Open Gapps and Delta Gapps, they both support MarshMallow, and don't have any serious issues. I use Delta Gapps with CM because they allow you to flash only the apps you want, or replace some of the CM stock apps, if you prefer the Google versions.
Here are the different Open Gapps packages, and the apps they contain:
https://github.com/opengapps/opengapps/wiki/Package-Comparison
If your ROM is MarshMallow then use the Delta Gapps under MarshMallow.
DO NOT MIX GAPPS, use either Delta Gapps, OR Open Gapps, but not both.
Gus Ghanem said:
TWRP is a custom recovery not a ROM, it allows you to flash ROMs and Gapps.
Right now, the only Gapps that are being constantly updated are Open Gapps and Delta Gapps, they both support MarshMallow, and don't have any serious issues. I use Delta Gapps with CM because they allow you to flash only the apps you want, or replace some of the CM stock apps, if you prefer the Google versions.
Here are the different Open Gapps packages, and the apps they contain:
https://github.com/opengapps/opengapps/wiki/Package-Comparison
If your ROM is MarshMallow then use the Delta Gapps under MarshMallow.
DO NOT MIX GAPPS, use either Delta Gapps, OR Open Gapps, but not both.
Click to expand...
Click to collapse
Hey,
i need ur help again.. sry.
I downloaded this now
http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
Is this a good, stable version?
Can u link me to the Gapps that i need? i cant figure out what im doing wrong...
Bedii said:
Hey,
i need ur help again.. sry.
I downloaded this now
http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
Is this a good, stable version?
Can u link me to the Gapps that i need? i cant figure out what im doing wrong...
Click to expand...
Click to collapse
That looks like stock factory firmware, you don't need Gapps for it. You only flash Gapps with custom ROMs, because they don't include the Google Play Store and Services (Google doesn't allow it). Which model and region is your phone?
Gus Ghanem said:
That looks like stock factory firmware, you don't need Gapps for it. You only flash Gapps with custom ROMs, because they don't include the Google Play Store and Services (Google doesn't allow it). Which model and region is your phone?
Click to expand...
Click to collapse
Serialnumber is TA99300WN5.
Dont know what region the phone is from, im from GER.
U said its a stock recovery, does that mean root is not possible?
Do a clean install of your ROM (cyanpop--which tells you clearly not to install SuperSU) with full wipes as per the ROM instructions. Add 'Open Gapps arm 6.0 full'. Follow the instructions.
Or
Read the various guides in Tony Stark's sticky thread for installing the stock ROM (if you're in Germany then it'll be for an xt1092*) and rooting a stock ROM, make sure you understand them, and then do as they say.
Gus has given you several very straightforward and helpful answers and you need to do some real brainwork to make sure you understand what you're doing. I'm sure you'll manage it and learn from it, as we all have.
* you have to check the model of your phone.
kboya said:
Do a clean install of your ROM (cyanpop--which tells you clearly not to install SuperSU) with full wipes as per the ROM instructions. Add 'Open Gapps arm 6.0 full'. Follow the instructions.
Or
Read the various guides in Tony Stark's sticky thread for installing the stock ROM (if you're in Germany then it'll be for an xt1092*) and rooting a stock ROM, make sure you understand them, and then do as they say.
Gus has given you several very straightforward and helpful answers and you need to do some real brainwork to make sure you understand what you're doing. I'm sure you'll manage it and learn from it, as we all have.
* you have to check the model of your phone.
Click to expand...
Click to collapse
Okay, i did 3 things now..
First i installed this: http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
i just followed that tutorial. But when i started my phone, i couldnt open the most apps, they just closed with the Erro message e.g "Whatsapp closed".
Then i tried to install the stock ROM. i was on Tony Starks sticky, and just followed the tutorial. But after flashing the stock ROM into my device, i couldnt reboot it. It just booted into fastboot.
So i tried the Method one again and installed the ROM again. now i can open APP's, but cant get a mobile connection... so no calls and no SMS
I dont know whats wrong, always diffrent errors with diffrent trys...
You are having problems because you seem to be flashing the stock image for an xt1097 onto what I guess is an xt1092.
I was clear about checking phone models and being sure you understood the different instructions and guides.
Start again and make sure you have the right things. I assume you made no nandroid backups to return to.
kboya said:
You are having problems because you seem to be flashing the stock image for an xt1097 onto what I guess is an xt1092.
I was clear about checking phone models and being sure you understood the different instructions and guides.
Start again and make sure you have the right things. I assume you made no nandroid backups to return to.
Click to expand...
Click to collapse
With the new ROM i can see that i have XT1092. The old one just showed me "Moto x 2014".
This is the one i have atm: http://forum.xda-developers.com/moto-x-2014/development/rom-cyanogenmod-13-t3243768
There was no saying that it is for specific models, so my guess was that it works for all.
I tried to get the Stock Image via this tutorial : http://techbeasts.com/2014/11/11/how-to-restore-moto-x-2014-to-stock-firmware/#
Since i tried that i cant get a mobile connection with various ROM's, just WLAN workds atm. Also on that tutorial i searched if it was restricted to a Model that i dont have, but there seem to be none...
its not that i wasnt looking if it works for my model..
aI dont have a nandroid back up too
Well okay, i downloaded the Android 4.4.4 from Motorolas original site for my Phone. unrootet and than flashed it on my Phone.
Now everything is working fine. I dont like this old version tho. How do i get OTA updates? shouldnt he tell me that updates are available?
Well done! You'll probably not get updates with an unlocked bootloader, but this German site might help: http://www.android-hilfe.de/thema/factory-images-ota-4-4-5-0-5-1-6-0-retdeall-xt1092.703838/
kboya said:
Well done! You'll probably not get updates with an unlocked bootloader, but this German site might help: http://www.android-hilfe.de/thema/factory-images-ota-4-4-5-0-5-1-6-0-retdeall-xt1092.703838/
Click to expand...
Click to collapse
Unlocking the bootloader does not effect getting updates.
Sent from my XT1095 using Tapatalk
Hi,
my ASUS ME176CX currently is:
* rooted
* xposed
* able to boot "anything" (unsigned bootloader)
* using L-Speed
and is running UL-K013-WW-12.10.1.24
So fine so nice...but:
My charging rate drops from 0.5% each minute to 0.125% each minute.
APK-files I download from apkpure reaches the external SD-card as *.zip files, which
I first have to rename to install them (so the structure as such is not touched).
May be all this problems are a result of my experimenting...
I think it is time for the total reset of everything.
But what to take?
* UL-K013-WW-12.10.1.24 again ?
* UL-K013-WW-12.10.1.33 (I read about a sever impact to battery life, though) ?
* UL-K013-WW-12.10.1.36 ?
* the russian lite version of the 36er firmware (I read of not working audio/gps/camera with this?)
* anything else which I had not found while searching?
And: Since TWRP now is installed, I would flash whatever it is advisable to flash with that...
and overwriting the code of a running program -- in this case the flashing application: TWRP itsself.
At this point I need the help of some deep gurus, I think?
How should I flash what firmware to get "the most" (less lagging, more battery life) out of my tablet?
Thank you very much for any help!
Cheers,
Noriatell
PS: Does anyone has experienced any wearout of the internal flash due to write cycles so far?
i use .36 uk release and i havent got any issues with it, ive rooted and debloated (i dont know why people are banging on about a russian lite version, its just debloated aswell isnt it)..
Theres been no point really for TWRP so far, i dont know if a custom rom will be released anytime soon
Hi russy23,
thank you for your reply
One thing I didn't understand (language problem...I am no native english speaker):
"Theres been no point really for TWRP so far" means: There are no problem reported
so far flashing a official ROM with the combon of unsigned bootloader and permanent
TWRP?
Do I need to reflash the bootloader?TWRP again?
Sorry for the tutti frutti of questions...I simply fear to lock out myself from the tablet...
Thanks a lot!
Cheers
noriatell
Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good
russy23 said:
Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good
Click to expand...
Click to collapse
Hi russy32,
I flashed the 36er ROM...and got an error at the end...but it rebooted fine (so far...did made extensively testing right now, though).
I had to reflash SUPERsu and xposed, but this seems to be quite normal...
Do you know, what triggers this error (Saying "Error flashing <filename of ROM>.zip") ?
When reflashing the 24er ROM there was a problem with a check in one the scripts, which has to be removed by hand before flashing...
I currently dont know of any similiar with the 36er ROM. And that failure was right in the beginning of the process and the ROM.
Is there a way to check whether I am on 36er ROM now (something which is for sure, since the "About" is only a copy of a string...)?
Cheers,
noriatell
If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section
russy23 said:
If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section
Click to expand...
Click to collapse
Bad news...
To get a clean install without error I wiped cache, system, Dalvik-cache and system and reinstalled the ROM.
I got errors and a bootloader-loop (stuck in the "Intel" logo).
Now the tablet is charging...I need new power for the next steps.
TWRP is still working.
What had caused this?
How can I get back a clean boot?
Post edit:
I have reapplied my nandroid backup of the 24er ROM. It works so far (It boots). But I have
back the problems I described above.
Question remains:
How can I get a clean install of the 36er ROM?
Cheers,
noriatell
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.