[UNOFFICIAL][ROM] crDroid 5.12 for Galaxy Tab E [SM-T560NU][Pie] - Samsung Galaxy Tab E ROMs, Kernels, Recoveries, &

I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.

I tried to install the ROM to my SM-T560NU, it boots with no issues. It's very laggy to use, so I mess around with crDroid settings and I changed the scrolling cache setting (Settings->crDroid Settings->User Interface->Animations->Scrolling Cache) from Default enable to Default disable, it fixed the laggy issue.
I also tried to flash Vince2678's overclock kernel and it boots with no issues.

This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.

This rom is for Android 7?

zeovani said:
This rom is for Android 7?
Click to expand...
Click to collapse
>Android Pie
Sorry bud this an android 9 rom lol

edwardnizz said:
This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Click to expand...
Click to collapse
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
edwardnizz said:
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.
Click to expand...
Click to collapse
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.

Tickbaby said:
I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.
Click to expand...
Click to collapse
download link for the rom is broken :/

Fruse said:
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.
Click to expand...
Click to collapse
I just installed liightningfast. It turns out, I forgot to wipe data the first time i tried. Thanks a bunch. Now i have a few choices! Dude your the BOMB!!

One Questions Dev's and Fellow members Can this rom be flashed on SM T561 too ?

running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys

malfuncion said:
running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys
Click to expand...
Click to collapse
i used super su to root

I have found a bug. When using stock screen recorder with puting only record internal audio, if u have headphones connected it freaks out. Plz don't mind the video, I clicked on it for representation of the issue.

Related

Magisk on Verizon Note 4

Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Try going to the Samsung Note 4 international section.. I just flashed a Note 7 port to my wife's phone and it rocks..
Could you possibly link to which one? Is it this one? Xerrum525 N7 FullFramework PortedRom for SM-N910C / SM-N910H
Also did you use magisk with it to use pokemon go?
Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I'd like to know too.
What I did was install PaulPizz. Once it finished I deleted the SuperSU folder via TWRP.
It booted up fine, I still had the SU app in my drawer, I did full unroot via SU. I then flashed the uninstall for Xposed and now I can play pogo.
I Haven't been able to get Magisk to work... I get unable to detect boot image. I'm unrooted for now on PaulPizz and can play PoGo 0.37
Tricil said:
Hello everyone,
As I'm sure everyone knows, Niantic has blocked rooted phones from playing with the most current update 0.37. I'm wondering if anyone has been able to find a ROM that will work on our phones and we can install magisk to be able to play with the latest update. If not, is there any other possible solution to play with the use of magisk or without giving up root completely. I'm currently running PaulPizz and have not tried any of the possible methods I have found from fear of losing root permanently. I'm open to any suggestions or ideas.
Thank you.
Click to expand...
Click to collapse
I downloaded an older version of the app from http://www.apkmirror.com/apk/niantic-inc/pokemon-go/.
I uninstalled the new version. Reinstalled the older. Ran fine. I've heard they'll force an update sooner or later but its good for now.
I also made sure to turn off auto app updated in settings.
I did find a solution using PaulPizz and magisk. It relatively follows most other tutorials. Plus I found a way to toggle magisk with tasker, if anyone is interested. I'll post a step by step tomorrow or possibly later tonight. Sorry to make everyone wait.
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
I still get unable to detect boot image :/
reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.
Tricil said:
When are you getting that, when you flash the zip or install the apk? I'm guessing that's when you flash the included Magisk_6.zip. You are rooted using the retail to dev on an N910V model? I would maybe backup your current system and restore from before you unrooted and try again possibly.
Click to expand...
Click to collapse
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
After clean install (wipe data, cache, system)
It says after mounting system
Mounting /system(ro), /cache, data
Device platform arm
unable to detect boot image
error 1
idk what to do
reggaeton1991 said:
I still get unable to detect boot image :/
Click to expand...
Click to collapse
reggaeton1991 said:
Yes rooted from retaill to dev on a N910V and yea, I get that when flashing Magisk_6.zip.
I'm factory resetting the rom. Going to ensure I have root from PaulPizz. and then try again. Thank you.
Click to expand...
Click to collapse
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.
Tricil said:
Also, this is my setup, if it helps at all. Please let me know if any of this helps, or if you find another way that works for you. Thank you.
Click to expand...
Click to collapse
Thanks again, it looks like the only difference was that I was on CPF3.r-2.
I tried going back to CPD1 and still no luck.
I appreciate you letting me know.
I used the Kyubi rom and uninstalled root with supersu and installed all of the magisk stuff and it works like a charm. All of the xposed modules work good too with the system less xposed. It takes a while to boot up after flashing magisk and clearing cache but worth it. The buddy system is pretty cool lol
Anyone else only able to MAYBE play on WiFi?
Tricil said:
So this is how I got it work with PaulPizz ROM for Verizon Note 4 retail converted to Dev edition.
I take no credit for the creation of the files required for this install, but I kind of muttled my way through this installation and got the files from different posts so credit is to go to the creators of these files, I am just redistributing. If someone feels the need to take credit for these please feel free to let me know.
Make sure to download all apks and zips before and place on sd card before hand to save time. I have also included the uninstaller for magisk version of xposed if you would like, do not use this one during the installation of magisk to remove xposed though.
Only flash xposed and install apk if you still want xposed, if not you can skip those files.
1. Do a full backup of phone using TWRP
2. Go into SuperSU settings and do full unroot
3. Reboot into recovery and mount system partion
4. Go to advanced in recovery and select File explorer
5. Navigate to system and delete .supersu file
6. Flash xposed-uninstaller-20150831-arm.zip and reboot system
7. Install pokemon go 0.37 and make sure it works at this point
8. Reboot into recovery again and flash Magisk-v6.zip, 1473968610260_phh-superuser-17-magisk.zip, and 1473980489208_xposed-v86.5-arm-alt-sdk23-topjohnwu.zip
9. Clear dalvik and cache and reboot system
10. After apps optimize install Magisk manager and Xposed Installer
11. Reboot and enjoy playing the new update. Just use Magisk Manager to turn root on/off at will before or after playing.
I'm going to create the tasker profile tomorrow and post instruction on that once completed to automatically activate Magisk when opening pokemon go.
If there are any questions, I will do my best to answer.
Click to expand...
Click to collapse
Well I have magisk installed but I dont know if the xposed went through entirely it says it flashed ok but according to the installer I don't have xposed installed? What's going on did I do something wrong
Did you remove the old xposed app after the flag and install the new xposed apk also? I think mine did the same, because I forgot to also install the xposed app after flashing the systemless xposed framework.
I was able to full unroot, delete the super su file in twrp. when I flash the Xposed uninstaller it removes the framework but leaves the APk in a form that I can't delete.
If I flash magisk and all the other stuff it goes through fine, but when I try to toggle root off in magisk it turns itself back on within a few seconds. I'm assuming this is because i didn't get Xposed all the way off?
Any ideas? Thanks in advance for the help.
Magisk will refuse to unroot while xposed is still there in the system form. Even a piece of it.
Well now I got Xposed off using tibu before I unroot. Everything installed, systemless Xposed registered as being active, but when I try to toggle root in magisk I get the same thing with it turning itself back on. If I try to request root privileges from an app I am told i have no root.
Ideas?

[STOCK][7.1.1] Nextbit Robin - ether - Flashable Stock ROM [N108]

Introduction
This is a flashable zip of the latest Stock ROM for the Nextbit Robin. The boot.img is modified with removed DM-Verity and forceencryption.
It contains no recovery.img so you can continue using TWRP.
Installation
Clean flash:
- Download latest build
- Boot TWRP
- Wipe system, data, cache, and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Dirty flash:
- Download latest build
- Boot TWRP
- Wipe cache and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Download
ROM: https://www.androidfilehost.com/?fid=673368273298967045
XDA:DevDB Information
Nextbit Robin - ether - Flashable Stock ROM, ROM for the Nextbit Robin
Contributors
crian
Source Code: https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
ROM OS Version: 7.x Nougat
Based On: Stock
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-25
Awesome thanks!
I've tried to use Substratum with this ROM but it won't work. Anyone successful?
jir591 said:
I've tried to use Substratum with this ROM but it won't work. Anyone successful?
Click to expand...
Click to collapse
It's stock and not compatible with oms.
A Mega mirror if possible? Thanks. AFH is taking too long.
I've uploaded it to MEGA
Let me know if you want me to delete the link
Hi is this stock the same and included also the 100 go memory cloud ?
Mchasard said:
Hi is this stock the same and included also the 100 go memory cloud ?
Click to expand...
Click to collapse
Yes
Sent from my Robin using Tapatalk
kwattro76 said:
Yes
Click to expand...
Click to collapse
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...
Mchasard said:
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...
Click to expand...
Click to collapse
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Sent from my Robin using Tapatalk
kwattro76 said:
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Click to expand...
Click to collapse
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?
Mchasard said:
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?
Click to expand...
Click to collapse
Just flash your favorite su app and delete some system apps.
This is just a flashable zip of the stock rom. So there are the same gapps as the factory image got.
Anyone try that unofficial xposed on this rom?
Sent from my Robin using Tapatalk
Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?
bilged said:
Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?
Click to expand...
Click to collapse
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.
/root said:
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.
Click to expand...
Click to collapse
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.
bilged said:
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.
Click to expand...
Click to collapse
I am currently using LOS but was on Omni most of the time as Omni was really stable and updated that time. But Omni started eating a lot of battery and stopped providing updates, so I switched to LOS as soon as LOS 15 was released for Robin. GPS worked fine for me on Omni too, it sometimes had problem locking the location but navigation on Google Maps worked as it should. Waze I used a few times it didn't crash that time. But not a regular Waze user.
Did your clean flash the ROM?
Can't tell you about NFC as I sadly have no reason to use it.
By the way, how is your battery? Mine is degrading bad. My SOT has gone from 3-4hrs to 2-2.5hrs. over the 2+ years of owning this device. Not only that, below 30-40% it would shut down on running any heavy app like Camera or Maps or Music Streaming. Battery is degrading badly.

Not able to install any custom ROM in OnePlus 5T

Hello Guys,
I need help regarding the issue that I'm facing. What happens is ROM get installed properly without any error but not boots up. It get stuck at boot animation screen. I tried lots of ROMs including DOT OS, C droid, AICP, TOXYC OS. Facing the same issue to all of the ROMs. I followed the below steps to install.
1. Download the ROM file
2. Download the GApps.
3. Booted into TWRP Recovery Mode.
4. Backup done (optional)
5. Wipe all the 4 partitions except Internal Storage.
6. Then install the ROM file and followed by GApps
7. Installation successful for both ROM & GApps.
8. Reboot.
I tried installing the ROM only but result was same.
I'm currently running on Oxygen OS Open Beta 10.
PLEASE HELP. THANKS IN ADVANCE.
Which TWRP do you use? Personally, I recommend this one by codeworkx: https://sourceforge.net/projects/ch....1-0-20180309-codeworkx-dumpling.img/download
Some roms require you to be decrypted; others don't. Most roms require the latest firmware (5.1.3) to be flashed before the rom, gapps, etc. Read the installation instructions carefully. Use the recommended firmware and gapps package linked to the rom. Before you start flashing roms, you should wipe your phone in fastboot mode: fastboot format userdata. This will wipe your phone clean; all your data will be gone. So, backup all your data to your PC before proceeding. After format, reboot directly to TWRP and move your firmware, rom, gapps, etc. to internal storage; follow the flash order and procedures exactly as outlined for the rom you want to try.
I tried installing latest TWRP (3.2.1-2) for my OnePlus 5T but no luck. Please suggest.
KDPalekar said:
I tried installing latest TWRP (3.2.1-2) for my OnePlus 5T but no luck. Please suggest.
Click to expand...
Click to collapse
The link to a working TWRP is in the post above; it's not the latest or official TWRP, but it works. Also, please read through this thread if you haven't already: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592.
Did you try to format data (after wiping the partitions) ?
bud7dha said:
The link to a working TWRP is in the post above; it's not the latest or official TWRP, but it works. Also, please read through this thread if you haven't already: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592.
Click to expand...
Click to collapse
Read the whole instructions and installed it but no luck .
Zark0s said:
Did you try to format data (after wiping the partitions) ?
Click to expand...
Click to collapse
sorry.. i didn't get u.
KDPalekar said:
sorry.. i didn't get u.
Click to expand...
Click to collapse
In twrp, when you go in the wipe tab, there is a "format data" button. It will wipe the data and internal storage partitions and remove encryption. But don't worry, depending of the ROM you flash it will encrypt again.
Zark0s said:
In twrp, when you go in the wipe tab, there is a "format data" button. It will wipe the data partition and remove encryption. But don't worry, depending of the ROM you flash it will encrypt again.
Click to expand...
Click to collapse
so do i need to do that as well?
KDPalekar said:
so do i need to do that as well?
Click to expand...
Click to collapse
I format data everytime I do a clean flash lol, so yeah just give a try and let us know if it works ^^
Hi,
It worked. I format the data and install the clean flash. Thanks a lot. One more thing can u please suggest custom ROM with ANDROID P notification panel.
KDPalekar said:
Hi,
It worked. I format the data and install the clean flash. Thanks a lot. One more thing can u please suggest custom ROM with ANDROID P notification panel.
Click to expand...
Click to collapse
Idk if a custom rom exists with that feature but there is a xposed module which does that and works on any custom rom (aosp 8.1 based at least) : https://forum.xda-developers.com/xposed/modules/xposed-android-p-ify-features-t3764556
Zark0s said:
Idk if a custom rom exists with that feature but there is a xposed module which does that and works on any custom rom (aosp 8.1 based at least) : https://forum.xda-developers.com/xposed/modules/xposed-android-p-ify-features-t3764556
Click to expand...
Click to collapse
I installed the Lineage OS, rooted, installed the xposed module, installed the android P fy module but still I'm not getting the exact look like android p notification panel. Can you suggest me ROM that works fine with Android P-fy module to get the exact Android p notification panel.
Please find the attachment. This is what I'm getting with Lineage OS.
KDPalekar said:
I installed the Lineage OS, rooted, installed the xposed module, installed the android P fy module but still I'm not getting the exact look like android p notification panel. Can you suggest me ROM that works fine with Android P-fy module to get the exact Android p notification panel.
Please find the attachment. This is what I'm getting with Lineage OS.
Click to expand...
Click to collapse
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Zark0s said:
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Click to expand...
Click to collapse
I tried AOSP Extended before a week ago. Everything was working fine except headphone Jack. Sound was not coming in my earphones. Sound from speaker grill was coming, even I tried with connecting to Bluetooth speaker, that's also working fine. The only issue I had with that headphone Jack.
Please suggest if you have any solution for that then I'll surely try it again.
Thanks
Zark0s said:
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Click to expand...
Click to collapse
Oh. How unlucky I'm. I just checked the headphone Jack with this ROM. Here also headphone Jack is not working. This is very unlucky. Do have any solution for this?
KDPalekar said:
Oh. How unlucky I'm. I just checked the headphone Jack with this ROM. Here also headphone Jack is not working. This is very unlucky. Do have any solution for this?
Click to expand...
Click to collapse
I think you didn't flash the latest firmware available (5.1.3), which you can find here :
https://forum.xda-developers.com/showthread.php?t=3728665
Zark0s said:
I think you didn't flash the latest firmware available (5.1.3), which you can find here :
https://forum.xda-developers.com/showthread.php?t=3728665
Click to expand...
Click to collapse
Thanks a lot Buddy. Flashed the latest firmware and now headphone Jack is live more. Thank you do much Buddy.

[GUIDE] How to flash Android 9 Pie (PixelExperience, Havoc OS etc.)

Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):
Don't need to flash p lag fix, volte fix and other stuff?
Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.
Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help
moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.
HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.
Is hotspot working in PIE GSI?
dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok
expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on

LG V500 Tablet - Nougat Upgrade Problem (Lineage File)

First off I'm no tech guru, so please provide as much detail as possible if you can so I can follow along... TIA!!
I am trying to upgrade my old LG V500 from KitKat 4.4.2 to Nougat.
I followed details in a video, by downloading the necessary files....
-Latest TWRP App (the APK)
https://dl.twrp.me/twrpapp/
-Latest TWRP Recovery for the v500
https://dl.twrp.me/v500/
-Stump Root
https://forum.xda-developers.com/lg-g...
-LineageOS build for the v500
lineage-14.1-20180909-nightly-v500-signed.zip
I hit Install and selected the above Lineage file and swiped to confirm the flash in TWRP.
What I got was this error...
https://drive.google.com/file/d/12ZY3y9pNaRJxqWHuCJSEmyl5Xmn3CtXq/view?usp=sharing
Now I am confused on what to do. I don't want to lose my old 4.4.2 build since this upgrade didn't work.
I could really use some serious help on what steps I should take. My preference would be to upgrade this tablet, but if I have to revert back then so be it (but don't even know how to do that). Wondering if I did something wrong or this .zip file is just outdated, not sure what else 'Error 7' refers to, other than Error installing .zip file.
Any help would be appreciated!
stargreen said:
Wondering if I did something wrong or this .zip file is just outdated, not sure what else 'Error 7' refers to, other than Error installing .zip file.
Click to expand...
Click to collapse
Most likely that is the case, rom file is two years older than the recovery. You can either:
1. Install newer version of Lineage with that recovery: https://www.los-legacy.de/v500
2. Flash older version of TWRP first and then install that older Lineage, or some other rom (for example I have TWRP version 3.3.1-0 and Resurrection Remix N 5.8.5 FINAL which works flawlessly https://forum.xda-developers.com/lg-g-pad-83/development/testing-resurrection-remix-n-5-8-3-oms-t3601456)
Thx Indie Zex for the options.
My dilemma now is, how would I install this new Lineage with the recovery file, since I am still in TWRP?
Need help on what steps I need to follow to either exit out of TWRP to get the newer Lineage file.
I assume you can't load anything from the link you provided while I'm in TWRP....am I correct?
If I exit out of TWRP now, will I completely lose my original 4.4.2 (KitKat) build?
TY
stargreen said:
My dilemma now is, how would I install this new Lineage with the recovery file, since I am still in TWRP?
TY
Click to expand...
Click to collapse
If I understand correctly, you are still in TWRP on your tablet right? If you performed full wipe of Dalvik Cache/Cache/System/Data (like you always should do before installing a new rom) then you can kiss your KitKat goodbye forever! If for some reason you didn't wipe anything, then in the main menu of TWRP you can select Reboot, then System and your tablet should (luckily) boot into KitKat. But lets say your tablet is wiped and you now have to install new rom:
1. On your computer download https://www.los-legacy.de/v500 and open gapps https://opengapps.org/ (ARM, 7.1, pico)
2. Connect your tablet with computer via usb cable and copy both rom and gapps to internal storage (Windows should see your tablet as a mass storage device no problem even if you're in TWRP and you have proper LG drivers installed)
3. Now on your tablet: from main menu go into Wipe, then Advanced Wipe, then on Select Partitions to Wipe page tick Dalvik Cache/Cache/System/Data and Swipe to Wipe
4. Back to main menu and select Install, then find rom from the internal storage, then Add more zips and find gapps and finally Swipe to confirm Flash
5. Once that's finished press Wipe Dalvik Cache/Cache and then Reboot
That should hopefully be it.
TY Indie Zex,
You understood correctly, and I did a full wipe of Dalvik Cache/Cache/System/Data. I was afraid you would say I lost my old 4.4.2., but I really just wanted some insurance to go back if things got messed up, which they did!
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'?
or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q.
I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
TY you again for being patient with a newbie
stargreen said:
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Click to expand...
Click to collapse
Yes, the latest one.
stargreen said:
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'? or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q. I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
Click to expand...
Click to collapse
You always flash custom roms the same way in TWRP, you can not just update unfortunately. The next thing to pay attention to is to download correct version of gapps for Oreo or Pie roms (there are no Q roms for our tablet). You have probably seen this tutorial here for Pie https://forum.xda-developers.com/lg-g-pad-83/general/guide-tutorial-howto-lg-gpad-8-3-v500-t3967069. I have tried it as well as https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076 but they both have broken camera unfortunately. Everything else is basically fine, with Oreo having better performance.
stargreen said:
TY Indie Zex,
You understood correctly, and I did a full wipe of Dalvik Cache/Cache/System/Data. I was afraid you would say I lost my old 4.4.2., but I really just wanted some insurance to go back if things got messed up, which they did!
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'?
or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q.
I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
TY you again for being patient with a newbie
Click to expand...
Click to collapse
Rhetorical questions.
What's wrong with pressing the THANKS icon under Indie Zex's answers instead of writing "TY"?
.
Besides, if you were advised to install a very stable Nougat, why don't you try it first, before thinking about P and Q?
.
Indie Zex said:
Yes, the latest one.
You always flash custom roms the same way in TWRP, you can not just update unfortunately. The next thing to pay attention to is to download correct version of gapps for Oreo or Pie roms (there are no Q roms for our tablet).
TY.
You have probably seen this tutorial here for Pie https://forum.xda-developers.com/lg-g-pad-83/general/guide-tutorial-howto-lg-gpad-8-3-v500-t3967069. I have tried it as well as https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076 but they both have broken camera unfortunately. Everything else is basically fine, with Oreo having better performance.
Click to expand...
Click to collapse
Yes, I did see the Pie tutorial and did read through it, the non-working camera was certainly something I did not want. Good to know you have Oreo running on yours, and better performance.
So do you suggest I load Oreo vs Nougat?
For Oreo would I select v8 or v8.1? and what variant?
I found this info...I was thinking of Micro or Mini, thoughts? Can the V500 handle the memory requirements for these?
Variant:
Aroma: Graphical installer of the super package while in recovery menu, it allows user to select which applications to install.
Super: Includes all Google Apps that were ever shipped on a Google device.
Stock: Recommended package that contains all Google Apps that come standard on latest Nexus/Pixel phone.
Full : Very similar to Stock version.
Mini : Smaller set of popular Google Apps with extra functionality.
Micro: Limited set of Google Apps with Gmail, Calendar Google Now with extra functionality.
Nano : Minimal installation with extra functionality.
Pico : Minimum with Google Play functionality. (Each package varies with file sizes and included Google Apps)
TY again, much appreciated!
ze7zez said:
Rhetorical questions.
What's wrong with pressing the THANKS icon under Indie Zex's answers instead of writing "TY"?
Click to expand...
Click to collapse
Haha calm down ze7zez, he probably doesn't even know how . We've all been young and innocent once...
Indie Zex said:
Haha calm down ze7zez, he probably doesn't even know how . We've all been young and innocent once...
Click to expand...
Click to collapse
You right Indie Zex, Thx for the patience...hit the Thx icons for you!
Can you just take a few secs to answer my last few questions in last post, please?
stargreen said:
Good to know you have Oreo running on yours, and better performance.
Click to expand...
Click to collapse
No, as a matter of fact I have Resurrection Remix N 5.8.5 FINAL installed on TWRP version 3.3.1-0.
stargreen said:
For Oreo would I select v8 or v8.1? and what variant?
Click to expand...
Click to collapse
There is only one version of Oreo for our tablet: https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076. I have tried it, it runs nicely but camera DOES NOT work just like in Pie version (which is a little bit choppy for my taste).
stargreen said:
I found this info...I was thinking of Micro or Mini, thoughts? Can the V500 handle the memory requirements for these?
Click to expand...
Click to collapse
I wouldn't go above micro, 2GB of ram is a little bit tight. But hey, if you like Google so much try and see how it runs.
stargreen said:
So do you suggest I load Oreo vs Nougat?
Click to expand...
Click to collapse
Since you already have latest TWRP version installed, I suggest you go with latest lineage rom (2020-09-05) with gapps of your choice. For Oreo and other older roms you need to flash older TWRP version, such as above mentioned 3.3.1-0 (and please do not ask how ).
And finally I wanna say this: don't worry if you mess something up, you already have and you certainly will again :laugh:. There is a wonderful world of flashing roms (and wasting your precious time ) ahead of you, so go boldly into the unknown! :fingers-crossed:
Indie Zex said:
No, as a matter of fact I have Resurrection Remix N 5.8.5 FINAL installed on TWRP version 3.3.1-0.
There is only one version of Oreo for our tablet: https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076. I have tried it, it runs nicely but camera DOES NOT work just like in Pie version (which is a little bit choppy for my taste).
I wouldn't go above micro, 2GB of ram is a little bit tight. But hey, if you like Google so much try and see how it runs.
Since you already have latest TWRP version installed, I suggest you go with latest lineage rom (2020-09-05) with gapps of your choice. For Oreo and other older roms you need to flash older TWRP version, such as above mentioned 3.3.1-0 (and please do not ask how ).
And finally I wanna say this: don't worry if you mess something up, you already have and you certainly will again :laugh:. There is a wonderful world of flashing roms (and wasting your precious time ) ahead of you, so go boldly into the unknown! :fingers-crossed:
Click to expand...
Click to collapse
I guess I misunderstood you earlier on which rom you where using, thought it was Oreo. Does the camera function with this Resurrection Remix N 5.8.5 FINAL? Based on the Variant list I posted, how would you categorize this rom?
I am intrigued, I thank you for the words of encouragement, just a bit intimidating this world, but I am willing to try!
stargreen said:
I guess I misunderstood you earlier on which rom you where using, thought it was Oreo. Does the camera function with this Resurrection Remix N 5.8.5 FINAL? Based on the Variant list I posted, how would you categorize this rom?
Click to expand...
Click to collapse
Camera (and everything else) works on all Nougat (and earlier) roms. Differences between them come down to customization: for example Resurrection Remix N 5.8.5 FINAL and crDroid Android 4.7 offer more customization options compared to LineageOs, but are two years old. Latest Lineage, on the other hand, has literally last month security patches. And I suggest you install them all, one at a time
Indie Zex said:
Camera (and everything else) works on all Nougat (and earlier) roms. Differences between them come down to customization: for example Resurrection Remix N 5.8.5 FINAL and crDroid Android 4.7 offer more customization options compared to LineageOs, but are two years old. Latest Lineage, on the other hand, has literally last month security patches. And I suggest you install them all, one at a time
Click to expand...
Click to collapse
I followed your instructions...at least I'm pretty sure I did. lol
I got an install Error 20, it says to download the correct version for my rom 6.0.1
I went with the GAPPS file (ARM, 7.1, micro)
Does this mean I cannot use the micro variant?
stargreen said:
I followed your instructions...at least I'm pretty sure I did. lol
I got an install Error 20, it says to download the correct version for my rom 6.0.1
I went with the GAPPS file (ARM, 7.1, micro)
Does this mean I can use the micro variant?
Click to expand...
Click to collapse
Hm, the error suggests that you have 6.0.1 rom which you tried to flash with 7.1 gapps. Just in case, download older version twrp-3.3.1-0-v500.img and flash it in TWRP:
1. Copy twrp-3.3.1-0-v500.img from computer to internal storage of a tablet
2. In main menu of TWRP select Install, then Install Image
3. Choose twrp-3.3.1-0-v500.img and flash it (IMPORTANT: do not reboot right away!)
4. Go back to main menu then press Reboot and select Recovery
5. You will boot to recovery again, now the older version
6. Now flash rom ONLY (whichever Nougat variant you want) with standard described procedure (with wipe and everything) and reboot
7. Once you are in system, check it out and come back later into TWRP to install correct gapps (yes, you can use micro)
---------- Post added at 12:54 AM ---------- Previous post was at 12:23 AM ----------
And let me know did you make it in about 8 hours, it's late here so I have to sleep
Indie Zex said:
Hm, the error suggests that you have 6.0.1 rom which you tried to flash with 7.1 gapps. Just in case, download older version twrp-3.3.1-0-v500.img and flash it in TWRP:
1. Copy twrp-3.3.1-0-v500.img from computer to internal storage of a tablet
2. In main menu of TWRP select Install, then Install Image
3. Choose twrp-3.3.1-0-v500.img and flash it (IMPORTANT: do not reboot right away!)
4. Go back to main menu then press Reboot and select Recovery
5. You will boot to recovery again, now the older version
6. Now flash rom ONLY (whichever Nougat variant you want) with standard described procedure (with wipe and everything) and reboot
7. Once you are in system, check it out and come back later into TWRP to install correct gapps (yes, you can use micro)
---------- Post added at 12:54 AM ---------- Previous post was at 12:23 AM ----------
And let me know did you make it in about 8 hours, it's late here so I have to sleep
Click to expand...
Click to collapse
Hi Indie Zex,
I read your above instructions, but somewhat confused.
I looked for twrp-3.3.1-0-v500.img but can't seem to find it, has the file name changed?
I went to the link page you provided (below) for your Resurrection Remix build, and the Rom available there was RR-N-v5.8.5-20171001-v500-Final.zip
2. Flash older version of TWRP first and then install that older Lineage, or some other rom (for example I have TWRP version 3.3.1-0 and Resurrection Remix N 5.8.5 FINAL which works flawlessly https://forum.xda-developers.com/lg-...3-oms-t3601456)
stargreen said:
I looked for twrp-3.3.1-0-v500.img but can't seem to find it, has the file name changed?
Click to expand...
Click to collapse
Download twrp-3.3.1-0-v500.img from official page here https://dl.twrp.me/v500/
stargreen said:
I went to the link page you provided (below) for your Resurrection Remix build, and the Rom available there was RR-N-v5.8.5-20171001-v500-Final.zip
Click to expand...
Click to collapse
Yep, that is the "newest" one which I have installed. If download link is broken, you can get rom from here https://androidfilehost.com/?fid=4349826312261778561
Indie Zex said:
Download twrp-3.3.1-0-v500.img from official page here https://dl.twrp.me/v500/
Yep, that is the "newest" one which I have installed. If download link is broken, you can get rom from here https://androidfilehost.com/?fid=4349826312261778561
Click to expand...
Click to collapse
Before I try to flash my tablet with twrp-3.3.1-0-v500.img, what do I need to do with the lineage-14.1-20200905-UNOFFICIAL-v500.zip that I ran and is still in Internal storage. Can I just delete via my computer, or do I need to remove it thru TWRP?
stargreen said:
Before I try to flash my tablet with twrp-3.3.1-0-v500.img, what do I need to do with the lineage-14.1-20200905-UNOFFICIAL-v500.zip that I ran and is still in Internal storage. Can I just delete via my computer, or do I need to remove it thru TWRP?
Click to expand...
Click to collapse
If you don't need it anymore, you can delete it via computer. It doesn't really matter when you install .img file. When you select install image in main menu of TWRP you won't see any other files except for .img ones. Just make sure to reboot to recovery instead of reboot to system to continue with installing rom.
Indie Zex said:
If you don't need it anymore, you can delete it via computer. It doesn't really matter when you install .img file. When you select install image in main menu of TWRP you won't see any other files except for .img ones. Just make sure to reboot to recovery instead of reboot to system to continue with installing rom.
Click to expand...
Click to collapse
Great TY.
So from yesterday when my install failed, I just need some direction on what do I do to get out of this screen, please.
I have the option button to Wipe Cache/Dalvik or Reboot System.
Do I need to hit the Wipe button to remove the lineage-14.1-20200905-UNOFFICIAL-v500.zip? Or Wipe anything else?
Or do I just go back to the main menu for TWRP and install the twrp-3.3.1-0-v500.img and follow the rest of your instructions?
TY again.

Categories

Resources