Database Users

[Guide][Steps][KITKAT] Installing cyanogenmod 11 M7 on Samsung Galaxy S2 (i9100)

Well, I know there are lot of helpful guides out there on how to install cyanogenmod but not everybody gets what he's looking for. I recently searched a lot of sites, forums, and lot of xda posts for installing cyanogenmod 11 M7. And i finally found few posts that helped me.
With these posts one can get an idea about how to flash a kernel, how to back up the data, and how to flash a custom ROM on a S2. Pretty helpful...isn't it? All thanks to these guys - @avirk , @-Grift- @banjara @Vivek_Neel @Phil3759 .
The steps might fit correct for some.. where there might be some variations for others. I myself didn't find some steps from the guide i followed while backing up my data. But still.. i went for it. And it was good enuf.
So here are the steps that i followed... n i think which might help some one like me out there.
First of all. as they say.. If anything goes wrong. I'm not responsible. If everything goes right.. well..Thank you then.
1) Downloads required
- << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
- CWM 6.0.4.7 (Compiled From CM11 KK 4.4.2 Source) (LATEST) recovery
- cm-11-20140609-SNAPSHOT-M7-i9100.zip
- Gapps
2) Copy << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >> into external storage.
3) Boot into stock recovery (volume up+home+power)
4) Select "apply update from external storage".
5) Now select the << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >> file you copied in previous step
--- Rooted! ---
6) Reboot into recovery select option “Backup and Restore”
7) Select the option “Advance Backup and Restore”
8) Select the “Custom Backup Job”. There you have tick the “Preload” folder
9) scroll down and “Start custom Backup job” And then it will ask where you want to store the backup on you “Internal/External Storage”
10) After selecting the storage path it will start the backup process. When it finished you are ready to install the new ROM.
- One thing to be noted. I did not find the ‘Advanced backup and restore’ option while I was doing it. So I just took the normal back up. For a complete guide on backup refer to THIS POST
11) Boot into recovery (Do not boot into OS)
12) Select "apply update from external storage".
13) Now select the 6.0.4.7 (Compiled From CM11 KK 4.4.2 Source) (LATEST) recovery file that was copied on your external storage
14) CWM 6.0.4.7 now installed.
15) Boot into recovery (Do not boot into OS)
16) Wipe data/factory reset
17) Wipe cache
18) Wipe dalvik cache from advanced menu.
19) Select "apply update from external storage".
20) cm-11-20140609-SNAPSHOT-M7-i9100.zip
21) It will get installed.
22) Go back to recovery and Select "apply update from external storage".
23) Select the Gapps .zip file.
24) Reboot to OS.
And you're done!

Where are /format system and /format preload??? If you are on 4.1.2 stock you need to do a full wipe.
Flash latest philz kernel in stock recovery, then reboot into recovery again(hold 3 buttons) and flash latest Philz CWM Touch recovery(6.0.4.8!). Then do a full wipe and flash a custom rom and gapps.
Послато са GT-I9100 уз помоћ Тапатока

Zile995 said:
Where are /format system and /format preload??? If you are on 4.1.2 stock you need to do a full wipe.
Flash latest philz kernel in stock recovery, then reboot into recovery again(hold 3 buttons) and flash latest Philz CWM Touch recovery(6.0.4.8!). Then do a full wipe and flash a custom rom and gapps.
Послато са GT-I9100 уз помоћ Тапатока
Click to expand...
Click to collapse
Well.. i did factory, cache and dalvik.. :\ and till now everything's fine..
But you might be correct. I used the guide that has steps for backup and all...

SubraiSambary said:
But you might be correct. I used the guide that has steps for backup and all...
Click to expand...
Click to collapse
Please use the rom nuke script it is better. It will clean your phone and prepare for new rom. Then everyting will work fine.
Послато са GT-I9100 уз помоћ Тапатока

Zile995 said:
Please use the rom nuke script it is better. It will clean your phone and prepare for new rom. Then everyting will work fine.
Послато са GT-I9100 уз помоћ Тапатока
Click to expand...
Click to collapse
That sounds nice.. can you provide the link?

nice guide @SubraiSambary , keep up the good work

shriom_manerker said:
nice guide @SubraiSambary , keep up the good work
Click to expand...
Click to collapse
Thanks buddy

SubraiSambary said:
Well.. i did factory, cache and dalvik.. :\ and till now everything's fine..
But you might be correct. I used the guide that has steps for backup and all...
Click to expand...
Click to collapse
I Agree with Zile.
I installed Cyano with similar steps and I finished with an useless phone with system partition full.
format system and preload are mandatory moving from stock to cyano in my opinion.

FandangoL said:
I Agree with Zile.
I installed Cyano with similar steps and I finished with an useless phone with system partition full.
format system and preload are mandatory moving from stock to cyano in my opinion.
Click to expand...
Click to collapse
What happened with me was.. i didn't find the preload thing while making my backup.
So i missed some steps from the guide which i followed. I'll be trying it again when cm11 m8 will be out.
May be that time i can find the preload section.

SubraiSambary said:
Well, I know there are lot of helpful guides out there on how to install cyanogenmod but not everybody gets what he's looking for. I recently searched a lot of sites, forums, and lot of xda posts for installing cyanogenmod 11 M7. And i finally found few posts that helped me.
With these posts one can get an idea about how to flash a kernel, how to back up the data, and how to flash a custom ROM on a S2. Pretty helpful...isn't it? All thanks to these guys - @avirk , @-Grift- @banjara @Vivek_Neel @Phil3759 .
The steps might fit correct for some.. where there might be some variations for others. I myself didn't find some steps from the guide i followed while backing up my data. But still.. i went for it. And it was good enuf.
So here are the steps that i followed... n i think which might help some one like me out there.
First of all. as they say.. If anything goes wrong. I'm not responsible. If everything goes right.. well..Thank you then.
1) Downloads required
- << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
- CWM 6.0.4.7 (Compiled From CM11 KK 4.4.2 Source) (LATEST) recovery
- cm-11-20140609-SNAPSHOT-M7-i9100.zip
- Gapps
2) Copy << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >> into external storage.
3) Boot into stock recovery (volume up+home+power)
4) Select "apply update from external storage".
5) Now select the << 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >> file you copied in previous step
--- Rooted! ---
6) Reboot into recovery select option “Backup and Restore”
7) Select the option “Advance Backup and Restore”
8) Select the “Custom Backup Job”. There you have tick the “Preload” folder
9) scroll down and “Start custom Backup job” And then it will ask where you want to store the backup on you “Internal/External Storage”
10) After selecting the storage path it will start the backup process. When it finished you are ready to install the new ROM.
- One thing to be noted. I did not find the ‘Advanced backup and restore’ option while I was doing it. So I just took the normal back up. For a complete guide on backup refer to THIS POST
11) Boot into recovery (Do not boot into OS)
12) Select "apply update from external storage".
13) Now select the 6.0.4.7 (Compiled From CM11 KK 4.4.2 Source) (LATEST) recovery file that was copied on your external storage
14) CWM 6.0.4.7 now installed.
15) Boot into recovery (Do not boot into OS)
16) Wipe data/factory reset
17) Wipe cache
18) Wipe dalvik cache from advanced menu.
19) Select "apply update from external storage".
20) cm-11-20140609-SNAPSHOT-M7-i9100.zip
21) It will get installed.
22) Go back to recovery and Select "apply update from external storage".
23) Select the Gapps .zip file.
24) Reboot to OS.
And you're done!
Click to expand...
Click to collapse
Where's the GApps.zip file? There's no link provided.

ranzzit said:
Where's the GApps.zip file? There's no link provided.
Click to expand...
Click to collapse
I left the choice to the readers.
Anyways... You can find gapps in the following threads :
http://forum.xda-developers.com/gal...wip-cyanogenmod-11-unnofficial-build-t2523604
http://forum.xda-developers.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
http://forum.xda-developers.com/showthread.php?t=2397942
http://forum.xda-developers.com/showthread.php?t=2530929
And you might find some links on google search too.
Just be sure you download the gapps for Kitkat 4.4.x. This will avoid problems
Go ahead and take your pick

SubraiSambary said:
I left the choice to the readers.
Anyways... You can find gapps in the following threads :
http://forum.xda-developers.com/gal...wip-cyanogenmod-11-unnofficial-build-t2523604
http://forum.xda-developers.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
http://forum.xda-developers.com/showthread.php?t=2397942
http://forum.xda-developers.com/showthread.php?t=2530929
And you might find some links on google search too.
Just be sure you download the gapps for Kitkat 4.4.x. This will avoid problems
Go ahead and take your pick
Click to expand...
Click to collapse
Thanks a ton mate You rock. Much appreciated.

ranzzit said:
Thanks a ton mate You rock. Much appreciated.
Click to expand...
Click to collapse
hehe. You're welcome buddy!

SubraiSambary said:
I left the choice to the readers.
Anyways... You can find gapps in the following threads :
http://forum.xda-developers.com/gal...wip-cyanogenmod-11-unnofficial-build-t2523604
http://forum.xda-developers.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
http://forum.xda-developers.com/showthread.php?t=2397942
http://forum.xda-developers.com/showthread.php?t=2530929
And you might find some links on google search too.
Just be sure you download the gapps for Kitkat 4.4.x. This will avoid problems
Go ahead and take your pick
Click to expand...
Click to collapse
You can link your above post for the link to the GApps section in the OP, then you'll not get other questions as to the link for GApps.... Also, as said by @Zile995, it is better if you include formatting system and preload too in your guide as not doing so may cause issues and doing so is the best way to full wipe your system for fresh flashing without issues...
And yes...Great work.... :good:

hi
i did every step of your procedures (more times) and the result is the same!!
when the phone starts all the google processes crash and it is impossible to do anything...
If I install the Cyano 10.1 everything is fine...
What can I do????

Any tried this on SHW-M250K model? Is it even compatible?
Sent from my iPhone using Tapatalk

Can I boot into system after installing 03.06.2013 - PhilZ-cwm6 v5.06.1 and later install new rom?

Would any of you guys be able to help me (a rookie when it comes to this) with these Q's in my thread about CyanogenMod?
This thread: http://forum.xda-developers.com/galaxy-s2/help/stock-rom-to-cyanogenmod-import-sms-t2903491
Btw, isn't it easiest to acquire CyanogenMod by using the CyanogenMod Installler for the i9100?
http://beta.download.cyanogenmod.org/install

Bizius said:
hi
i did every step of your procedures (more times) and the result is the same!!
when the phone starts all the google processes crash and it is impossible to do anything...
If I install the Cyano 10.1 everything is fine...
What can I do????
Click to expand...
Click to collapse
Never had this problem bud. I installed M9 in the same way but google process failures were never encountered.
I'm afraid i might not be of any use here but would suggest one thing that stick to 10.1 till u find an answer to this.
And regarding your problem..... These guys( @avirk , @banjara , @-Grift- , @Vivek_Neel , @Phil3759 ) might be able to help you out. They helped me too.

bums85 said:
Can I boot into system after installing 03.06.2013 - PhilZ-cwm6 v5.06.1 and later install new rom?
Click to expand...
Click to collapse
I guess it should be ok to boot into the system because you'd be installing the recovery and if the recovery is compatible with the ROM and won't give any problem then you can. But still.. always take a second opinion before you try because... even I'm a learner.

Fix error installing STOCK GAPPS on Oreo ROM

Hey,hey,hey
Did you facing error while installing Full Gapps or Stock Gapps? which says installing gapps error because not enough system partition size.
Yes,i'm facing that bug too,but i have a solution for this issue.That bug can be happen because after flashing any Oreo ROM your system partition become smaller,sure that is not normal.
To fix this you need to "resize" your system partition. I almost resize my system partition using an "Extreme Way!" and if i do that maybe my phone goes bricked. Thanks to god i can found what the problem after try "try and error" method so it can be said,this solution I found because of accident.Ok enough
Ok this the simple method.
1. Download Flashable Busybox by @YashdSaraf https://sourceforge.net/projects/busybox-yds/files/Sep-06-17/Busybox-1.27.2-YDS-UNIVERSAL.zip/download original thread https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:

error 1 when repairing the partition. But it still worked. Thanks

Ichijou Raku said:
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:
Click to expand...
Click to collapse
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??

mg712702 said:
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??
Click to expand...
Click to collapse
Same question here.

raiden_1115 said:
Same question here.
Click to expand...
Click to collapse
Bro....I just test it and yes you have to de this everytime when you installing oreo....and I didn't flash the busybox....but I successfully resize it.....then the question is what's for the busybox is??

Doing this every installing oreo is,yes...
I think,cannot resize partition is only happened when upgrading Nougat to Oreo ,because every changing an oreo rom to another oreo rom,I dont have to install busybox again..
Busybox...mmmmm try flashing oreo rom after a nougat one,then resize Partition you will facing an error code on twrp say "resize error blablablabla" (or another,im forget what it say) ,for that,im thinking why i cannot resize the partition,While still in nougat I still can resize partition without any problem..And as you know, busybox contains a number of commands that can run in the terminal, and "resizing command" is contained within the busybox ..
Oh,im not responsible with any error after trying this method,But all this time I have never experienced any errors because this method..

Im still a newbie on android,i dont have a lot experience on android..As I said ,i found this method by trying "try and error" method,trying installing nougat first then oreo,trying installing boot.img first then oreo,and much more attempt..and i still got same error hahaha.. frustrated because cannot installing large gapps..
Then i found this method,just try this method and tell me if you found an error after trying this method..
But I can be sure it will not happen just because resize the partition, because resizing partition here instead of changing the size of partition system becomes bigger,Resize here only returns the size of the corrupted partition system

i got an error when resizing and repairing on my lg v20 h918, I still followed steps and ended up with the error after gapp installation. I am back to a blinking black screen after the lg logo. I think my phone is a lost cause.

[FIXED] How to remove data encryption in TWRP

Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+ will likely face the same issue and the solution preferred here would work.
By default, your device storage is encrypted (Settings > Security > Encryption) and any TWRP from 3.1+ respects that protocol.
This means that the internal storage would be showing 0mb because it can't be mounted, (no) thanks to the encryption.
Previous versions of TWRP (eg 3.0.3) could easily decrypt the device using the default password but from version 3.1, things changed.
SOLUTION
Needed:
1. An unlocked bootloader
2. TWRP installed (download from the TWRP thread)
3. An SD CARD (or USB OTG)
4. Magisk.zip (latest version, copy it to the SD card)
NOTE: Copy/Backup your files from your internal storage into your PC as this process would wipe everything from the internal storage.
STEPS
> With the bootloader unlocked and TWRP flashed, boot into recovery.
> The screen might be dark when in recovery, just press the power button and the the vol- button, it'll turn ON. Then swipe to unlock.
> You can change the language to English by clicking on the 2nd rectangle by the right above the swipe function.
> Tick "do not show again" and the swipe to allow modification.
> Confirm device encryption by clicking "Backup" or "Install", if the storage size is 0mb or no folder is showing while trying to install, then the device is encrypted.
> Go back, click "Wipe"
> You can choose to Factory reset, Format data or Advanced wipe > tick /data. Either way, it's going to wipe EVERYTHING in the internal storage (that's the purpose of device encryption, to prevent unauthorized access to the storage). However, I recommend you choose "FORMAT DATA"
> If you chose "Format data", then type yes in the next screen and swipe to format.
> When completed, go home, click Reboot and choose Recovery to boot into recovery (very important, do not reboot the phone into system otherwise you'll start all over. Reboot into recovery, not system).
> When in the recovery, click install > select storage > SD card (or USB OTG) (note that the internal storage will display as normal but remember it is now empty following the data reset)
> Navigate to the Magisk in /Sdcard (or USB OTG) and install.
> When completed, you can now reboot safely into system.
> Complete the phone setup and Open Magisk Manager. Notice that Magisk is now installed and "Preserve force encryption" is now unticked". You can also go to Settings > Security > Encryption and notice that it will ask you to encrypt your device, meaning it is decrypted now.
> The next time you will boot into recovery, TWRP may still be in Russian language, just change it one more time and you are good to go.
> Now you can flash anything you want including Xposed (download latest version from the official Xposed thread/website).
That's all. Cheers! Happy tweaking

If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery

I love you broo!!
I was like 5 hours with this encryption problem without being able to solve it, Thank you very much. I LOVE YOU! Hahaha :good::victory::victory::fingers-crossed:

Cheers!

dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
How to you get OTA update when you are rooted? I can't

dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?

Ersid Kapaj said:
How to you get OTA update when you are rooted? I can't
Click to expand...
Click to collapse
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.

dwapking said:
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.
Click to expand...
Click to collapse
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.

have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?

Ersid Kapaj said:
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.
Click to expand...
Click to collapse
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.

mrmazak said:
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?
Click to expand...
Click to collapse
The kernel version is correct. The 4.4 is only shown in CPU_Z app

TheSpartanM4 said:
have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?
Click to expand...
Click to collapse
Yes... Some modules (Viper4Android, Busybox NDK) did flash successfully (though not mounted in Magisk modules section but are working just fine) while many others refused to install.
I am currently trying to verify the cause. For now, no solution yet.

dwapking said:
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.
Click to expand...
Click to collapse
I have downloaded the update once but when i try to install it says the it's rooted and can't install. Since then it's the same problem.

Yes of course, before any update is installed, root integrity check is performed. Once any modifications has been detected, it will abort.
That's why I said you should flash back your STOCK SYSTEM, RECOVERY AND BOOT, since they're the partitions affected by the root.
Don't forget to wipe the data of "Wireless Update" before proceeding to install.

ok, i'm gonna give this a try once i'm properly awake. i had been trying to install magisk via adb push and it would not work, so we'll see how this does. thanks!

Does safetynet pass for anyone? MobileIron still detects the phone as rooted with Magisk installed...

I got it to work! I have TWRP installed, I have Magisk working, and Safetynet check passes. I can't post screenshots because I don't have enough posts, but I suppose I have root now! ...it's not nearly as exciting on a non-bloated phone with no available roms. But I think we're maybe ready to say we officially have root? I can't learn coding or I'd try to make my own rom.

Cheers!

Doogee Mix only reboots to Doogee Splash which warns: Orange State
Your device has been unlocked and can't be trusted. YOur device will boot in 5 seconds. Then TWRP boots in English instead of Russian. Thats all I get. Is there a custom ROM for Doogee Mix? Did I wiped the OS? Thank you for getting me out off the Encryption - loop.

Can someone please help me understand why I can only boot into TWRP Recovery now???

error flashing stock rom

so, i recently flashed stock rom (miui 10.3.11) and after flashing, wifi will not turn on, it just tries to turn on and doesnt while trying to activate the xiaomi account on my phone. This has never happened to me before, and i dont know what is happening help?
Edit 1: after trying multiple stock roms, all of them wont turn on the wifi, my pc is connected to ethernet, is that a factor?

To fix Wifi issue on stock roms:
1) Flash a working TWRP for your device / MIUI & Android version.
2) Boot to TWRP
3) "Mount" menu > Select "persist" partition
4) "Advanced" menu > "File Manager" > Open "persist" folder and delete "wlan_mac.bin" file
5) "Mount" menu > Deselect "persist" partition
6) Reboot the phone and check WiFi again
P.S.: If "wlan_mac.bin" file doesn't exist then I don't know how to help you...
But you can flash xiaomi.eu ROMs, I'm sure it will fix this issue.

Micdu70 said:
To fix Wifi issue on stock roms:
1) Flash a working TWRP for your device / MIUI & Android version.
2) Boot to TWRP
3) "Mount" menu > Select "persist" partition
4) "Advanced" menu > "File Manager" > Open "persist" folder and delete "wlan_mac.bin" file
5) "Mount" menu > Deselect "persist" partition
6) Reboot the phone and check WiFi again
P.S.: If "wlan_mac.bin" file doesn't exist then I don't know how to help you...
But you can flash xiaomi.eu ROMs, I'm sure it will fix this issue.
Click to expand...
Click to collapse
can't flash twrp, as my device is locked by xiaomi account verification
edit: will try again, hopefully it works

Micdu70 said:
To fix Wifi issue on stock roms:
1) Flash a working TWRP for your device / MIUI & Android version.
2) Boot to TWRP
3) "Mount" menu > Select "persist" partition
4) "Advanced" menu > "File Manager" > Open "persist" folder and delete "wlan_mac.bin" file
5) "Mount" menu > Deselect "persist" partition
6) Reboot the phone and check WiFi again
P.S.: If "wlan_mac.bin" file doesn't exist then I don't know how to help you...
But you can flash xiaomi.eu ROMs, I'm sure it will fix this issue.
Click to expand...
Click to collapse
well, wlan_mac.bin does not exist

riotp100 said:
well, wlan_mac.bin does not exist
Click to expand...
Click to collapse
Like me, but it was after failing to flash a custom ROM....
Now I installed xiaomi.eu custom ROMs (weekly/beta), Wifi is working and it's a good ROM.

Micdu70 said:
Like me, but it was after failing to flash a custom ROM....
Now I installed xiaomi.eu custom ROMs (weekly/beta), Wifi is working and it's a good ROM.
Click to expand...
Click to collapse
do you think its a problem with persist.img? i think it failed after trying to flash lineageos

@Micdu70
Same problem, your solution worked but after each reboot there is a notification that "the search for the device" (or something like that) is damaged.
The solution is to search for the file persist.img in the rom stock and reflash it alone with TWRP to the partition "persist".
After a reboot it ask to re-calibrate the front camera and everything seems to work perfectly else Widevine L1 -> L3 ...

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte Stock to Android 13

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 herolte (Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models:
International & Canada:
- SM-G930F
- SM-G930FD
- SM-G930W8
Korea:
- SM-G930S
- SM-G930K
- SM-G930L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 herolte to a powerful one with Android 13.
Make sure your phone is herolte/Exynos before going further: in Android, go to Settings > About phone > Check model number is listed below.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v9. Back to TWRP 3.6 until 3.7 is fixed
v8. Android 13, TWRP 3.7
v7. BiTGApps v1, Magisk v25
v6. Switch to MindTheGApps as BiTgapps are dead, TWRP 3.6.2
v5. Add Screen definition override with adb folder + screen sensitivity recalibration, TWRP 3.6.1
v4. Android 12, improve readability, fix ROM download link, TWRP 3.6
v3. Android 11, Magisk 22, fixed the missing OEM unlock description
v2. Moved to LineageOS 17.1 because of low call sound on earpiece with Pixel Experience
v1. Initial release for Android 10 / Pixel Experience
1) DOWNLOAD
- djibe Galaxy S7 herolte pack: https://bit.ly/djibe-galaxys7-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...e-spoofing-ota-updates-for-s7-exynos.4484505/
Download latest build: https://ivanmeler.github.io/devices/herolte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON.
Shut down phone.
Boot in Download Mode: hold Home + Power + Volume- until you see Samsung's logo and release all buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Download mode, do not turn off target".
Connect phone in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.6.2_9-0-herolte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black.
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
Boot in Recovery Mode : Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup Boot, System, Cache, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + GApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS (OPTIONAL)
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Screen saver > Desactivated
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Avdanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 480
// Defaults 1440x2560 and 640
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds

Updated tutorial for LineageOS 17.1 as Pixel Experience call volume is really too low.

Thank you for this guide.
Used with 18.1 + NikGapps core 65 + Magisk and work absolutely fine.

ytccts said:
Thank you for this guide.
Used with 18.1 + NikGapps core 65 + Magisk and work absolutely fine.
Click to expand...
Click to collapse
Hi,
Thanks for sharing.
I'll test your packages and then update tutorial for everyone.
Enjoy.
S7 is damn good.

Hey, thanks for the detailed explanation. Will root and install Lineage in upcoming weekend. Before proceeding with tripping knox, will I be able to use Google Pay and banking apps after installing Lineage ROM? Will wireless charging work? And if I do not want to take backup, will I be able to flash stock firmware in future to revert back to original? There was a time when I was into this stuff rooting and custom ROMS, but now I am too old for it and just being cautious. Thanks again dear.

abhi_qwerty said:
Hey, thanks for the detailed explanation. Will root and install Lineage in upcoming weekend. Before proceeding with tripping knox, will I be able to use Google Pay and banking apps after installing Lineage ROM? Will wireless charging work? And if I do not want to take backup, will I be able to flash stock firmware in future to revert back to original? There was a time when I was into this stuff rooting and custom ROMS, but now I am too old for it and just being cautious. Thanks again dear.
Click to expand...
Click to collapse
Hi,
Thanks for your message.
PLEASE make a TWRP backup before flashing, it just takes 2 minutes.
No idea for wireless charging. You may ask in ROM's thread
Normaly banking apps work with Magisk + MagiskHide module

Hi, updated pack for latest TWRP and Magisk.
Switched ROM to Android 11.

thanks a lot for this guide!
I successfully used it on my SM-G930F with following files:
- twrp-3.5.2_9-0-herolte.img.tar
- lineage-18.1-20210505-UNOFFICIAL-herolte.zip
- MinMicroG-NoGoolag-2.10-20210428084817-signed.zip

Thank you Master especially for the tutorial, Before this I was tried out 10 methods but only this works with oreo.

Hi, I updated tutorial for Android 12

I'v found a bug in a 11.
The battery only charging max 75%, but if I turn off it can be load normally

djibe89 said:
Hi, I updated tutorial for Android 12
Click to expand...
Click to collapse
Thank you kindly this is exactly what I have been looking for. God bless you and Merry Christmas

donnytuco said:
Thank you kindly this is exactly what I have been looking for. God bless you and Merry Christmas
Click to expand...
Click to collapse
Glad you liked it ! Merry Christmas

Thanks for this excellent instruction.
Maybe you'd like to consider one small change in part 6 - Flash ROM, Gapps, Magisk.
According to the devs of BitGapps they suggest to do a reboot to recovery after flashing of ROM:
GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project
The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.
github.com

bgsdeluxe said:
Thanks for this excellent instruction.
Maybe you'd like to consider one small change in part 6 - Flash ROM, Gapps, Magisk.
According to the devs of BitGapps they suggest to do a reboot to recovery after flashing of ROM:
GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project
The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Done, thanks !!

Could you add part 9) UPDATE, please. In case of a newer rom.

blinthor said:
Could you add part 9) UPDATE, please. In case of a newer rom.
Click to expand...
Click to collapse
Hi, then you have to "Clean flash"

djibe89 said:
Hi, then you have to "Clean flash"
Click to expand...
Click to collapse
I do not know if I understand correctly.
1. Install new rom
2. Wipe Dalvik, Cache
What about BitGapps. Do you install after rom or not?

blinthor said:
I do not know if I understand correctly.
1. Install new rom
2. Wipe Dalvik, Cache
What about BitGapps. Do you install after rom or not?
Click to expand...
Click to collapse
- Backup
- Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy

djibe89 said:
- Backup
- Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Click to expand...
Click to collapse
Thanks