I am using AEX 8.1 now,but now have many problem in Android 8.1,such as NFC mode(always in card reader mode,I can't use my phone as a NFC card but it can read them) and battery life(less than 7.1 RR 5.8.5), so I was flashing RR5.8.5 again. But when I open my phone ,it had a full-screen warning about ''the password you had already input is correct,but it's a pity that your data is broken,want to continue use your phone please resource factory setting(translate from Chinese I don't sure its the original text)'',and had a bottom ''resource factory setting'',but touch that bottom or go to Twrp recovery to wipe data and cache were no use,and some tutorials said that I must wipe the internal storage,but I have many data in there so I can't do. So it's something like encrypt method is different between 7.1 and 8.1 let me can't did it
No. This should not happen, but unfortunately you will have to format the internal memory if you want your device to work again.
Dark Stranger said:
No. This should not happen, but unfortunately you will have to format the internal memory if you want your device to work again.
Click to expand...
Click to collapse
Did you ever flash 7.1 ROMs when you were using 8.1 ROMs? Did it work?
You cannot keep internal data if it is encrypted in case you switch from 7.1 to 8.1, and from 8.1 to 7.1.
People had issues with encryption when they switched from 7.1 to 8.1. So you will have to back up your data.
You might also have to downgrade TWRP. At least I had to (trying to switch to xiaomi.eu ROM).
NaiveExcited said:
Did you ever flash 7.1 ROMs when you were using 8.1 ROMs? Did it work?
Click to expand...
Click to collapse
Yes. I only have an encryption problem when I go from aosp to miui or miui to aosp.
There are unfortunately no ROMs specifically for this device yet, but has anyone tried to use a generic treble ROM on this device?
Thanks in advance
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
gtaadicto92 said:
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
Click to expand...
Click to collapse
Hi Mate, I've been trying to flash a working GSI rom but had no success so far(have an SM-T830). In the past have built ROMs for Tab A 10.1 and flashed them many times with TWRP and Odin so I just cannot understand am I retarded to not being able to flash a working one or what? Have managed to put TWRP 3.3.0.0 and TWRP 3.3.0.1 on the device. Have tried my own arm64_aonly image first. Then an original AOSP one, then a Lineage OS version, at the moment I am just downloading Havoc. The result (apart from the havoc) was always the same. The flashing went through successfully and when I rebooted into system the very fist image came up and boot looped from there. I am always able to go back to TWRP and try another image or through odin can restore the factory image but none of the GSI images seem to be working. So, here is my question. As you managed to get a Lineage and Havoc working, can you tell by looking at it what am I doing wrong please:
1.: OEM unlock
2.: TWRP install with odin
3.: Boot straight into TWRP to prevent being overwritten
4.: TWRP: format data
5.: Flash system image (arm64_aonly)
From here have tried so many things like,
- booting straight into system
- booting back to recovery
- flashing the force_decryptor or how the hell is that called
- formatted data again as the decryptor suggests
The result was always the same, boot looped from the very first image. It seems like that the image is not getting flashed and even if TWRP says was flashed right it is just not there. I'm literaly pulling my hair as it was so easy and straight forward with the Tab A 10.1, but with this ….. thanks for your answer in advance
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
droidbot1337 said:
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
Click to expand...
Click to collapse
I used AOSP 9.0 and LineageOS 16 with OpenGApps Pico and both work but are very buggy.
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
motomotomotoG said:
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
Click to expand...
Click to collapse
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
droidbot1337 said:
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
Click to expand...
Click to collapse
Strange, How did you go about installing it?
last1youlove said:
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
Click to expand...
Click to collapse
I have not. I just really wanted an AOSP based ROM and i had gotten to the point where i had reflashed the stock firmware 3 times through ODIN because I messed up 1 thing or another. So once i got a functional ROM that worked great I just decided to stick to it. Also I don't think Android 10 has Xposed support yet, and i need that in order to enable Signature Spoofing for MicroG's FakeStore.
Greetings, I have flashed a GSI several months ago, but I can't seem to flash any GSI anymore. Every time I flash a GSI it gets stuck at the Lenovo logo upon rebooting. I have tried using official and unofficial TWRPs, official LOS 16 (treble), official AOSPExtended (also treble), but none of them worked. I have also used different guides: Flashed patches, wiped internal storage, formatted data, etc. but it still ends up getting stuck at the logo every time I boot.
TheEvilSkeleton said:
Greetings, I have flashed a GSI several months ago, but I can't seem to flash any GSI anymore. Every time I flash a GSI it gets stuck at the Lenovo logo upon rebooting. I have tried using official and unofficial TWRPs, official LOS 16 (treble), official AOSPExtended (also treble), but none of them worked. I have also used different guides: Flashed patches, wiped internal storage, formatted data, etc. but it still ends up getting stuck at the logo every time I boot.
Click to expand...
Click to collapse
I am wondering why you would install a GSI when specific ROMs are available for P2. However, you may be installing A/B GSI for P2 rather than A only GSI.
alirazaagha said:
I am wondering why you would install a GSI when specific ROMs are available for P2. However, you may be installing A/B GSI for P2 rather than A only GSI.
Click to expand...
Click to collapse
I've only used A only GSIs, but I've also tried A/B. I only do it for fun. I want to try out other ROMs that don't support the phone.
TheEvilSkeleton said:
I've only used A only GSIs, but I've also tried A/B. I only do it for fun. I want to try out other ROMs that don't support the phone.
Click to expand...
Click to collapse
I guess, your fun with GSIs is over now
My XT1795 is on stock 8.1 with unlocked BL, TWRP and magisk (I haven't installed any modules though). I am facing this weird issue since an year, the WiFi randomly keeps disconnecting and reconnecting automatically every 10 to 15 mins. I am sure that it has nothing to do with my WiFi router as I face the same issue when I am connected to mobile hotspots or any public or private network. I tried resetting the wifi and network settings, restored the device quite a few times, and also reflashed the stock rom but the problem still exists. The most recently that I reflashed the stock rom was a month ago, i didn't face any issue for the first 15 days but now it's back again.
Can someone please help me?
Try using a different kernel. But make sure that stock 8.1 is supported
Some random said:
Try using a different kernel. But make sure that stock 8.1 is supported
Click to expand...
Click to collapse
Yeah but I don't understand the reason behind this problem..
rizwan.mahai said:
Yeah but I don't understand the reason behind this problem..
Click to expand...
Click to collapse
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Some random said:
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Click to expand...
Click to collapse
View attachment alogcat.2020-03-30-11-09-20+0530.txt
Please have a look at the logcat, this morning while generating this log the wifi network ([email protected]) disconnected and reconnected atleast 3 times. Even after the reconnection, most of times I am not able to access the internet, I have enable airplane mode, then enable the wifi again or reboot the device. I am sure there is no problem with my router because, I face the same issue when ever I connect to any network be it a mobile hotspot or railway public network.
@lohanbarth @vaserbanix @kalyansundhar
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Some random said:
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
rizwan.mahai said:
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
Click to expand...
Click to collapse
The problem is still there on Lineage 15.1.
Lineage 15.1 Logcat
Some random said:
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
The wifi drops are more severe on lineage 15.1. Most of the times there's no internet access even while wifi is connected. Please have a look at the new logcat file.
View attachment logcat_lineage.04-01-2020_10-57-24.rar
I am being forced now to roll back to the stock rom from twrp backup.
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Some random said:
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Click to expand...
Click to collapse
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
rizwan.mahai said:
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
Click to expand...
Click to collapse
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Some random said:
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Click to expand...
Click to collapse
What is GSI ?
rizwan.mahai said:
What is GSI ?
Click to expand...
Click to collapse
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Some random said:
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Click to expand...
Click to collapse
Please try to run this command in terminal emulator, while wifi is on.
Code:
su
killall wpa_supplicant
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
rizwan.mahai said:
Please try to run this command in terminal emulator, while wifi is on.
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
Click to expand...
Click to collapse
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Some random said:
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Click to expand...
Click to collapse
Thanks. I'll give it a try.
rizwan.mahai said:
Thanks. I'll give it a try.
Click to expand...
Click to collapse
If the launcher for example is lagging, try adding this line
Sys.use.fifo_ui=1
Into build.prop and rebooting, maybe that makes it better
I was thinking about purchasing a Google Pixel XL due to the reasonable specs and good rom support. But I was just wondering if the device was treble supported before I decided to buy anything as it would help me out quite a bit. Also I am quite the enthusiast when it comes to custom roms and stuff.
If anyone has an answer i will be very grateful.
Thanks.
Sent from my Samsung Galaxy A20e (SM-A202F/DS)
Got this
Check attached photo. I have been playing with one of these for a bit. I loaded up TWRP followed with the latest Resurrection Remix and the phone is so fun to use.
mindlery said:
Check attached photo. I have been playing with one of these for a bit. I loaded up TWRP followed with the latest Resurrection Remix and the phone is so fun to use.
Click to expand...
Click to collapse
How did you flash it? I've been trying to flash phh and lineage but it won't boot at all. Tried in both TWRP and fastboot.
Sorry i was not clear about my message. I'm not using any GSI images. I am using https://forum.xda-developers.com/pixel-xl/development/unofficial-resurrectionremix-8-5-8-t4149771
I used to flash a lot of GSI's on another model and often i would need patches, custom kernel and some needed a clean flash of one first to get what i wanted after. I really like this ROM, but i have no problems going to stock if i screw up, which i will. So i'll go see if i can get a gsi on top of Rrmix. I'll be back.
I tried a couple gsi's and twrp gives a partition size error. (Too small).. What methods other than factory resetting and trying to install have you tried?
Pretty sure the version of TWRP used is specific. I tried RR with 3.4 and it was a mess. Now i'm using 3.2.3.1 and things are not perfect, but close enough for me.
mindlery said:
I tried a couple gsi's and twrp gives a partition size error. (Too small).. What methods other than factory resetting and trying to install have you tried?
Pretty sure the version of TWRP used is specific. I tried RR with 3.4 and it was a mess. Now i'm using 3.2.3.1 and things are not perfect, but close enough for me.
Click to expand...
Click to collapse
TWRP 3.4.0.0 is only good because it brings decryption support - there's also a fork of 3.3.0.0 by NZedPred on the regular Pixel forum (but the port is built for the XL too) which brings the best of both worlds, 3.4.0.0 decryption and 3.2.3.1 stability.
The small system partition is a known problem with our Pixels, there are repartitioning scripts ... but here be dragons.