Related
IMPORTANT: THE S3 MINI MODULE SUPPORTS 4 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
GT-8190T LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
***reserved if needed***
thanks developer!!!!!!!!!!!!!!!!!!!
will report feedback after tested
Great work MSKIP the safest way and easy way to root and stock your phone thank you testing in progress.
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
you should pm mskip he will link you a download
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Thanks we are waiting them...
sent from the super siii mini GT-I8190 using xda premium app.
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
Sending you a link to the test file.
Mark.
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
Now uploading files and waiting for testers
Mark.
Click to expand...
Click to collapse
would like to test, thanks
Click to expand...
Click to collapse
funiewski said:
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
would like to test, thanks
Click to expand...
Click to collapse
Pm me as soon as you are available to test and I will send you the installer link. It needs to be tested on an unmodified stock rom and I would advise making a nand backup before doing any testing so you can easily get back to your previous state when you are done.
If anyone else can test as soon as possible please pm me for a link as testing is going a bit slow. I would have like to have it tested on all 3 variants and released by now but as long as I know its working on 1 variant I can release it.
Mark.
Click to expand...
Click to collapse
Works great thanks. :good: Let me know if u need a logcat (default)
Can't wait to get the Pro version and donate to the toolkit. :fingers-crossed:
Great work
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Would like link also please.
Sent from my GT-I8190 using xda premium
Count me in as a tester, I can spare a few minutes here and there.
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Me too
Sent from my GT-I8190 using xda premium
i have a variant i8910L the latin american version..stock movistar peru rom unmodify so u can send me the link to test it and see what happen
Can I ask you for the link, too, please? Thank you.
SAMSUNG GALAXY S3 MINI TOOLKIT RELEASED TO PUBLIC VERSION
The Toolkit has now been tested to my satisfaction and has been released for download in the 1st post. Please remember that this is the first release and I dont own the device so there may be some textual errors or minor bugs that need ironing out. If you find any problems please post in this thread and they will be fixed as soon as possible. Do not pm me as any pm's that should be posted in a public thread will be ignored.
Enjoy
Mark.
Re: [GALAXY S3 MINI TOOLKIT V1.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Superb!!!!
Great work Mark. I'm glad to see new developers joining us.
I see an option to re-flash stock recovery but now implemented yet. If nobody provided a stock recovery for you to implement, here you go then.
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
dave457 said:
(snipped)
Click to expand...
Click to collapse
Couple thoughts:
1) Please replace every reference of "bootloader" with "boot." Bootloader is entirely different from the boot (kernel). Know the difference if you're going to provide instructions. Using these words interchangeably will cause new users to brick their device because they flashed the bootloader.img when they rarely need to install this. You only flash an image to its similarly named partition on the phone, bootloader does not equal boot.
2) You do not need a custom kernel to get root on Oreo. Your post is misleading. Magisk roots the stock boot image just fine.
3) TWRP will persist between reboots with just the stock boot image rooted with Magisk.
4) TWRP works when you are encrypted. I am unsure why you have a hangup with TWRP and encryption. Are you referring to File Based Encryption which can only be enabled through Developer Options?
5) Why are you making people install a 4 core version of TWRP? If they do not have the BLOD, why force people to use a version of TWRP they do not need?
Sent from my Nexus 5X using Tapatalk
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.[/QUOTE]
Nice thanks man
---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------
jam_09 said:
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
Hey jam_09
I will help you Install 8.1 oreo
First tell me which career are you using? Is your current rom a career specific or a global one check and tell me .. and I'll instruct on what to do further
Click to expand...
Click to collapse
dave457 said:
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
Click to expand...
Click to collapse
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
storo1975 said:
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
Click to expand...
Click to collapse
Yes because later in the process you are going to wipe the data partion to get rid of the encryption this will erase everything on your phone it is like doing a factory rest.
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
I don't know alot about the newer versions of Android like 6 7 8 but I know I read that if you don't root the first time you install twrp then the stock recovery will over write twrp when you reboot. And I also read that magisk modifies the system img in order to hid root. so you can still use gpay and Netflix and pass the safety net check. So I think installing the custom kernel is an extra step that is not nessesary but on the other hand you get certian perks with a custom kernel. Again I don't know much about the newer modding community so o don't know how stable elementalx is. Without installing it I won't know. I have tried dozens of kernels some were spectacular like those from faux others not so much. Also keep in mind to ur technically not on stock rooted version of Android if you have a custom kernel. It no longer is stock software.
Thank you so much for this thread. I was actually about to make one asking how to get back to stock. I used to love flashing the phone all the time, but it got to the point where I never did anything with customization and got bored of it, so I'd rather just be on stock these days.
hi sorry but how to flash the ziP? through TWRP?
Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks for this. Where is twrp.img for Note 20 Ultra 5G / N986B
Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards
Thanks, for this I'll keep for more year Note 20 Ultra. Time to wait or maybe make GSI for Note.
Yaayyyy
I m newbie to note 20 ultra...i want to flash root and twrp... What steps shld i follow.... Currently i m on stock non rooted.. Confused what to flash via odin..
@corsicanu
Many thanks for the latest update mate. It's working perfectly, as everything from you does
corsicanu said:
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
Click to expand...
Click to collapse
I notice I have bootloder on my device that I didn't install my self. I'm just a average user and have no clue how this was put on my phone. Also all of my apps are older versions an I'm unable to update them. I need help figuring out what's going on. Anyone please help!!!
@corsicanu
Many thanks for the latest update mate
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
monicaONxda said:
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
Click to expand...
Click to collapse
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Where's 2.8
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
monicaONxda said:
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
Click to expand...
Click to collapse
Fw as in firmware. Regarding plain android - search for AOSP based projects, i'm not aware of the active developement so i can't properly advice you in this matter.
Regards
corsicanu said:
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Click to expand...
Click to collapse
i am trying to root my note 20 u device. when all succesfully start from magisk module and twrp, i find the screen flicker for a second every 15 seconds. I'm trying to figure out which app the problem is from. looked in screen recorder and found the problem. apparently from system ui. then start again from the initial step one by one. and the cause of the problem is after installing twrp. I'm on Ui5.1 N986B exyns. i feel twrp has a bug
Now im use back stock recovery and problem has gone
Hi it's been a while since I last install TWRP on SS phone, it got complicated now I have few question, can you help answering?
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
Click to expand...
Click to collapse
- For this, do I have to press the key combo 1 time only after clicking Start Odin or I have to hold till the progress done?
2.
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Click to expand...
Click to collapse
- I never install TWRP on my phone, do I have to follow this step?
-If yes, do I have to install that file right after TWRP first boot (when odin completed flashing)
And finally, does it support android 13?
Thank you so much