I am running the beta 2 of RROS downloaded from the openkirin.net website. Every thing works fine and is smooth. However when I tried to go into settings in the YouTube app, the app stopped working. So I rebooted and tried again. Same result. Until now, this has been only happening in YouTube and in no other app (for now). Is there any fix for this or is this a bug? Thanks for your help.
Also a few other questions. How can I root this room like what TWRP and Magisk to use? If I want to change ROMs to LineageOS what should I do? What's the best custom kernel and how to install.
Edit. If there is an updated version of this build available how can I get that. Do I have to flash through TWRP? Because in the OTA update tab in customizations, it says can't check update. So far loving this ROM.
Also what's the main difference between LineageOS and RROS? Which one is better?
Reboot Twrp and try to clean cach or dalvikcach
Twro isn't compatible with open Kirin builds
Related
Hi,
I unlocked My bootloader successfully and installed twrp. Everythings fine so far.
Now I saw a thread mentioning a rollback to stock 6.0.0 is neccessary before installing cm13 because of the baseband. Do I still have to do that?
I also read about supersu. Do I have to install it before cm? In a rooted device? I thought supersu is for rooting the device?
And finally I thought cm13 is stable for My A9 but there are only nightly builds. Recommended for daily use?
Sry for all those noob questions, but I already read around for hours, without coming to a solution. Although flashing cm to My S5 Mini was alot easier.
I appreciate any help with that stuff.
?
Btw. I saw the supersu Thread and I found instructions on how to root the device.
The Instruction says I have to install supersu to root the device. In the supersu thread they say my device has to be rooted to install supersu.
Confusion is complete
On all devices I've had, never had to root (SuperSU) to install CyanogenMod. Just unlock bootloader and install twrp.
The SuperSU thread is wrong, I read the same thing when I had a nexus 5. I think it means just bootloader needs to be unlocked.
Only time I used SuperSU was if I was on stock rom. CM13 has root built in. Enable it in developer options.
As far as having to downgrade to 6.0, no idea if it's still needed. It's one of the reasons I'm still on stock. I don't like methods needed to downgrade.
thx
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
itsabrick said:
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
Click to expand...
Click to collapse
Really? Your phone had latest stock update and you installed cm13, and have no issues with it? No boot loops?
I've been using cm for some days. Some apps a crashing once a while, voice recording in whatsapp doesnt work without crashing the APP. AS far as I use My phone it is fine.
I booted the phone two times since I installed cm and no bootloops.
Bought it in germany.
Edit: Don't know it was the latest stock. I left the Version that was already installed on the phone. AS far as I remember it was 6.0.1
Hi!
My shieldtablet is running CM 12.1 (latest 20160807 build)... That works fine. It has latest TWRP 3.0.2-2 installed. And latest open GAPPS 5.1 (mini arm).
I am trying to get it to run CM 13 I've tried the first builds... didn't work... I tried today with the very latest nightly build 20160909... I do this by booting to recovery (TWRP 3.0.2-2) then going to install, and installing cm-13-20160909-NIGHTLY-shieldtablet.zip, and also open_gapps-arm-6.0-mini-20160912.zip (using the install multiple ZIPs feature of TWRP). Then I wipe DAVIK and cache and reboot.
Device stays forever at the nvidia logo.
I turn it off. Boot to recovery, reinstall CM 12.1 and opengapps 5.1 with same process... and that works fine. Machine reboots like a charm.
Any idea if I am missing a step? And what step that would be?
Thanks in advance,
Gilles.
Have you done the firmware update?
http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
Firmware Update:
If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.
3.1.1 (L)
4.2.0 (M)
Ah... No. I'm confused, though. What's the difference between L and M files? Do I need to flash both? Or just one?
I'm running CM 12.1 (Android 5.1.1 Lollipop)... So I could imagine having to flash L? But since I'm updating to 6.0.1... Would that mean M?
I imagine I download the ZIP, boot into TWRP, flash the right version. Then flash CM 13. Then flash Open GAPPS?
Or in a different order?
Thanks,
Gilles
I'm on stock, so it's just a shot in the dark - but i think this sounds logical:
L - Lollipop - 5.x, flash this when you are on 13.0 and want back to 12.1
M - Marshmallow - 6.x, flash this when you are on 12.1 and want flash 13.0
and then cm + gapps of course
regards,
wakko
All in one shot? Boot to TRWP, flash M, CM, GAPPS then reboot?
Hopefully - you'll only find out, when you try
So... that's exactly what I did, and it worked.
So steps : log into the SHIELD (CM 12.1 / Android 5.5.1)
Reboot to recovery (configured advanced reboot in developer options)
From recovery, selected the M drivers, then added the CM 13 zip, then added the Open GAPPS (6.0 ARM MINI) ZIP.
Then clicked FLASH
Then rebooted (I was impatient, didn't think to clear DALVIK and cache).
Machine rebooted and all seems well (SD card was detected and I said use as portable storage, Avast asked for a few more permissions, only Viber got confused and requires relinking to mobile account).
All nice.
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
ggravier said:
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
Click to expand...
Click to collapse
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Steel01 said:
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Click to expand...
Click to collapse
Thanks! Solved! So far, I love it!
ggravier said:
Thanks! Solved! So far, I love it!
Click to expand...
Click to collapse
I am having the exact same issues as OP. Not tried this fix yet, but seems promising. Question is, does any of those L or M files wotk with Nougat? or is there one for that too?
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.
So, I just installed Google Pay and wanted to connect it with my PayPal account. Everything was going fine until I finished the setup - the app showed me a message saying "Setup for paying in stores could not be finished - This smartphone can not be used to pay with in stores. This can be due to your phone being rooted or changed otherwise."
I have a completely vanilla LineageOS 15.1 (latest build) installed. No Magisk or Xposed. So this might be because I installed a custom ROM.
I will keep this thread updated - I will try to install the latest build of LineageOS 16, then if it does not work, continue to flash the latest stock ROM.
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
DKXC said:
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
Click to expand...
Click to collapse
Lineage builds for Samsung have that issue. They struggle to pass SafetyNet even if its not rooted. I'm running stock + Magisk and have Snapchat, Fortnite, Google Pay, and Pokemon Go all working no problem. Sac23's s9 port also has a good SafetyNet, just make sure to not use the Magisk included in the Aroma installer and use the latest zip
I've tried LineageOS 15 with Magisk. Google Pay works, but does not allow fingerprint use, only PIN/pattern. Same with WellsFargo app. It appears that something is incomplete or incorrect on the Samsung port of Lineage. Stock roms with Magisk do not have this issue.
So what's the best way to get android pay working? Just install Stock ROM and use Magisk to root?
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol