[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S5 mini G800F to Android 9 Pie
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S5 mini G800F/kminilte (Exynos) Any version to Android 9 Pie
This detailed step-by-step guide helps you transform your Samsung Galaxy S5 mini G800F to a powerful one with Android 9.
Verify your phone is G800F before going further : in Android, go to Settings > About > Check model is G800F.
If not, quit this tutorial.
CHANGELOG
v10. TWRP 3.6, check links
v9. Latest TWRP + Magisk 23 + ROM
v8. TWRP 3.5, Magisk 22
v7. Updated pack for TWRP recovery 3.4.0-0 + ROM download link + Samsung USB drivers, Magisk for root, MagiskManager-v8.0.2
v6. Updated pack for TWRP recovery 3.3.1-0 + IMEI backup
v5. Updated tutorial and pack to Android 9 Pie
v4. Updated pack with Odin 3.13.1, TWRP Recovery 3.2.3-0 and Spookcity kernel 6.0-1
v3. Added Google Play certification, TWRP recovery 3.2.1-0
v2.1. Updated Spookcity kernel to v6
v2. Updated to Android 7.1 Nougat, TWRP3.1.1-1, Spookcity kernel 5, overclock, fixed bootloops
v1. Initial release for Android 6
1) DOWNLOAD
- djibe Galaxy S5 mini G800F pack v3: http://bit.ly/G800Fdjibepackv3
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.0_9-0 official recovery + Magisk 23). Unzip files.
+ ROM Unofficial Lineage OS 16: https://forum.xda-developers.com/galaxy-s5-mini/development/rom-lineageos-16-0-t3868612
Download latest build here: https://androidfilehost.com/?w=files&flid=64356&sort_by=date&sort_dir=DESC
### ROM perfectly working except Encryption, Video recording doesn't work in all apps or with all camera applications
+ OpenGApps ARM 9 pico : http://opengapps.org/?arch=arm&api=9&variant=pico
+ a microSD card. Copy ROM, Gapps and Magisk on microSD card (FAT32 format) and insert it in phone.
+ Charge phone to 100 %
2) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Erase your Google Account: Go to Settings > Account > Google and erase it.
3) FLASH TWRP 3.6 RECOVERY
Shut down phone.
Boot in Download Mode : hold Home + Power + Volume- for 3 seconds and release.
Confirm with Volume+.
Phone now displays: Downloading, do not turn off target.
Connect phone in USB, wait for bootloader 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.0_9-0-kminilte.img.tar
### Warranty will be Void after next click ###
Click Start.
When PASS! success green message appears.
Wait a few seconds, then hold again Home + Power + Volume- to reboot phone.
Let phone restart then shut it down.
4) BACKUP IMEI PARTITION
Boot in Recovery Mode: Hold Home + Power + Volume+ until you see the Samsung logo then release and wait a few seconds for TWRP recovery to boot.
If it asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
Select all partitions in order to be able to restore phone to it's original state.
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 EFS, Boot and System.
Now type Select Storage > Select Micro SD card and confirm with OK
Now Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Connect phone or microSD to PC.
Open microSD folder and backup TWRP folder to a safe place.
Youe /efs partition is now safe (+/- other partitions if you need to fix some crashes).
5) WIPE PARTITIONS
Go to Wipe > Format Data
Type yes and confirm with bottom right Check icon.
Then 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,
then back.
Go back to TWRP Home screen > Reboot > Recovery and Swipe to confirm.
At reboot, if TWRP asks for Keep System Read Only ? > Swipe to Allow Modifications.
6) FLASH ROM, GAPPS AND MAGISK
Back to TWRP Home menu. Then tap on Install > choose LOS16*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > open_gapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### OPTIONAL FOR ROOT
Go to Reboot > Recovery.
Once phone rebooted, go to Install > Magisk.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
7) ROOT ACCESS
No extra steps for root. Magisk starts with Android.
Open Magisk Manager app to manage root permissions.
8) DON'T USE BUILT-IN CAMERA APP
Using LineageOS default camera app will crash when switching from photos to videos.
Use Simple Camera app included (or Google Camera, Footej camera).
9) EXTRA
You can use GPS Status & Toolbox app for faster GPS fix.
For faster phone, go to Settings > About.
Tap 7 times on Build number.
Go to Settings > System > Avdanced > Developer options.
Set Windows animation scale, Transition animation scale and Animator duration scale to 0.5x.
For better battery longevity, set Dark mode. Settings > Display > Avanced > Style > Style > Dark
And Dark mode > Dark.
Enjoy,
djibe
Thanks : @panzerknacker, LOS Team, TWRP Team, @spookcity138, @hennymcc, @rodman01, @Friedensfurz, @cschsz, @ayke, @CTXz, @psyafter
Update: Thanks to C0rn3j in the TWRP thread I got it to work with heimdall and pulling the battery.
Great guide, worked well for me except rebooting to TWRP recovery failed with the kernel length error. Tried using the previous version of TWRP and then with the stock kernel but both failed with the same error. Does TWRP work with LOS14.1 on kminilte?
Nice guide! I have been using custom roms on my mini for about a year and never knew mutch about that I can change the filesystem.
However sometimes my phone becomes very laggy, and unresponsive.(Maybe memory settings problems) I tried several kernel settings but did not find the best yet.
What is Your opinion? What are the best kernel settings to our model?
Evos11 said:
Nice guide! I have been using custom roms on my mini for about a year and never knew mutch about that I can change the filesystem.
However sometimes my phone becomes very laggy, and unresponsive.(Maybe memory settings problems) I tried several kernel settings but did not find the best yet.
What is Your opinion? What are the best kernel settings to our model?
Click to expand...
Click to collapse
Hi, try not to overclock too much, like 1600 Mhz, cause overheating can slow down phone.
What other parameters did you try ?
rimc100 said:
Update: Thanks to C0rn3j in the TWRP thread I got it to work with heimdall and pulling the battery.
Great guide, worked well for me except rebooting to TWRP recovery failed with the kernel length error. Tried using the previous version of TWRP and then with the stock kernel but both failed with the same error. Does TWRP work with LOS14.1 on kminilte?
Click to expand...
Click to collapse
Hi. Yes LOS 14.1 and TWRP 3.1 both work very well on my dad's G800F.
You can't boot in TWRP ?
What kernel do you use ?
djibe89 said:
Hi. Yes LOS 14.1 and TWRP 3.1 both work very well on my dad's G800F.
You can't boot in TWRP ?
What kernel do you use ?
Click to expand...
Click to collapse
I got it working now. All is well.
rimc100 said:
I got it working now. All is well.
Click to expand...
Click to collapse
Glad to hear it.
Enjoy
Latest version of tutorial is available to obtain GOOGLE MOBILE SERVICES (GMS) CERTIFICATION
+ updated TWRP recovery
+ updated Kernel
Do you think LOS is stable enough to propose it in my tutorial ?
Thank you for the guide! It worked really well. There were a number of details I didn't know, like the performance difference between filesystem formats, and everything was very step-by-step and super helpful.
One issue: TWRP 3.2.1 doesn't work with the 6.0 Spookcity kernel. You have to disable the device check to get it to work. Looks like Panzerknakker uploaded one with that change: https://forum.xda-developers.com/showpost.php?p=77725358&postcount=285
djibe89 said:
Do you think LOS is stable enough to propose it in my tutorial ?
Click to expand...
Click to collapse
Are you talking about LOS 15? If so, no IMO. It was stable but buggy. I'm actually downgrading back from 15.1 to 14 due to issues with internal storage and battery consumption, and sometimes it would stop charging and require a hard restart..
Frostcrystal said:
Thank you for the guide! It worked really well. There were a number of details I didn't know, like the performance difference between filesystem formats, and everything was very step-by-step and super helpful.
One issue: TWRP 3.2.1 doesn't work with the 6.0 Spookcity kernel. You have to disable the device check to get it to work. Looks like Panzerknakker uploaded one with that change: https://forum.xda-developers.com/showpost.php?p=77725358&postcount=285
Are you talking about LOS 15? If so, no IMO. It was stable but buggy. I'm actually downgrading back from 15.1 to 14 due to issues with internal storage and battery consumption, and sometimes it would stop charging and require a hard restart..
Click to expand...
Click to collapse
Hi, thank you very much for your help.
I'll fix the Kernel thing and stick to LOS 14.
Thanks,
djibe
v4. Updated pack with TWRP Recovery 3.2.3-0 and Spookcity kernel 6.0-1
Update: I'm having some major issues with lag on my device. 15 seconds to open Chrome, occasional overheating, high CPU usage on small things, etc.
I've had LOS14.1 (a slightly older version) on this device before, minus the different filesystem format and the Spookcity kernel, and not experienced this issue. So I'm thinking about rolling back some of the changes to see which ones were the cause.
Is there an unmodified version of the kernel out there?
Frostcrystal said:
Update: I'm having some major issues with lag on my device. 15 seconds to open Chrome, occasional overheating, high CPU usage on small things, etc.
I've had LOS14.1 (a slightly older version) on this device before, minus the different filesystem format and the Spookcity kernel, and not experienced this issue. So I'm thinking about rolling back some of the changes to see which ones were the cause.
Is there an unmodified version of the kernel out there?
Click to expand...
Click to collapse
Hi,
I didn't experience that but we never know.
To have a fresh system, reboot to TWRP recovery. Wipe cache + system.
Flash LOS, addonsu, OpenGApps.
Wipe cache and reboot.
Thank you for posting this guide. Much appreciated.
Was thinking of getting a Galaxy S i9000 ready for moms but didn't quite understand all the dated guides/roms so decided to buy a 2nd hand s5 mini which now works like a charm!
(struggled a bit with the power off/power on after twrp flash but removing battery for shutdown and holding home+power+vol+ a little longer works!)
rewre said:
Thank you for posting this guide. Much appreciated.
Was thinking of getting a Galaxy S i9000 ready for moms but didn't quite understand all the dated guides/roms so decided to buy a 2nd hand s5 mini which now works like a charm!
(struggled a bit with the power off/power on after twrp flash but removing battery for shutdown and holding home+power+vol+ a little longer works!)
Click to expand...
Click to collapse
Hi, you are very welcome for this tuto.
I like when phones don't go to the rubbish !
You are quite right, Galaxy S2 i9100 can be tricky when USB is badly recognized by the PC. And to be honest its performances are low.
Hope you had a merry christmas,
cheers
Hi, i have this device now. ¿Which rom its the most stable and smooth?
Zsheoran said:
Hi, i have this device now. ¿Which rom its the most stable and smooth?
Click to expand...
Click to collapse
Hi,
use the LineageOS build from the 1st post of this thread.
My mother is very happy with it !
Enjoy
Tutorial is up to date
djibe89 said:
Tutorial is up to date
Click to expand...
Click to collapse
Hi,
I have followed the steps and it works pretty well.
However i have some issues:
1. Mobile network is not detecting unless i switch on then off Airplane mode
2. The STK is not working when you use online banking and other isp services.
Related
UPDATE - Flashback 10.3 (12/07/2011) - See Downloads (below)
STANDARD DISCLAIMER:
USE AT YOUR OWN RISK. By running this firmware, you agree that there is the possibility that you may brick your device. You agree that only you are responsible and no one else is responsible for supporting you if that occurs.
Acknowledgments
Roebeet, Mrguy, Pershoot, Zebwen, Clemsyn and all the Adam and VEGA developers, for this excellent port. If you have contributed something I used let me know and I will add you here.
Pre-requisites
1. Setup and learn how to use nvflash. This is your backout in case something bad happens, so I would recommend you understand how to use this, in advance.
2. Have your device on a stock 1.2-based ROM / mod baseline. For example, build 4349 is the latest 1.2-based stock ROM, as of this writing.
NVFlash
-NVFlash rev5 by tlb1961 (Detailed Instructions for Windows and Linux included in download)
Installation for 1.2-based stock (also, see Changelog)
Options for Installing Flashback:
Option 1 (Update)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe cache partition
2. Advanced > Wipe Dalvik cache
3. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
4. Install from SDCard
5. Choose zip from SDCard
6. Navigate to and choose Flashback-10.X.zip
7. Accept/Choose Flashback-10.X.zip
8. Backspace/Return key (back to Main menu)
9. Reboot system
Option 2 (Clean)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe data/Factory reset
2. Wipe cache partition
3. Advanced > Wipe Dalvik cache
4. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
5. Install from SDCard
6. Choose zip from SDCard
7. Navigate to and choose Flashback-10.X.zip
8. Accept/Choose Flashback-10.X.zip
9. Backspace/Return key (back to Main menu)
10. Reboot system
Option 3 (Wipe & Format)
Download/Copy Flashback-10.X.zip to Internal SDCard (USB storage)
Shutdown and boot into ClockworkMod recovery.
1. Wipe data/Factory reset
2. Wipe cache partition
3. Advanced > Wipe Dalvik cache
4. Backspace/Return key (back to Main menu) < Very Important Here [DO NOT REBOOT RECOVERY]
5. Moints and Storage:
> Format boot
> Format cache
> Format data
> Format system
> Format sdcard - OPTIONAL (FOR ADVANCED USE ONLY)
6. Backspace/Return key (back to Main menu)
7. Install from SDCard
8. Choose zip from SDCard
9. Navigate to and choose Flashback-10.X-signed.zip
10. Accept/Choose Flashback-10.X-signed.zip
11. Backspace/Return key (back to Main menu)
12. Reboot system
Disaster recovery - 'tlb1961' NVFlash (see above)
Flashback Team Members
HiTekRedneck
jazzruby
OtherGuy
rowwor
Sharpe351
TEK112
tlb1961
tlbardelljr
Downloads
Flashback 10.3 (updated 12/07/2011)
Download Link: http://dev-host.org/dn0au4ajdokt/Flashback-10.3-signed.zip
MD5: ce7898ecb48b0a0a9d0b0d45d99b9669
Pershoot's kernel 2632.48 11/24/2011 (included in Flashback 10.3)
Download Link: http://dev-host.org/ol6timuj4aw1/pershoots_2632.48_gb_newbl-112411-signed.zip
MD5: 6606eb179ff22d4738da0b62e14187bd
Clemsyn's kernel Honeycomb Trial 5
Download Link: http://www.mediafire.com/?7s7c1anfv1pnfe3
Changelog
Flashback (see Post #2)
Pics
Changelog:
Flashback 10.3
Updated kernel/WiFi modules
Recommended install method for Flashback 10.3:
'Update' install for 10.2 > 10.3
'Clean' install for all others
Flashback 10.2
Files added:
GalleryNew3DGoogle
Files updated:
Browser (Homepage)
Superuser (3.0.7) - If doing an 'Update' install, you must 'Uninstall update' from Settings > Applications > All
framework-res (Wallpaper)
updater-script (corrected 1 line)
boot.img (new kernel)
Files removed:
TitaniumBackup (issues) - If doing an 'Update' install, you must 'Uninstall update' from Settings > Applications > All
StatusbarToggle (issues)
Wallpapers (app not stock)
[/system/data] folder (contains 3rd party appps and will provide as a separate download)
Recommended install method for Flashback 10.2:
'Clean' install, due to system apps, i.e. TitaniumBackup and Superuser
'Update' install, (for experienced users and from 10.1 only) - You must 'Uninstall update' for TitaniumBackup and Superuser from Settings > Applications > All
-JR-
loving it
The latest update is great! Still having a problem with the flashplayer causing crashes though..any recommendations other than the hacked apk that is available in the build?
Thanks JR,
This will always be the ROM running on my GTAB. You are a great asset to the gtab community!
tlbardelljr
This isn't a new problem (I've had it with all the Honeycomb ROMs I've used), but when I hold the power button and choose "Recovery", my G Tablet doesn't boot into recovery, it just reboots normally. I can only get into recovery by holding the volume up button while rebooting. Is this normal? It isn't really a big deal, but I thought I'd report it.
I'm running Flashback 10.3.
JazzRuby, Thank you so much for posting an update for the Gtab, any new ROM is a welcome, but more so for a HC!!!
So again Thanks!!
Just got the gtab from a friend. This ROM is amazing, but no working flash player, can't play anything. Any ideas?
Seanbest said:
Just got the gtab from a friend. This ROM is amazing, but no working flash player, can't play anything. Any ideas?
Click to expand...
Click to collapse
Flash player DOES work (kind of). If you long press on the area where the flash "would be." And then press in the upper-left of the area, you can make the flash object full screen, where it WILL work!
which version?
miker2431 said:
Flash player DOES work (kind of). If you long press on the area where the flash "would be." And then press in the upper-left of the area, you can make the flash object full screen, where it WILL work!
Click to expand...
Click to collapse
Are you using the hacked flash.apk?
Nope, just update or fresh download the newest version that shows up in the market and most browser pages with flash videos will play (you can hear them but prob not see them) then you kind of have to "guess" where that "full screen" button is on the video window, and if you hit it spot on, it should launch the flash video full screen. It's a *****, but it works. I'm going back and reloading some of the other HC roms to see which one I can live with for now.
Hey everyone!
Just put this on my gtab, and i have an issue. When i go to install an app, it causes a reboot from the splash screen, and when it comes back up, the wifi doesnt work(gives an error) until i restart the tablet.
Any ideas?
Thanks!
-Steve
mq1991 said:
Hey everyone!
Just put this on my gtab, and i have an issue. When i go to install an app, it causes a reboot from the splash screen, and when it comes back up, the wifi doesnt work(gives an error) until i restart the tablet.
Any ideas?
Thanks!
-Steve
Click to expand...
Click to collapse
Hi Steve,
Can you be a little more specific, i.e. previous ROM, install method, what app, etc...
-JR-
timbck2 said:
This isn't a new problem (I've had it with all the Honeycomb ROMs I've used), but when I hold the power button and choose "Recovery", my G Tablet doesn't boot into recovery, it just reboots normally. I can only get into recovery by holding the volume up button while rebooting. Is this normal? It isn't really a big deal, but I thought I'd report it.
I'm running Flashback 10.3.
Click to expand...
Click to collapse
This is a known issue with the Shutdown.apk (app), unfortunately no resolve at the moment, but will look into it further.
Thanks,
-JR-
Thanks for the quick repsonse!
Alright, well a bit of a rollercoaster here..
I went through and followed this guide to get my tablet up to 4349.
This one
Then, I attempted to install CWM .8 to manage roms and such.
That did not work, it soft bricked the device, so i went and NVFlashed it back, and went through the process of getting it back to 4349.
I then used the included recovery (v3?) to install Flashback.
Any tips on getting CWM to go on along with 4349?
EDIT: So far its happened with every app, it downloads fine. When it switches to "installing..." the tablet goes to the Flashback splashscreen.
mq1991 said:
Thanks for the quick repsonse!
Alright, well a bit of a rollercoaster here..
I went through and followed this guide to get my tablet up to 4349.
This one
Then, I attempted to install CWM .8 to manage roms and such.
That did not work, it soft bricked the device, so i went and NVFlashed it back, and went through the process of getting it back to 4349.
I then used the included recovery (v3?) to install Flashback.
Any tips on getting CWM to go on along with 4349?
Click to expand...
Click to collapse
OK, I think I follow you, your currently running Flashback 10.3, correct?
If so, you can flash/install ClockworkMod 3.0.2.8 rev5 internally.
FB 10.3 includes the recovery binaries for Stock and ClockworkMod, you just need to flash/install via terminal.
Open/Run Terminal Emulator and type the following:
$ su - become Superuser
# cwmrecovery.sh - will flash/install ClockworkMod 3.0.2.8
# fixrecovery.sh - will flash/install Stock recovery
Terminal Emulator: https://market.android.com/details?id=jackpal.androidterm&hl=en
Thanks! I will try that out and post back!
Haha yeah I was, Im just gonna start from the beginning to try and iron out any problems I may have caused.
Also, the kernel in the first post, will that help improve stability? Or is it simply the overclock?
Thanks for your help!
mq1991 said:
Thanks! I will try that out and post back!
Haha yeah I was, Im just gonna start from the beginning to try and iron out any problems I may have caused.
Also, the kernel in the first post, will that help improve stability? Or is it simply the overclock?
Thanks for your help!
Click to expand...
Click to collapse
First of all, make sure you're on 1.2 bootloader; if you've already NVFlashed 4349 then you are.
Second, download and flash/install this ClockworkMod:
http://dev-host.org/g4e68tsmgdlp/gTab.cwm.3028.1.2.zip
If you already got ClockworkMod 3.0.2.8 rev5 then skip the above, if not, and you have Stock recovery, then rename to update.zip and flash.
Third, use the 'Clean' install method in the OP.
Flashback 10.3 already has pershoot's kernel baked in, the 2 kernel pkgs in the OP are to allow trying/testing between the two.
-JR-
Could you point me in the direction of finding that version of NVFlash? Im using one that goes to a very old version of TnT and then i need to wait for an OTA update.
Ive searched on the forum but havent turned up much.
That makes more sense. Thanks for all your help. I dont want to come across as a noob, but for some reason this tablet has been giving me the most trouble of all getting this stuff right. haha
---------- Post added at 09:46 PM ---------- Previous post was at 09:27 PM ----------
*facepalm* All I had to do was reinstall Flashback.
Thanks so much for your help! It no longer restarts when I install apps.
So i think the problem was down to that I didnt use CWM to install it, after I used NVFLASH v5 it installed that new version of CWM you mentioned. I then did a CLEAN install of Flashback and so far so good! I hope this can help someone else out as well.
Looking good JR. Keep up the great work!
Is anyone else missing the \system\ data\ folder where the hacked adobe flash apk
I'm coming from flashback 10.1 upgrade install, wiped cache and dalvik cache
Sent from my Nexus S 4G using xda premium
hello everyone,
i have a nexus 7 2012 tab i have had for almost 3 years now and ever sense the last version of jellybean or the first version of kitkat the tablet will eventually lag after a fresh install after 3 to 4 weeks. i have had my tab rooted for over a year now and have tried many versions of stock roms to cyanogen and slimroms and i even tried converting the filesystem to F2FS but it just seems every rom i try it will just get to a point where it lags so much its crippled. right now i am on slimbean 4.3 build 2.2 official 1776 with ext filesystem. i am just trying to get some feedback if anyone knows a rom that is nexus 7 2012 friendly before i reinstal again as i am about to try downgrading to a slimrom version of 4.1 which they say was the original version the tabbed shipped with
any input would be apprecialted
I use stock 5.1 + latest Franco kernel with /data and /cache formatted to F2FS. It works flawlessly for me. Very fast and responsive. No lags at all. For me, it is as fast as 4.4.4, if not faster.
Fobos531 said:
I use stock 5.1 + latest Franco kernel with /data and /cache formatted to F2FS. It works flawlessly for me. Very fast and responsive. No lags at all. For me, it is as fast as 4.4.4, if not faster.
Click to expand...
Click to collapse
how long have you been using it with that configuration? i ftried using F2FS with lego's kernel with a version of slimkat. it made my tablet speedy but after a month it just slowed back to a crawl
I'm not sure for how long exactly, but it's a long time. I'd say two or three months at least.
Correction: I'm using it since Android 5.1 is out, I don't know when that happened.
cool man would you be able to link to me the directions you used to install F2FS with from your post i'm not sure how to install F2FS with stock. android. i do want to use 5.1 though
I don't remember where I got the instructions so I can't link it. I think I went like this:
1) download the official factory image from google (https://dl.google.com/dl/android/aosp/nakasi-lmy47d-factory-ee97ce42.tgz)
2) extract it
3) flash it using the flash-all script
4) let the tablet boot android 5.1, skip the wifi and google account setup
5) reboot to bootloader/fastboot
6) download latest TWRP recovery ( http://dl.twrp.me/grouper/twrp-2.8.6.0-grouper.img)
7) flash it using adb: "fastboot flash recovery twrp-2.8.6.0-grouper.img"
8) using the volume and power button boot to recovery
9) wipe -> advanced wipe > select cache -> repair or change file system --> change file system --> f2fs
10) wipe -> advanced wipe > select data -> repair or change file system --> change file system --> f2fs
11) in TWRP select reboot --> bootloader
12) download Franco kernel(http://kernels.franco-lnx.net/Nexus7/5.1/boot-r82.img)
13) flash franco kernel using adb command "fastboot flash boot boot-r82.img"
13) If it doesn't work that way, download the kernel in zip format(http://kernels.franco-lnx.net/Nexus7/5.1/zips/franco.Kernel-nightly-r82.zip)
and flash it using recovery's sideload(advanced-->adb sideload) --> to sideload type this adb command: "adb sideoload franco.Kernel-nightly-r82.zip"
14) After you've flashed kernel, normally reboot the system and everything should be fine.
If anything is unclear, please feel free to ask. I repeat, I don't exactly remember how I did it, but I think it goes the way I wrote now.
Note: Everything you do, you do on your own risk.
Good luck!
thanks for posting the instructions i will give it a try
22 May 2016
version 0.32 is considered more stable than 0.33
default settings should be fine for both new installs and updates
Root Junky Video
Amazon Fire 5th gen 7in Slim Rom install on Fire OS 5 1 1 with FlashFire App
https://youtu.be/NaCBSuUuhRE
Official Chainfire FlashFire thread
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Google+
https://plus.google.com/u/0/communities/116661625291346007584
Alt downloads
https://www.chainfire.eu/
https://download.chainfire.eu/956/FlashFire/FlashFire-v0.31-20160405175326.apk
http://www.apkmirror.com/apk/chainfire/flashfire/
- Fresh Installation from FlashFire 0.27
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Ensure Auto-mount and Mount /system read/write are UNCHECKED
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Ensure Auto-mount is UNCHECKED
- Ensure Mount /system read/write is CHECKED
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
Upgrading from FlashFire 0.27
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Ensure Auto-mount is UNCHECKED
- Ensure Mount /system read/write is CHECKED
- Click the Red + again and choose 'Wipe'
- ONLY tick Dalvik and Cache.
- Press the big FLASH button.
Installing gapps on Stock Rom Root Required
Wiping should not be necessary.
[url]http://opengapps.org/[/URL] Arm | 5.1.1 | Micro, Nano or Pico
Instructions
Install the app
Download gapps
Open FlashFire app
Allow root access
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to Gaaps.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
Shouldn't need to check Auto-mount
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will see normal scripts for gapps install
Device will reboot
Changelog
29 April 2016
Added link to
http://www.apkmirror.com/apk/chainfire/flashfire/
13 May 2016: Current Version is 0.33
Unless otherwise noted, use newest version.
Files may need to be on internal storage, rather SD card.
16 April 2016
Added links to ChainFire's Blog...
Cleaned up post abit
Added instructions from CM12.1
20 March 2016
Due to so many brick devices, I recommend that those with 5.1.X bootloaders
do not install cm12.1
nexus and slim roms have caused far fewer issues
20 Feb 2016
Note:There is some risk if using on 5.1.X Bootlader
Some have reported bricking, when trying to install a rom, unclear what the cause is.
I'm still on 5.0.1 bootloader, and I am not going to update to 5.1.1
I have not seen a clear reason as to why Flashfire is bricking some and not others.
With the locked bootloader, Flashfire should not effect the stock recovery, but yet that seems to be the result in some cases.
There is not failsafe way to install any rom with Flashfire.
Davey126 said:
Fully concur. Additional thoughts:
- leaving wipe at the bottom is just asking for trouble
- dirty flashes are not a great idea when switching roms
- recent FlashFire versions (0.26+) have several changes targeted at CM
- the most serious issues seem to occur with older versions of FlashFire
- wipe options make a difference; consult the rom OP for best selections
- stick to recommended zip options (see rom OP for guidance)
I also believe (but have no decisive evidence to prove) that evironmental complexity plays a role. Suggestions:
- make sure current rom is stable before updating or flashing a new rom
- minimize the number of background tasks before launching FlashFire
- when switching roms skip GAaps on the first pass. A package of choice (preferably nano) can be flashed later with individual apps added from the Play Store as needed. This does complicate the process as FlashFire will need to be sideloaded on the new rom for the initial GAaps flash. Best leave a copy of the FlashFire apk and GAaps zip in a location that won't get overwritten.
Click to expand...
Click to collapse
6 Jan 2016: Be sure that wipe option is listed first,
FlashFire places it as last task,
which will wipe system, and rom will no longer be usable.
and likely the cause of the bricking of fires with the 5.1.1 bootloader.
23 Jan 2016
Don't try to install a custom rom with a low battery
Original post #1
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
next
sd_shadow said:
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
Wonder if it will work from within FireOS 5.0.1.
4t701 said:
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
Click to expand...
Click to collapse
I just forced power off, and then I booted it into fastboot mode.
Sent from my KFFOWI using Tapatalk
Failed to install stock over SlimLP, just reboots to SlimLP
Could just need a different install script for stock.
blueberry.sky said:
Wonder if it will work from within FireOS 5.0.1.
Click to expand...
Click to collapse
I haven't tried installing a rom in stock yet.
In Stock 5.0.1, restore SlimLP worked, but it took a while, I thought it was stuck, ,but just left it, came back later and it was running SlimLP just as I backed up
backup was created with FlashFire, haven't tested Twrp created backup with FlashFire, but don't think it will be compatible.
4t701 said:
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
Click to expand...
Click to collapse
i wonder if I just didn't wait long enough? Didn't time it, thought it was about 10 mins?
Edit: in reference to the install
I tried to use flash fire to create a backup of my modified stock from, and it ran some script, then went to a blank screen with flash fire on the top. It stayed like that for about 30 minutes before it rebooted, and there was no backup file. I thought I would try it. I would like to see if I can flash cm12.1 on stock. It was a $35 tablet, I don't mind trying stupid stuff with it.
Sent from my SPH-L710T using Tapatalk
pbailey212 said:
I tried to use flash fire to create a backup of my modified stock from, and it ran some script, then went to a blank screen with flash fire on the top. It stayed like that for about 30 minutes before it rebooted, and there was no backup file. I thought I would try it. I would like to see if I can flash cm12.1 on stock. It was a $35 tablet, I don't mind trying stupid stuff with it.
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
Blimey that's a long wait. Totally sure it didn't back it up anywhere, seems odd given how long it took?
Pond-life said:
Blimey that's a long wait. Totally sure it didn't back it up anywhere, seems odd given how long it took?
Click to expand...
Click to collapse
I got it to back up and restore on stock, now to try to install cm12, worst case scenario, I have to hook it up to my computer and install it through adb and twrp
Sent from my SPH-L710T using Tapatalk
I dirty flashed CM latest build, gapps.zip, and superSU.zip yesterday. Everything worked perfectly. It only took like a minute to flash all 3 of those zips. No frozen screen or unresponsiveness. No issues with the new CM install or gapps.
Only things I did different from you @sd_shadow was I only wiped dalvik cache and cache partition, I did check 'automount' feature on all 3 of my .zips, and I didn't use the EverRoot to inject superSU into system (as I preferred to just flash the superSU.zip)
sd_shadow said:
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse
Installing cm12 on stock didn't work. It stuck on the blank flas fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh weel. It was worth a shot
Sent from my SPH-L710T using Tapatalk
pbailey212 said:
Installing cm12 on stock didn't work. It stuck on the blank flas fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh weel. It was worth a shot
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
sd_shadow said:
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse
Did you guys use the 'automount' feature or no?
So I tried to flash SlimLP over my CM install...
-I wiped dalvik and cache partition.
-flashed SlimLP, checked 'automount'
-flashed my gapps.zip, checked 'automount'
-flashed SuperSU.zip, checked 'automount'
-FLASHED
-system reboots but hangs at boot animation forever like @pbailey212
So it appears FlashFire is only really useful if you are just using it to update your current CM or SlipLP install (or to flash xposed.zip or your gapps). Doesn't look like it can be used to flash a different ROM from what you are already on. Oh well, it's still pretty useful. Just wish it woulda worked for flashing a different ROM. That or our BL get unlocked so TWRP could be installed. If that ever happens this would be the perfect budget tablet. [emoji41]
4t701 said:
So I tried to flash SlimLP over my CM install...
-I wiped dalvik and cache partition.
-flashed SlimLP, checked 'automount'
-flashed my gapps.zip, checked 'automount'
-flashed SuperSU.zip, checked 'automount'
-FLASHED
-system reboots but hangs at boot animation forever like @pbailey212
So it appears FlashFire is only really useful if you are just using it to update your current CM or SlipLP install (or to flash xposed.zip or your gapps). Doesn't look like it can be used to flash a different ROM from what you are already on. Oh well, it's still pretty useful. Just wish it woulda worked for flashing a different ROM. That or our BL get unlocked so TWRP could be installed. If that ever happens this would be the perfect budget tablet. [emoji41]
Click to expand...
Click to collapse
Well sd-shadow did get it to flash from CM to Slim in the second post on the thread, maybe you needed to wipe more as he did.
---------- Post added at 06:04 PM ---------- Previous post was at 06:00 PM ----------
pbailey212 said:
Installing cm12 on stock didn't work. It stuck on the blank flash fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh well. It was worth a shot
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
Installing slim on stock did work. And restoring my stock back up after realising I really didn't like slim gapps.
Pond-life said:
Well sd-shadow did get it to flash from CM to Slim in the second post on the thread, maybe you needed to wipe more as he did.
Click to expand...
Click to collapse
Oh, yeah...I completely missed @sd_shadows' post (#2) And yeah I didn't wipe system apps so I guess that's probably why it didn't work for me. Was gonna try that later after I had made a proper backup.
I think my problem was I installed open gapps normal, I should have done pico. The normal is too large to fit in the system partition. I bet that's why it hung up on the flash fire screen. Its the same thing that happened when I tried to create a backup in the eternal storage
Sent from my KFFOWI using Tapatalk
Pond-life said:
Installing slim on stock did work. And restoring my stock back up after realising I really didn't like slim gapps.
Click to expand...
Click to collapse
So with FlashFire it is possible to flash custom roms without access to the fastboot boot command. If we can get root in 5.1.1 then we are back in business! Safestrap of course would be much better, safer.
Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance
1.No need to flashing blod
2.remove any passwords or screen lock before flashing
3.boot into fastboot make sure bootloader is unlocked
4.flash the twrp recovery provided in the forum u can't use the usual one
5.after installing recovery wipe everything from the advance wipe except internal storage
6.locate and install the rom don't flash the gapps its already included
7.before booting in the system make sure to wipe ur data from wipe or ur phone will not boot
8.time to enjoy!!!
varunvrk said:
Hey I want to try pixel experience rom in my nexus 6p but the installation guide there is too complex can someone from the forums break it down and explain so I can install it and also my device is a 8core model so I am not sure weather or not I need a BLOD patch and why I need a custom recovery (other then the normal custom recovery) Thanks in advance
Click to expand...
Click to collapse
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.
Champdroid said:
It is quite simple. You'll just need to do a bit if reading about adb and fastboot and make sure you follow these steps methodically. You do not need BLOD patch. You need the custom recovery version from the pixelexperience thread because of the way files are encrypted.
1 . Go to settings - system - about phone. Tap on build number 7 times until you see a pop up saying developer options enabled.
2. Go to settings - system - advanced - developer options. In there you want to enable oem unlocking and usb debugging.
3. Go to settings - security. Remove all device security so it's just swipe to unlock.
4. Follow this guide to setup google drivers, adb, fastboot and unlock the bootlader https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
5. Download latest rom version and twrp recovery version from pixelexperience thread to your pc and follow instruction in above guide for flashing twrp via fastboot.
6. Boot into your custom recovery (hold power + volume down while phone is off, use volume keys to select recovery, power for enter) ignore warning screen.
7. Go to backup. Select system, data and boot. Name it something like stock_todaysdate. Swipe to create backup. Reboot system.
8. Connect phone to pc. Through pc find twrp folder in phone, find your backup, copy to pc for safe keeping (this can restore your phone to how it was if anything goes wrong). Copy the rom zip you downloaded to your phone's internal storage.
9. Boot back into recovery. Go to wipe. Wipe everything except internal storage. Go to install. Locate the rom zip file and install it. Go to wipe again. Select format data and confirm.
10. Reboot system and wait for rom to boot this can take a while. Once booted leave your phone alone for a few minutes then you are good to go. If all is well make another backup and store on pc.
Click to expand...
Click to collapse
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this
mojorisin7178 said:
That is the best instructions I have seen in a while. I kinda figured that that was how to do it but I am not confident in my abilities. This confirms what I thought needed to be done.
I am not new to flashing I have been doing it since the LG g2x. But I did take a 3 year break from flashing and now everything is a little different.
Anyway thank you for this
Click to expand...
Click to collapse
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.
Champdroid said:
Pleasure mate glad you appreciate it.
I also took a long break. Started back in the HTC sensation days! It's amazing how much everything changes when you don't check in for a while. Magisk for example blows my mind.
Click to expand...
Click to collapse
Yeah magisk is crazy the devs here at xda can do anything. They really are the best of the best. Everything I know I learned here on xda. I just read they are working on a new way to root at the kernel level so it's built in right from the when it's compiled. That's just crazy smart.
[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