Hi,
I'd like to have root and xposed installed and keep the encryption enabled, I don't care about backing up the data partition or creating nandroid backups, so having a custom recovery is not important.
I've followed these steps:
- Flashed stock Oreo firmware using Odin 3.13
- Flashed TWRP 3.2.1.1, then boot to it.
- Flashed no-verity-opt-encrypt-6.0 and Magisk v16.0 from TWRP then rebooted.
but I still get Verification failed.
I've also tried to patch the boot image using Magisk Manager and flash it with Odin, but got the same results.
Can anyone tell me what else do I need to do?
Phone is Exynos (SM-G935F) edition.
Thanks.
Any luck
Hi
Just wondering if you had any luck with this?
Im actually trying to get the OREO stock ROM to allow internal storage to be accessed in TWRP so I can do a Nandroid backup but I can never seem to get it to work.
Everytime I come back it cant mount data.
Ive tried flashing ROM then TWRP immediately after.
Boot into TWRP install Magisk and no verity then reboot to system.
Once i come back data is gone. Are you able to access data in Recovery?
This custom ROM is as close to stock as possible less the unnecessary bloat. As far as I am aware, this is the only Oreo ROM that you can encrypt. Make sure you follow the instructions and then you'll have an encrypted rooted phone running Oreo:
[ROM][G935F/FD][ALEXNDR] * U2ERF4 (Oreo) * DevBase v5.8 * Encryption support [Jul-03]
https://forum.xda-developers.com/s7-edge/development/rom-dqd1-devbase-v4-1-multi-csc-safe-t3591647
Related
I"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.
You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.
3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk
Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?
Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.
if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.
Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad
sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.
yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?
If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.
I tried flashing Lineage, but I can't install Oxygen
Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Joe199799 said:
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Click to expand...
Click to collapse
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
farhan20 said:
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
Click to expand...
Click to collapse
I flashed OOS 9.0.12 yesterday because I switched ROMS with 9.0.11 and it resulted in a msm flash, turns out switching roms from 9.0.11 is a bad idea. But after updating I flashed havoc OS and everything is all good. We appreciate the answer I understand it a little better now
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good.
Click to expand...
Click to collapse
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Nsane457 said:
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Click to expand...
Click to collapse
That was a very well written and insightful answer thank you. The way you wrote makes everything much easier to understand
I think with the new TWRP recovery flashing is about to be less of a d**k. TWRP 3.3.0-0
Hello, I have a T-Mobile 6T which thanks to the XDA thread about bypassing T-mobile, is running the international firmware so I didn't have to kiss their butt trying to unlock the bootloader. Yesterday I decided to try the Resurrection Remix rom since it is unclear whether the Lineage 16 rom supports the in-display fingerprint reader, and I am too busy at work and too lazy to read the entire thread to see if it does.
I followed the instructions and updated my OxyOS to the latest .15 release via TWRP which I also updated to the latest version via OTG using a USB drive because I was unable to unencrypt using the older Blu-Spark TWRP version I had installed. After the OxyOS update (on both partitions) I flashed TWRP again, rebooted to recovery and installed Pico Gapps.
I found the Resurrection Remix rom to be very buggy and I hate the way the in-display biometric works (very slow and I don't like the paw print used as fingerprint placement). Anyway I started installing apps and after 4 apps installed, it says there is no space left in storage.
Nothing will update, and when I try to check storage with any file explorer it says "access denied" or just won't load. I've tried everything. Wiped the data and did factory reset, then flashed stock rom again and same issue. What am I doing wrong?
That looks like a messed up flash. And is pretty common. Considering that A/B is still new and everyone has his own method of flashing. So assuming you can make it back to latest Stock OOS (9.0.15 right now). If you dunno how to then simple reboot to recovery, flash OOS ZIP and then TWRP. Again Reboot to Recovery from within TWRP (Reboot -> Recovery) and again flash OOS ZIP and TWRP Installer. For TWRP I recommend you to grab the latest one (3.3.1-6 as of now). Once flashed, Format Data (Wipe -> Format Data -> YES) and Reboot. Wait for it to boot up. Now you should be on Stable Stock OOS with TWRP Installed.
Now Download ROM of your Choice (RR, LOS, Bootleggers, whatever). You will also need the latest TWRP Installer (same as above) and Gapps (Nano/ Stock Recommended) and Magisk if you want to Root. Reboot to Recovery, flash ROM ZIP and TWRP Installer ZIP. Wait for it to Finish. Reboot to Recovery. Once in TWRP, again flash ROM and TWRP Installer. Once done, again. Reboot to Recovery from Within TWRP. (Read above on how to). Now, flash Gapps. Magisk if you want to Root. Once done, again do a Format Data. Reboot and be patient for ROM to boot. And then tell me wether this works or Not. Good Luck.
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
rebgershon said:
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
Click to expand...
Click to collapse
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Sent from my hero2lte using XDA Labs
shah22 said:
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Thanks for your reply Shah though I'm still a bit confused by it.
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
In 1). of your reply you say 'You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.'
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Please correct any errors above as I've now tried 3 times since my original post without success but always managed to reflash the stock rom to get me going again.
Click to expand...
Click to collapse
rebgershon said:
Thanks for your reply Shah though I'm still a bit confused by it.
Click to expand...
Click to collapse
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
rebgershon said:
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
Click to expand...
Click to collapse
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
rebgershon said:
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows
Click to expand...
Click to collapse
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
rebgershon said:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Click to expand...
Click to collapse
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
shah22 said:
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
rebgershon said:
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
Click to expand...
Click to collapse
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Sent from my Legendary Hero2LTE using Tapatalk
shah22 said:
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Shah,
Many thanks for the recommendation of the FloydQ rom.
I installed it yesterday after making all backups inc. Smartswitch.
Very easy to install both from flashing and Aroma installation viewpoints. Ran 1st time without a glitch and phone now thinks its an S9+ running Android 10 a la Samsung. I even managed to transfer my Smartswitch backup to my wife's old S7 Edge and then used Smartswitch to transfer from that phone to the 'S9+'.
Only glitch was logging into my Samsung account but sorted that as well so all in all very happy so far.:good:
Click to expand...
Click to collapse