Database Users

Samsung galaxy tab 4 7.0 SM-T230NU TWRP RECOVERY COULD NOT MOUNT data/system/cache

Hey i have Samsung galaxy tab 4 with model no. SMT230NU..
I have flashed twrp custom recovery and i want to install a custom rom..
So, iwent and wiped the data but error ocuurs. it couldnt mount cache/data/system.... I could not even factory reset the data.. Can anone tell me whats the problem and how could i fix it??
(the same error occurs when i install the rom)

pratheekreddy said:
Hey i have Samsung galaxy tab 4 with model no. SMT230NU..
I have flashed twrp custom recovery and i want to install a custom rom..
So, iwent and wiped the data but error ocuurs. it couldnt mount cache/data/system.... I could not even factory reset the data.. Can anone tell me whats the problem and how could i fix it??
(the same error occurs when i install the rom)
Click to expand...
Click to collapse
try fix premissions or lastest twrp 3.0.0.2 or then older 2.8.7.0 twrp. Make sure its not european twrp

Please Help :(. Bootloop after re-flashing stock rom 6.0.1

Hello,
Please help me out guys
I tried for the 1st time to flash custom recovery TWRP - it worked.
Then, i immediately entered to TWRP and i tried to root my phone installing the supersu.zip. When i rebooted my phone - bootloop
In the end, I reflashed stock rom via ODIN but my phone still gets bootloop at SAMSUNG LOGO(NEVER HAPPENED BEFORE)
PS:If i try to enter stock recovery - first it appears "installing system update", then "no command" and then it enters the stock recovery, but nothing can solve the bootloop problem
please help
1.Why bootloop after rooting with the supersu.zip?Should i use the cfautoroot metod?
2.Why bootloop after reflashing stock rom?Never happened before!!!
Thanks!

What Phone have u got mate?
Sent from my Galaxy J5 using XDA Labs

J500F....
I think i managed to solve this...I was flashing the 1st update package .tar which was released for the J5 last summer
Flashing that - not working NOW, ALTHOUGH it worked a few months ago
Flashing .tar from SAMFIRMWARE - working!
But what about the root problem? Which way is the proper way to root your J500F 6.0.1 without bootloops&stuff
johnhux7 said:
What Phone have u got mate?
Sent from my Galaxy J5 using XDA Labs
Click to expand...
Click to collapse

Nothing works: supersu.zip, cf auto root.zip....
i only get bootloops

After flashing using TWRP you should always clear dalvik cache,
The first boot always take some time, 2-5 min,
Before flashing anything try to do a nandroid backup,
The supersu.zip method worked for me,
There is a detailed thread on xda j5 forum on how to upgrade/downgrade and root your device,
After using Odin to flash a ROM enter recovery and wipe data then wipe cache
Sent from my SM-J500H using XDA Labs

Update:
1. It seems it ONLY works to flash 6.0.1 AFTER flashing 5.1.1.(so i have to always repeat this double procedure)
Reflashing 6.0.1 over 6.0.1 - NOT WORKING
2. About root problem - damn, i still can't make it work. I will try your advices and let you know what happened,
Thanks!
saedlar93 said:
After flashing using TWRP you should always clear dalvik cache,
The first boot always take some time, 2-5 min,
Before flashing anything try to do a nandroid backup,
The supersu.zip method worked for me,
There is a detailed thread on xda j5 forum on how to upgrade/downgrade and root your device,
After using Odin to flash a ROM enter recovery and wipe data then wipe cache
Sent from my SM-J500H using XDA Labs
Click to expand...
Click to collapse

I just installed the Recovery then installed @zonik's performance ROM with all its files and my phone was rooted !
I'm using the J5FN
John
Sent from my Galaxy J5 using XDA Labs

Lawr3nce said:
Hello,
Please help me out guys
I tried for the 1st time to flash custom recovery TWRP - it worked.
Then, i immediately entered to TWRP and i tried to root my phone installing the supersu.zip. When i rebooted my phone - bootloop
In the end, I reflashed stock rom via ODIN but my phone still gets bootloop at SAMSUNG LOGO(NEVER HAPPENED BEFORE)
PS:If i try to enter stock recovery - first it appears "installing system update", then "no command" and then it enters the stock recovery, but nothing can solve the bootloop problem
please help
1.Why bootloop after rooting with the supersu.zip?Should i use the cfautoroot metod?
2.Why bootloop after reflashing stock rom?Never happened before!!!
Thanks!
Click to expand...
Click to collapse
I've seen your PM.
I don't really have any idea. But I have a suggestion, although I don't know if it will solve your problem. Backup your stuff from internal memory before. Try to wipe everything including internal memory (internalsd in TWRP recovery), then turn off your phone and re-flash stock rom.

Hello, @Lawr3nce I followed this tutorial by @rjrulz007 http://forum.xda-developers.com/galaxy-j5/how-to/tutorial-upgrade-j5-2015-to-6-0-t3443904 to root my j500h, I downloaded the supersu.zip from this link http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Don't forget to backup your data before upgrading (you can use smart switch), after flashing using Odin go to recovery (stock recovery), wipe data/factory reset and wipe cache partition, this should solve the boot loop problem.
Before flashing the supersu zip file do a nandroid backup using TWRP (boot to TRRP, choose backup, select sdcard as save location then swipe to start backup. In case the flash of zip file failed choose restore and select the backup you did before, better than reflashing the whole ROM using Odin )
Sent from my SM-J500H using XDA Labs

Ok, thank you all for the help. Conclusions:
1. For some reason, it NEVER works to flash directly the 6.0.1...I always have to flash the 5.1.1 first, then the 6.0.1.
2. I will try that root procedure from the link .
I am very willing to root it because i want to remove many useless preinstalled bloatwares from my phone
(due to very low free space i can't even update my apps)
UPDATE: That procedure with that .zip WORKS! THANKS

[Help][Support] TWRP for s7 edge on 8.0 Oreo

I flashed stock oreo after running into issues with SafetyNet on custom ROMs and TWRP. I'm now trying to reinstall TWRP but after trying two different versions, files under internal storage are not visible, and flashing filed from external SD card does not work. It may have something to do with the stock firmware I flashed, but I honestly have no idea. I flashed a BTU Oreo build from UK, even though my 935F is from South America. I couldn't remember which country, so I just went with the BTU.
Any advice is greatly appreciated. Thanks in advance for the help.

Rehvix said:
I flashed stock oreo after running into issues with SafetyNet on custom ROMs and TWRP. I'm now trying to reinstall TWRP but after trying two different versions, files under internal storage are not visible, and flashing filed from external SD card does not work. It may have something to do with the stock firmware I flashed, but I honestly have no idea. I flashed a BTU Oreo build from UK, even though my 935F is from South America. I couldn't remember which country, so I just went with the BTU.
Any advice is greatly appreciated. Thanks in advance for the help.
Click to expand...
Click to collapse
flash 3.2.3 twrp
If you don't use 3.2.3 internal storage can't be edited or viewed.
Go into twrp and hit install then go to install image to install the img file. If you don't use this option you will only install zips.

pingufanpoy said:
flash 3.2.3 twrp
If you don't use 3.2.3 internal storage can't be edited or viewed.
Go into twrp and hit install then go to install image to install the img file. If you don't use this option you will only install zips.
Click to expand...
Click to collapse
3.2.3 is what i tried with the first time, and that didn't work. After that I tried 3.1.1, since thats what I had working the first time, but that didnt work either. Also, I go into flash the image in twrp like you said but after a reboot it sends me to download mode when i try recovery.

Boot into odin then flash as ap.
https://mega.nz/#!4JcmXKpK!BANHL1q1ZiDfL_R-YlM4pWERjnO724EFn84C413BJuY

pingufanpoy said:
Boot into odin then flash as ap.
https://mega.nz/#!4JcmXKpK!BANHL1q1ZiDfL_R-YlM4pWERjnO724EFn84C413BJuY
Click to expand...
Click to collapse
Followed directions with the file you provided, same problem though

Rehvix said:
Followed directions with the file you provided, same problem though
Click to expand...
Click to collapse
Flash the checkboxes individually if you are getting bootloop.
It reboots to odin if system os is unstable or corrupt missing too. So try re-downloading also.

pingufanpoy said:
Flash the checkboxes individually if you are getting bootloop.
It reboots to odin if system os is unstable or corrupt missing too. So try re-downloading also.
Click to expand...
Click to collapse
I only get bootloop if I allow system modifications on first startup in TWRP. If I leave it as read only, I can reboot into System no issue. Either way, flashing ROMs and Magisk doesn't work.

you Need to wipe data and then reboot into recovery and then Flash "remove encryption.zip"

Solved issue. After flashing TWRP, I went into Wipe, Advanced, reformat, and reformatted Data as EXT2, then EXT4. Everything worked as normal after that.

Phone stuck at Decryption unsuccessful :crying:

I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:

Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.

jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now

Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.

Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...

Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.

I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.

In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...

There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?

Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!

downgrade twrp i has same prob twrp 3.3.1 gives issues

ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !

Boot Problem after Successful TWRP flash

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