Hi there,
currently I am still using MIUI 8 Global (7.4.20) in Beta version with weakly updates on my RM Note 2 Prime and I am quite fine with it (above all the really impressive fast charging time).
But I also want to keep in touch with newer versions of Android as far as possible without giving up the overall usability of my phone and its components (Battery Live, Charging Time, GPS, Camera, Audio...).
So I try to keep myself informed about newer ROM versions for RM Note 2 which seems unfortunately not be supported by Xiaomi regarding newer Android Releases.
That lead my to RR and Lineage OS with RR seeming to be the better choice.
Now I am wondering what would be an efficient way to flash one of these ROMs with newer Android over my current MIUI ROM while keeping or restoring all my data, pictures, chats, navigation routes etc.?
Does Xiaomi PC suite also work with RR or Lineage OS?
All experiences, hints and tips are welcome!
Did someone else switch from MIUI to a newer Android ROM and what is your proposed procedure?
Thank you in advance!
Bye
Best way to get a custom ROM is to flash twrp!
When install with twrp you have to choose if you want to clear data, cache, dalvik, system, internal, external and otg, and so if you want to leave your data, the best option is to install Titanium backup (better with pro version) here you can safe all your apps (with all its data of course) and leave the backup in your internal.
Afterwards you can download any ROM you want (LP recommended!!) And better place it external if available.
Also to download gapps (Google apps) recommended
Than backup all your data with Titanium backup and you can boot after backup in twrp which is needed for custom ROMs!
Here you have to clear system (otherwise you will get error, because of cm based and miui based ROMs) and data+dalvik/cache.
Now you can choose with the install method your ROM and gapps and install.
Now you have to boot up system and after setup go into settings, build number 5times clicking, go to developer options and grant root access to all apps!
Now you have to install Titanium backup app again (pro recommended again) and choose the restore option
Now it will reinstall all apps with all its data and you can go on!
Hope I could help a bit
@Noobsi:
Thank you! Helps quite a lot. But what do you mean by "LP recommended"? Which ROM do you refer to here?
Regarding changing ROM (in my case this would be from MIUI to some kind of MM) I read that restoring Apps with their data is not recomended due to possible filesystem changes and things like that.
He means Lollipop (android 5) recommended, because marshmallow isn't stable enough.
IshtaNoob said:
He means Lollipop (android 5) recommended, because marshmallow isn't stable enough.
Click to expand...
Click to collapse
Thanks - this will leave me with MIUI further (since they [Xiaomi] will never bring it to newer Android versions it seems).
Try Dual Boot Patcher: https://forum.xda-developers.com/showthread.php?t=2447534
I use it to have MIUI 8 and Lineage OS 13, and when reboot, shows a menu to choose where want to boot.
Wow, did not even know such kind of things exists for Android mobiles too!
Thanks a lot! Are you happy with LOS13? Why did you choose it (instead of RR or something else)?
What are the diffs between MIUI8 and LOS13 you are experiencing? And which OS are you using more often?
And regarding Dual Boot Patcher: I also discovered other multi boot managers in Play Store for example, could I use them too or are all of them restricted/proposed to/for certain devices?
Im on latest stable MIUI 9 the problem is when I go to Settings > Storage, settings stops working. Tried wipeing dalvik and cache from twrp
Immortal0907 said:
Im on latest stable MIUI 9 the problem is when I go to Settings > Storage, settings stops working. Tried wipeing dalvik and cache from twrp
Click to expand...
Click to collapse
Can you be a bit more specific? Try answering the following question so that I can be helpful.
Which build of MIUI9 did you flash?
Which recovery did you use?
Did you flash OpenGapps package on the top of it?
Is it a custom MIUI that you use?
Most probable cause of this would be flashing a bigger OpenGapps package (stock or above) after flashing MIUI. OpenGapps tries to replace the stock MIUI applications with same application signature and hence causes incompatibility with the MIUI ecosystem. Hence, you face force-closes. The other reason might be the use of an incompatible third-party theme that does not render the Settings app properly. Just possibilities.
ADInfinity1999 said:
Can you be a bit more specific? Try answering the following question so that I can be helpful.
Which build of MIUI9 did you flash?
Which recovery did you use?
Did you flash OpenGapps package on the top of it?
Is it a custom MIUI that you use?
Most probable cause of this would be flashing a bigger OpenGapps package (stock or above) after flashing MIUI. OpenGapps tries to replace the stock MIUI applications with same application signature and hence causes incompatibility with the MIUI ecosystem. Hence, you face force-closes. The other reason might be the use of an incompatible third-party theme that does not render the Settings app properly. Just possibilities.
Click to expand...
Click to collapse
MIUI 9 latest global stable build. 9.6.2 redmi note 4 SD
TWRP Recovery
No i didnt flash gapps they are alredy in MIUI?
Its not custom miui, downloaded it from their site and flashed with mi flash. Im running magisk , camera2 api enabler module and viper4android. Everything is working great except that settings force close. Silly thing is ive been using this rom for like a month and didnt go into Storage... I just noticed that force close.
Immortal0907 said:
MIUI 9 latest global stable build. 9.6.2 redmi note 4 SD
TWRP Recovery
No i didnt flash gapps they are alredy in MIUI?
Its not custom miui, downloaded it from their site and flashed with mi flash. Im running magisk , camera2 api enabler module and viper4android. Everything is working great except that settings force close. Silly thing is ive been using this rom for like a month and didnt go into Storage... I just noticed that force close.
Click to expand...
Click to collapse
Oh I see. Have you tried disabling any of the magisk module and check whether that improves the condition? Force close while going into storage might actually mean something. How about you go to applications settings in Settings app and clear data and cache of storage manager app? This might actually work, you know. Let me know about that.
Solved it thanks for help. Issue was being cause by Face ID for RN4 module which I forgot to mention. I disabled it and it just works.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Magisk (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and Magisk
Information
This is native tablet port with normal keyboard, animations and other stuff.
My port based on:
framework and apps: T510XXU1ASCE and T515XXU1ASCK (new Tab A 10.1 SM-T510\515) Android 9.0 with 2019-03-01 security patch
libs and etc: A600NKSU1ZSB6 (SM-M105F) Android 9.0 with 2019-02-01 security patch
kernel: based on M105FDDU1ASB2 (SM-M105F) Android 9.0 3.18.91
Additional
1. Added OC for CPU (1690MHz - Kernel Adiutor, EX Kernel Manager) and GPU (default 1001, in OC 1146MHz - EX Kernel Manager)
2. Added themes from A600N
3. new wlan driver driver 4.0.10.206A_20181017 (from A600FNXXU3BSC5)
Links
LTE version:
1. 20190523: https://drive.google.com/file/d/1tK1F92bTWaaOBqUbkyVL8j3Sw50B0kre/view?usp=sharing
WiFi version:
1. 20190523: https://drive.google.com/file/d/1v2OM_IL8SCq5rLxOG1Vy21syd2KTq-Zd/view?usp=sharing
Magisk
Before run Magisk installer in TWRP - you need run small script - https://drive.google.com/file/d/1ZnnKHtDAl0ioHjQXiNO6wErZN8odsO0P/view?usp=sharing
It's simply unmount /cache partition and then mount it as /vendor. After run the script, you can install Magisk. If Magisk Manager does not appear in the list of apps - extract magisk.apk from Magisk installer and manually install it.
Sources
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Thanks
Thanks to Samsung
good morning Valera! I've been waiting for this a lot, since Samsung Pie is very good rom, I've already downloaded and flashed it. I just had time to try the basics and everything seems to work and the Ui is nice. Then I will make a good revision. Thank you very much for your great works!
@Valera1978 First of all, thanks for the great Pie port. Tab feels brand new, smooth. One thing I have found is the Themes/Wallpapers don't work. It will download wallpapers but when you go to apply, all you see is a black square, and nothing is applied. If it is an animated one for lock screen, it fc's the systemui when you try. Not a big deal as I can always apply wallpapers from my own collection. This is only issue so far and I have a feeling there won't be many more if any. Thanks for your works!!!
great job from shortcomings is at present a problem with the keyboard
I like this rom, it seems clean and pretty and I would like to be able to install magisk but I do not understand how to do it, could you explain it ?. Thank you
Bootloop
I tried this on my T580 coming from RR latest Pie ROM. Backed up ROM, factory reset wipe and installed just the wifi port. Wiped dalvic and rebooted. Bootloops at first Samsung screen. What did I do wrong?
edit: Never mind. Used Advanced Wipe for everything but Internal and SD. Booting now.
Great rom. Thanks for your effort.
Looks good thank you.
Are there other people who get a failed when they try to sign in the Samsung account?
In the pie_t510_t580_port there are the follwing settings that don't work or crashes, or don't belong in the wifi version and if it's possible should be removed.
T-roaming
Service provider
Mobile networks
Also in the About tablet there is some LTE version information
There is also the mobile hotspot settign in the connections
Cellphone signal icon in the at the top next to the wifi signal
These are for when you have the LTE version
Great work man!!! Thanks for your work!!
Anyone managed to download other languages keyboards in samsung keyboard because swiftkey lags
chris333333 said:
Anyone managed to download other languages keyboards in samsung keyboard because swiftkey lags
Click to expand...
Click to collapse
When I try to download other languages I get the message download failed. Probably a bug.
I hope you can port this rom for P585Y. Thank you
Tung Lam said:
I hope you can port this rom for P585Y. Thank you
Click to expand...
Click to collapse
I imagine that if you were to give the dev a P585, he might have a reason to port and a device to test it on. Otherwise, he has neither. I've seen this request many times, where someone with a different device, asks a dev to support theirs, and it never succeeds.
My personal hotspot isn't working after my first reboot... though I've uninstalled every 3rd party app.
Edit: It comes after installing Magisk.
EDIT 2: I've tried to reboot without installing any apps twice, and the problem appears, I only need hotspot for hosting an offline game with friends, like Bombsquad.
Is it debloated?
jurgenmmehja said:
Is it debloated?
Click to expand...
Click to collapse
Sort of...
This ROM needs more focus though, it's faster than the stock Oreo, but has weird bugs...
To solve that keyboard bug switch to the phone interface through build.prop editor,
Edit the line: ro.build.characteristics=tablet to phone instead of tablet.
Then add the languages you want then revert back the changes after finishing.
About that hotspot bug, I don't know, but can't we just use the stock kernel and wifi instead? What's the use of the new one?
About the Secure Folder, there's a way to set it up by modifying the kernel, and we never had it on our own device, we only got it on S7.
But there's a small question... do we have a chance to get a Samsung 64-bit ROM on our device? Because the Play Store will shut down on 32-bit devices in August 2021, though this device is 64-bit.
Is it really much faster than stock 8.1? None of the roms I've tried so far have been, the ui lags and battery takes a hit I assume as it's running harder to keep up
Bingley said:
Is it really much faster than stock 8.1? None of the roms I've tried so far have been, the ui lags and battery takes a hit I assume as it's running harder to keep up
Click to expand...
Click to collapse
That's because it's overclocked, and it generally feels way smoother like the stock Nougat ROM, there are some annoying bugs though, some camera apps can't access the camera, and the Hotspot doesn't work after installing some apps and rebooting, looks like it's not Magisk to blame, that doesn't happen in the stock though.
So I'm waiting until the OP replies or gives us an update hopefully.
I've tried the hotspot in the A600N port and it works properly! Why not here in this port? I think due to the presence of numerous Korean carrier options and maybe the Wi-Fi Sharing, when it's enabled, the hotspot doesn't work, even if disabled and rebooted. So you should remove these options, I guess?
I use SwiftKey beta as a side keyboard, testing the puppets, they are working in the stock ROM, but in both Pie ports, though I've allowed camera permission, the app can't load puppets, and that is not just present in SwiftKey, it is present also in some apps, it may be a missing Pie support, hopefully.
And thankfully, there are no camera modes, just front and back camera,
When I switch modes in this port, it force closes immediately,
and the Photo editor works properly in the A600N port, but not in this port, when I switch the filter it gives me a black screen instead
The only thing that annoys me is that the tablet interface of the A600N is not as great as this port, landscape mode is better here, because this port has tablet framework.
So, I wish this port gets more attention than it deserves, thank you Valera1978 for your great contributions! Hope you focus on this port, well more than you do with LineageOS!
Work on P580 ??
My solution: I just flashed a new kernel and it seems like it fixed my problem with the newest Messenger. The kernel I flashed is Thunderstorm. Now I don't have to use the old version anymore
OG POST:
Hello!
First post here, so hoping this is the right place to post.
On to the problem:
I rooted and installed a custom os for my Samsung S7 flat and everything seems to be working fine except for Facebook Messenger. The app won't open and just crashes before even actually opening without any clear error message (Messenger has stopped). Funny thing is that Facebook Messenger Lite works without any problem. I've Googled around a bit and seen that people have the same issue but none of the fixes have worked for me..
I am currently running Black Diamond os (Pie) but I have tried two other os' with the same result.. I have also tried to flash back to stock and then again to custom but that didn't work either.
Other things I've tried:
- Core only mode in Magisk
- Hide messenger in Magisk
- Delete .odex file in data/facebook.ocra folder
- Wipe dalvik, cache etc.
- Uninstall / reinstall messenger
I even tried to debug the log with adb. One thing caught my eye in the log which might explain the crash (I'm not an Android dev tho):
HTML:
AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.facebook.messenger.app.MessengerApplication: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.String.length()' on a null object reference
Anyone have any idea how to fix this? Thanks!
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
xezrunner said:
Happens to me as well on the Pixel XL Pie semi-GSI on the Redmi Note 5 Global (whyred).
It's actually a problem in the latest versions of the app, you can revert to an older version from APKMirror and it works just fine...
I haven't been able to figure out the problem either.
Click to expand...
Click to collapse
Ok thanks! Hopefully they'll fix it soon. I'm gonna try an older version for now and see if it'll work.
Edit: and it indeed did work. Disabled autoupdates so I'll be rolling with this for now!
After Flashing Rom, On first boot There was no option shown for Copy Data.. There was only an option related to crDroid cloud. After Rom boot there was also no option device set-up just like miui rom or aosp rom. Now everything working perfect and smooth in this ROM. But Now I need to my all messages which I had taken backup on my google drive.
Please help if any working method is exist to resolve my problem.
I think you installed the basic version of nikGapps. Try with a larger one, like the omni, in order to have Google/Pixel Setup Wizard.
This way the setup should ask you to restore a google backup.
lucamacc said:
I think you installed the basic version of nikGapps. Try with a larger one, like the omni, in order to have Google/Pixel Setup Wizard.
This way the setup should ask you to restore a google backup.
Click to expand...
Click to collapse
Still did not work for me
StephenVannevel said:
Still did not work for me
Click to expand...
Click to collapse
I faced the same problems when flashing NikGapps myself. Although there is a download page listing all that goes into a package, there is hardly enough description. I'm sharing the solution I found here.
I tried installing the omni and the full version of NikGapps. Both packages included the 'Google setup wizard' but the wizard only gets triggered into action when it either recognizes a new account being added or at first boot after a factory reset. I didn't take any chances and factory reset the phone since it had nothing on it yet.
Other apps that I wish I had installed before were Android Auto, Google assistant and their dependencies. You can't flash them later (they give an error) and they don't work properly if they're installed from the play store.