[ROM][7.1.2]Ressurection Remix 5.8.5[SGP712/771] - Xperia Z4 Tablet Android Development

Hi. This is my ROM #4.
It's stable as LOS 14.1.
Tested:
Camera;
USB-OTG;
NFC;
FMRadio;
etc.
Bugs:
- The same as LOS14;
- NFC-HCE(in LOS14.1 that doesn't work either);
- something I haven't found.
How to install:
1) use TWRP 3.5.0.
2) wipe all except internal storage
3) Flash the gapps , magisk.
4) You may also need to reformat sdcard.
5) If gaaps taking too much time for checking for updates, just reboot the tablet.
Change log:
20210316 - initial build.
20210317 - build for karin windy.
Last builds (mirror) are here.
I'm also very grateful to sabar_op for guiding me to build me ROMs in the right way.
If you want to get stock back use Emma than flashtool.
Sources
https://github.com/ResurrectionRemix
https://github.com/LineageOS/android_device_sony_karin_windy
https://github.com/LineageOS/android_device_sony_karin
https://github.com/LineageOS/android_device_sony_kitakami-common
https://github.com/LineageOS/android_kernel_sony_msm8994

The next ROMs I'm gonna build is dotos, viperos and crdroid. If no own wish to test it on karin windy I will build it only for on my own karin.

I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.

aaa646123 said:
I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.
Click to expand...
Click to collapse
Have you wiped system dalvik cashe user data? I don't use adb push.

alex009988 said:
Have you wiped system dalvik cashe user data? I don't use adb push.
Click to expand...
Click to collapse
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.

aaa646123 said:
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.
Click to expand...
Click to collapse
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.

alex009988 said:
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.
Click to expand...
Click to collapse
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.

aaa646123 said:
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.
Click to expand...
Click to collapse
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.

alex009988 said:
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.
Click to expand...
Click to collapse
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?

aaa646123 said:
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?
Click to expand...
Click to collapse
I saw your messages you have that problem since 2018.
Nougat ROMs are the most stable roms for our tablet, based on my experiance with karin at least. I can say that kernelpanics are possible everywhere where root is, both stock and custom. I also faced it on los14 but it happens so rarely, usually when many apps are lunched.
If you have that problem on los14, you'll have it with any my noutgat rom too as I use the same los kernel and edit device and vendor and other stuff if neccessary.
The problem is that I haven't found another sgp712 user who has 20 minute reboot problem on sgp712. I don't know maybe something in the sources are broken for your device or it's hardware problem.
So do you have that problem without gapps installed?
Do you have that problem without root?
Did you try different versions of magisk/supersu?
It's better you to try los15, maybe this one is without the issue for you.
If all above-listed you tried you should take adb log by pc with kernel panic. At least we can identify what cause the problem.

Related

[Q] Booting problem CM12

Hi to everyone!!
I have Moto E XT1021 and I installed CM12 (25-2-15 build and older ones) and it won't boot.
Before I installed to cm12, I installed CM11, but no luck with booting. Also I flashed stock firmware and then cm12 but it won't boot
Plus, I tried different customs kernel for cm12 but.....
I used TWRP 2.8.5.0 recovery to install CM12 and kernels.
Any idea what a heck happens here?
Thanks
It'd be better of you could tell us what exactly happens - it's impossible to do anything without details, @t-shock. Attach a logcat if possible.
tech_master said:
It'd be better of you could tell us what exactly happens - it's impossible to do anything without details, @t-shock. Attach a logcat if possible.
Click to expand...
Click to collapse
It stays at the cyanogenmod face. I can't provide a logcat
Okay, @t-shock, the kernel can provide a logcat in certain builds even in boot-loops. Anyways, wipe data, cache and dalvik-cache. If that didn't work, wipe the system partition. The ROM will automatically put the system files back in place (at least that's what that happens in my private builds).
tech_master said:
Okay, @t-shock, the kernel can provide a logcat in certain builds even in boot-loops. Anyways, wipe data, cache and dalvik-cache. If that didn't work, wipe the system partition. The ROM will automatically put the system files back in place (at least that's what that happens in my private builds).
Click to expand...
Click to collapse
I tried everything but nothing.

OPX OOS 3.1.1 twrp recovery + root

Flash this recovery on the community build: http://forum.xda-developers.com/devdb/project/dl/?id=20236
And then flash the super SU file via recovery:
https://www.androidfilehost.com/?fid=24591000424944601
Let me know if this works or you need any help ?
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
From other posts in other topics it seams that it's the only twrp version that installs OOS 3.1.1
Sent from my ONE E1001
trendchanger said:
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
yes this is working
Jab_ said:
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
Click to expand...
Click to collapse
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Exodusche said:
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Click to expand...
Click to collapse
Maybe the problem is not xposed itself, maybe the issue is related to an specific module. I'll try one by one tomorrow and see what happens, thank you!
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Exodusche said:
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Click to expand...
Click to collapse
I know what the problem was. My xposed zip was correct. As I thought, it was because of a module. "Android N-fy", in recents, I just had to uncheck quick switch and change no recent image and that was it. I don't know if that module is optimized for this oos especific build, because in settings of the phone, the module does not change as much as in lollipop oos. Thank you tho
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Worked fine. Thanks OP.
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
TarushS said:
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
Click to expand...
Click to collapse
Oh lol, glad this helped
StraightEdgeKid said:
Worked fine. Thanks OP.
Click to expand...
Click to collapse
Np?
Sachin7843 said:
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Click to expand...
Click to collapse
What exactly are you looking to do?
marwan2704 said:
What exactly are you looking to do?
Click to expand...
Click to collapse
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Sachin7843 said:
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Click to expand...
Click to collapse
Make sure you have both .zip files on your phone, clean flash 3.1.1 then boot it up. If you don't like it, you can go back to 2.2.2 via stock recovery anytime. You don't even need twrp unless you want to root, install Xposed or backup.
might be a bit off-topic but...
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
error23 said:
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
Click to expand...
Click to collapse
Sounds like you forgot to wipe data. Wipe system, data, cache and just flash 3.1.1. As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Exodusche said:
As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Click to expand...
Click to collapse
It's not the place, but I can confirm that it didn't work for me. I still have the drain from time to time.
And if I don't have the Wifi drain I have a service Google Play service drain (33% for today's charge for example...).
And sometimes, I even had the wifi drain with Wifi completly switched off...

Cant get gapps to work

Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
I normally flash a new rom in this order if the new rom is in my Download folder:
- TWRP Wipe advanced, tick System,Data,Cache.
-Back
-Install, go to sdcard/Download
-Select rom.zip
-after finish go back
-Select gapps64.zip
-after finish installing I press clean Dalvik and Cache
- Reboot system.
Wait a while and install as new device.
This should work.
With a normal update of a rom I simply install the update without wiping my system.
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
If you're using opengapps, they are having trouble booting on a fresh install on slim and LineageOS. Try an older build of slim or lineage, boot up and set up, then update to newest build.
Solution
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
I had the same issue with my NEXUS 9 wifi, but this solution mentioned here worked for me!
I am using:
lineage-14.1-20180920-nightly-flounder-signed
open_gapps-arm64-7.1-mini-20180923
Vendor Version: n9f27m
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
MOCKBA said:
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
Click to expand...
Click to collapse
It's a gapps issue not a ROM issue. Every now and then the setup wizard is weird in opengapps.

[Fixed] Encryption isn't working anymore

I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?

Can't Access Mail After Restoring Backup - Help

I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
madbat99 said:
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
Click to expand...
Click to collapse
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
deloj said:
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
Click to expand...
Click to collapse
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
madbat99 said:
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
Click to expand...
Click to collapse
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
deloj said:
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
Click to expand...
Click to collapse
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
madbat99 said:
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
Click to expand...
Click to collapse
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
deloj said:
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
Click to expand...
Click to collapse
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
madbat99 said:
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
Click to expand...
Click to collapse
Hi madbat,
I answered your question in this link. Please read it bro. Thanks man:
https://forum.xda-developers.com/ne...e-lineagos-15-1-to-14-1-t3934751#post79642010
.

Categories

Resources