Hello,
I want to Install the Xiaomi.eu MIUI12 Rom in redmi note 7 i have the Orangefox Recovery and im currently on miui11 global 11.0.5 im confused about the encryprytion. Can anyone give me a step by step Guide what i have to so to Install miui12 xiaomi.eu Rom with orangefox and encryprytion
LuzzFN said:
Hello,
I want to Install the Xiaomi.eu MIUI12 Rom in redmi note 7 i have the Orangefox Recovery and im currently on miui11 global 11.0.5 im confused about the encryprytion. Can anyone give me a step by step Guide what i have to so to Install miui12 xiaomi.eu Rom with orangefox and encryprytion
Click to expand...
Click to collapse
(I would recommend a clean flash to prevent any mishap. However, this is a tested method on my Redmi 7S, I would not be responsible for your bricked phone, you know!)
First of all, backup all your important data & boot up into Orangefox.
Go to Menu》Settings》Tick "Disable Forced Encryption " (make sure it's ticked up)
Tip: In case you're flashing official MIUI, also tick "Disable dm-verity".
Now go to Wipe section
Select all partions except Internal storage, Micro SD and USB OTG.
Swipe to wipe.
Very Important: Go to Menu》Reboot》Recovery to reboot to recovery.
Now from the main menu, go to files, choose the ROM package and flash.
Now to be safe (however not needed), you would like to reboot to recovery rather than to system to make sure everything go right.
Then from Recovery go to Menu> Reboot>System.
It should boot up in around 5-10 min.
Best of luck.
Azamsm said:
.. Go to Menu》Settings》Tick "Disable Forced Encryption " (make sure it's ticked up)
Tip: In case you're flashing official MIUI, also tick "Disable dm-verity"....
Click to expand...
Click to collapse
Ahem! Most definitely do NOT tick either of these, or it will end in tears. With lavender, you must keep DM-Verity and encryption intact.
Will I lose orangefox if i flash official closed beta?
eraycetin said:
Will I lose orangefox if i flash official closed beta?
Click to expand...
Click to collapse
I lost It, the ROM replaced OrangeFox with Redmi Recovery, just reflash the Recovery from fastboot when you've installed the ROM
DarthJabba9 said:
Ahem! Most definitely do NOT tick either of these, or it will end in tears. With lavender, you must keep DM-Verity and encryption intact.
Click to expand...
Click to collapse
So is there any way to change custom roms without formatting data Everytime?
ahadrox said:
So is there any way to change custom roms without formatting data Everytime?
Click to expand...
Click to collapse
Yes - if the ROMs are based on compatible device trees with similar encryption protocols. Some of the new FBE ROMs fall in that category.
Related
10.0.2.0
https://sourceforge.net/projects/xi...ti_MI6_V10.0.2.0.OCACNFH_v10-8.0.zip/download
https://androidfilehost.com/?fid=11410963190603872619
10.0.1.0
https://sourceforge.net/projects/xi...ti_MI6_V10.0.1.0.OCACNFH_v10-8.0.zip/download
https://androidfilehost.com/?fid=1322778262903996298
Are there instant apps working? On beta 8.8.23 xiaomi.eu it didn't work, so i've moved to global beta.
is this legit? I don't see the release on their website
EDIT: nvm its legit, anyway can I just flash this one over xiaomi.eu 8.8.30? I don't want to reset my phone and lose all my files/apps as much as possible
RamonXick said:
is this legit? I don't see the release on their website
EDIT: nvm its legit, anyway can I just flash this one over xiaomi.eu 8.8.30? I don't want to reset my phone and lose all my files/apps as much as possible
Click to expand...
Click to collapse
Yep, you can.
Is there any major changes between xiaomi.eu MIUI 10 Stable and xiaomi.eu Weekly 8.8.30 ?
radzix27 said:
Is there any major changes between xiaomi.eu MIUI 10 Stable and xiaomi.eu Weekly 8.8.30 ?
Click to expand...
Click to collapse
+1
Been looking for this answer too. Anyone?
encryption working in miui 10 from xiaomi.eu?
Will I lose twrp and data upon flashing this?
Sent from Sagit
spicediablo said:
Will I lose twrp and data upon flashing this?
Sent from Sagit
Click to expand...
Click to collapse
No you won't loose TWRP. People on MIUI 10 Beta 8.9.20 can dirty flash but won't boot normally and get force close messages and will automatically go back into TWRP. To fix this you will need to swipe to factory reset (wipes data, cache and dalvik not including internal storage.)
That's how I was able to boot normally and had to install all my apps etc. I still had all my data etc. luckily.
So be warned!
after
Camerado said:
https://sourceforge.net/projects/xi...ti_MI6_V10.0.1.0.OCACNFH_v10-8.0.zip/download
https://androidfilehost.com/?fid=1322778262903996298
Click to expand...
Click to collapse
After i flash this rom i cant get back normal miui rom.
How do I flash it?
Currently I've AICP flashed.
Do I wipe system, data, cache, then flash the rom?
Thanks for any help!
Maybe U must format data: https://youtu.be/cvXbzhJEan8?t=26
How about battery? Does it heat or drain fast? Any bugs?
Really snappy. No bugs so far.
Battery drain is normal. Not exceptional.
My flash procedure -
1. Download latest build (I'm using 8.11.15) from xiaomi.eu website.
2. Remove all passwords/pattern lock (just to avoid any complications)
3. Wipe everything.
4. Format data
5. Flash the file via TWRP
6. Patiently let it reboot for the 1st time.
7. Wait for 1/2 minutes after 1st reboot.
8. Reboot to system (normal reboot). Login to Miui/Google account etc. Use for 5-10 minutes.
9. Reboot to TWRP to flash Magisk (mine is 17.1)
10. Reboot to system. And do whatever you want.. Lol
Hope it helps.
can i install gapps alongside xiaomi.eu rom ?
10.0.2.0 added in OP.
Changelog of 10.0.2.0?
Can't find what's new.
Is it worth to install this rom ? It's official ?
leokak said:
Is it worth to install this rom ? It's official ?
Click to expand...
Click to collapse
It's official. But my opinion. Battery is worse than prev update.
I like Lineage OS but the fact the second screen stays on even when locked drains battery even with a custom Kernal. I would love to be stock and rooted but since I DS the boot. I understand flashing stock will get rid of it(maybe I am wrong?). I just want a stock rom or a way to go to stock and stay rooted? is this possible or am I stuck with everyone else?
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
kaluna00 said:
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
Click to expand...
Click to collapse
Thank you, Is alpha Rom hard to install?
stevieshae said:
Thank you, Is alpha Rom hard to install?
Click to expand...
Click to collapse
No. Details should be in the OP
kaluna00 said:
No. Details should be in the OP
Click to expand...
Click to collapse
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
stevieshae said:
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
Click to expand...
Click to collapse
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
jackson019 said:
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
Click to expand...
Click to collapse
Thank you jackson for the fast response, have you tried the rom, and do you like it?
stevieshae said:
Thank you jackson for the fast response, have you tried the rom, and do you like it?
Click to expand...
Click to collapse
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
jackson019 said:
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
Click to expand...
Click to collapse
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
stevieshae said:
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
Click to expand...
Click to collapse
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
jackson019 said:
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
Click to expand...
Click to collapse
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
stevieshae said:
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
Click to expand...
Click to collapse
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
jackson019 said:
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
Click to expand...
Click to collapse
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Also... Should I install dirty santa kernal?
stevieshae said:
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Click to expand...
Click to collapse
First off, you should be rooted with TWRP 3.2.3-4 from here already installed. Then follow these steps:
Clean Install -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Install 1.0.7 -> Choose the proper kernel for your root method
If you rooted via dirtysanta, choose the mk2000 santa kernel
Reboot to recovery, no need to go to setup
Clean Install 1.3.0 -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Use the same kernel from above
Flash Magisk v18.1
Wipe Dalvik/Cache
Reboot to System
I have unlocked bootloader, official OrangeFox recovery, and Magisk installed. I'm currently on stable global MIUI (stock 10.3.6.0 PFGMIXM).
When I flashed OrangeFox and Magisk, I had the encryption issue in which the device asks for a non-existent password and I had to wipe data.
Will flashing an official update through OrangeFox or TWRP produce the same issue? Or can I just dirty-flash it normally?
TheGentlemanZombie said:
I have unlocked bootloader, official OrangeFox recovery, and Magisk installed. I'm currently on stable global MIUI (stock 10.3.6.0 PFGMIXM).
When I flashed OrangeFox and Magisk, I had the encryption issue in which the device asks for a non-existent password and I had to wipe data.
Will flashing an official update through OrangeFox or TWRP produce the same issue? Or can I just dirty-flash it normally?
Click to expand...
Click to collapse
Dirty flash the update shouldn't cause any issues. Remember to flash again magisk after the rom.
darhma said:
Dirty flash the update shouldn't cause any issues. Remember to flash again magisk after the rom.
Click to expand...
Click to collapse
I would format data one time only, then reinstall ROM. Shouldn't have any password asked from then on.
TheGentlemanZombie said:
I have unlocked bootloader, official OrangeFox recovery, and Magisk installed. I'm currently on stable global MIUI (stock 10.3.6.0 PFGMIXM).
When I flashed OrangeFox and Magisk, I had the encryption issue in which the device asks for a non-existent password and I had to wipe data.
Will flashing an official update through OrangeFox or TWRP produce the same issue? Or can I just dirty-flash it normally?
Click to expand...
Click to collapse
There is actually an OrangeFox thread you know.
DarthJabba9 said:
There is actually an OrangeFox thread you know.
Click to expand...
Click to collapse
I assumed you would tell me it was not really an OrangeFox-related question, but a general Lavender one; or you would just link me to the README file.
Could I get an answer if I asked in the official OrangeFox thread?
TheGentlemanZombie said:
I assumed you would tell me it was not really an OrangeFox-related question, but a general Lavender one; or you would just link me to the README file.
Could I get an answer if I asked in the official OrangeFox thread?
Click to expand...
Click to collapse
Well, you have already been given the answer. You only needed to format data once (and, yes, that is a general lavender issue). Flashing an updated ROM should not require formatting data. Of course if you flash a custom ROM that uses a different encryption protocol, you will need to format data again (ditto if you want to return to MIUI from a custom ROM).
Hey!
I want to ask you good people how to properly change my global 11.0.1.0.PFJMIXM to miui 11 stable xiaomi eu (xiaomi.eu_multi_HMK20MI9T_V11.0.6.0.QFJCNXM_v11-10).
My phone is actually encrypted, has antiroll back "1", twrp already installed (twrp-3.3.1-2-davinci-fix).
Lately I've tried:
1. twrp format data, typed "yes"
2. copied rom, installed
3. reboot to recovery, and flashed magisk
and bootlooped...
I also would like to have hasty kernel and try new 82hz dtbo... If you be soo kind, you can suggest me how to do it also.
Thank you
rapids said:
Hey!
I want to ask you good people how to properly change my global 11.0.1.0.PFJMIXM to miui 11 stable xiaomi eu (xiaomi.eu_multi_HMK20MI9T_V11.0.6.0.QFJCNXM_v11-10).
My phone is actually encrypted, has antiroll back "1", twrp already installed (twrp-3.3.1-2-davinci-fix).
Lately I've tried:
1. twrp format data, typed "yes"
2. copied rom, installed
3. reboot to recovery, and flashed magisk
and bootlooped...
I also would like to have hasty kernel and try new 82hz dtbo... If you be soo kind, you can suggest me how to do it also.
Thank you
Click to expand...
Click to collapse
Format data with yes
Reboot to recovery
Flash the rom
Clear cache/dalvik
Don't flash the Magisk right away
Sent from my Mi 9T using XDA Labs
welder73 said:
Format data with yes
Reboot to recovery
Flash the rom
Clear cache/dalvik
Don't flash the Magisk right away
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
okay! soo i'll flash magisk later, after first configuration, and what about hasky kernel and dtbo?
rapids said:
okay! soo i'll flash magisk later, after first configuration, and what about hasky kernel and dtbo?
Click to expand...
Click to collapse
Flash kernel after first setup too...if anything goes wrong, just flash the rom over.
About dtbo, I don't use it, follow the instructions in that thread...
Sent from my Mi 9T using XDA Labs
okay, i managed successfully xiaomi eu stable V11.0.6.0 and magisk.
Now can sombody advice me how exacly should I install "Hasty-davinci-Intoxicated-r3" and "VendorOverclockPackV2" (from topic: https://forum.xda-developers.com/mi-9t/themes/screen-overclock-mode-t4079693/page33 )
to get more then 66hz refresh rate?
Oh, and my phone is now actually encrypted...
I know it's something like:
1. mount vendor if isnt
2. backup boot, dtbo and vendor
3. flash VendorOverclock V2.img (without reboot)
4. install hasty kernel (without reboot)
5. flash oc dtbo file (without reboot)
6. install magisk (without reboot)
would it be ok?
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