Related
SAMSUNG GALAXY NOTE 4 - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
SUPPORTED MODELS/VARIANTS
ASIA, EUROPE EXYNOS LTE [SM-N910C] [Supported up to 6.0.1]
EUROPE MODEL QCOMM LTE [SM-N910F] [Supported up to 6.0.1]
SINGAPORE,INDIA,AUS QCOMM LTE [SM-N910G] [Supported up to 6.0.1]
US SPRINT QCOMM LTE [SM-N910P] [Supported up to 6.0.1]
US TMOBILE QCOMM LTE [SM-N910T] [Supported up to 6.0.1]
CANADA QCOMM LTE [SM-N910W8] [Supported up to 6.0.1]
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* 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]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* 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
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* 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
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, 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, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
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 AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
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 Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**UPDATES**
**VIDEOS**
**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.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.
Thanks for this great software
Any chance of getting this working for n910u?...
...
...please? :fingers-crossed:
eternal-intent said:
Any chance of getting this working for n910u?...
...
...please? :fingers-crossed:
Click to expand...
Click to collapse
The n910u is a exynos based device so if you select the n910c at the model selection screen(option 01) then it should work. If it does please let me know and I will add it to the list (with supported stock images).
Mark.
Thanks for your great efforts.
I'm a Nexus user, and totally new to Samsung. I wanna ask if internal storage contents will be erased after rooting like Nexus devices? (I guess not, because it's erased during unlocking Nexus bootloader, but I'm not very sure)
GialanG said:
Thanks for your great efforts.
I'm a Nexus user, and totally new to Samsung. I wanna ask if internal storage contents will be erased after rooting like Nexus devices? (I guess not, because it's erased during unlocking Nexus bootloader, but I'm not very sure)
Click to expand...
Click to collapse
Internal storage is not erased during rooting or by flashing stock firmware images on samsung devices. The only thing that will affect Internal Storage is a factory reset/wipe.
Mark.
Always used your toolkits, thanks man.
thanks for this.
loved it. will explore more. :good::good:
Confirmed working on the Bell Canada version of the SM-N910W8 Note 4. Only issue of note was the fact that on first boot after flashing customer recovery, the stock recovery reinstalled itself. Simple matter of following the easy-to-use instructions with the toolkit. As soon as the flash is complete, manually boot into recovery and re-flash the recovery from TWRP. This will allow recovery to stick after booting up.
Excellent job as always.
Does root through this tool increase Knox counter?
Sent from my SM-N910T using XDA Free mobile app
Does root through this tool increase Knox counter?
Click to expand...
Click to collapse
I'm fairly sure it does.
Also, this part needs a little editing:
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.
Click to expand...
Click to collapse
Also, of note, a lot of people ask if they will be able to update their device OTA after following the root procedure. Right after I successfully acquired root with MSkip's toolkit, I checked the status of my device and it showed "CUSTOM." This is to be expected. Checked for an update and got the expected "your device has been modified" message. But I installed the xPosed framework and installed theWanam module - it includes a feature to change the device status from "CUSTOM" to "OFFICIAL." Did this and rebooted and sure enough, device status now shows "official" and checking for an update only returned the message "the latest updates have already been installed." So now just wondering if I can apply the 5.0 update when it comes out over the next couple weeks and if we can re-root using the toolkit, but I doubt we'll know for sure until the update comes out.
Hi Mark,
many thanks for the new toolkit, it works great as allother and i get the pro key now for the Note 4 too.
many regards
EDIT
TWRP recover 2.8.4.0 for N910F is available now > http://www.techerrata.com/browse/twrp2/trltexx
N910G here!
i have always liked using the toolkits for rooting my devices. It's easier than manual flahsing. So I was wondering if this will work on my N910G?
Just a heads up... TWRP 2.8.5.0 is on the SM-N910F now PS Great Toolkit
acmilan77051 said:
i have always liked using the toolkits for rooting my devices. It's easier than manual flahsing. So I was wondering if this will work on my N910G?
Click to expand...
Click to collapse
Select the N910F from the model selection and try the root procedure. It should work fine. If it does then I will add support for that variant.
Mark.
Update
I have updated the module files (that are downloaded after the Note4 is selected at startup) to fix several config settings, update some Toolkit functions and update TWRP for all variants to 2.8.5.0. The unroot zip file has also been fixed/updated.
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069 if you don' already have the Toolkit
If you have already downloaded the new Toolkit and have the v1 module for the Note 4 then delete the ConfigGalaxyNote4.exe and the _currentrecoveryversionGalaxyNote4.ini from the tools folder and the Unroot-UninstallBusybox-CwmManager.zip from the root folder. Download the new unroot zip file from http://skipsoft.net/download/fileupdates/Unroot-UninstallBusybox-CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy Note 4 from the list. The Toolkit will then download new module files.
I will also push an AutoUpdate with the same updates/fixes for Pro users to automate the whole above procedure.
Mark.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Based ROM: Elephone_P8Mini_20170914
10/14 - UPDATED: TWRP version added
This is recommended for people that want something like more pure like AOSP, and without malware.
- Launcher changed to Next Launcher.
Ps. This is same Port ROM that i already released in japanese site at 1st October 2017 https://egg.5ch.net/test/read.cgi/smartphone/1504178568/208-209
TWRP version:
- Download link: https://mega.nz/#!iRkxALgJ!kuIwBusd_F_TqYj93CmzY03Z67NhDDrjN_8tJGMqOtk
- Install TWRP (real source link https://4pda.ru/forum/index.php?s=&showtopic=847735&view=findpost&p=65694030) You can download too in https://androidfilehost.com/?fid=673791459329051837
- Boot to TWRP
- Wipe Dalvik / ART Cache
- Wipe System
- Wipe Cache
- Wipe Data
- Wipe Internal Storage
- Install Port ROM
- Wipe Cache & Dalvik
- Reboot to system
- Done.
SP Flash Tool Version (complicated method):
- Download link: https://mega.nz/#!fddnGaqT!067RI1iNJn5U14NWoXyCf6LY8Nj-jC31Tw3CAQohKlQ
Attention: My guide only for people with original state, doesn't with mofidication. If you installed TWRP or rooted so please doesn't follow guide below. Use TWRP version.
1 - Update firmware your S8 to latest.
1.1 - Factory Reset (make backup before to do this step)
2 - Extract file of link above.
3 - Install adb-setup-1.4.3.exe from Tools folder. This is included in Tools folder, but you can download here https://forum.xda-developers.com/showthread.php?t=2588979
4 - Extract MT65xx USB VCOM DRIVERS.zip from Tools folder and install (use this guide if you don't know how install https://www.getdroidtips.com/install-mediatek-mt65xx-usb-vcom-drivers/)
5 - Extract SP_Flash_Tool_v5.1728.rar from Tools folder
6 - After extracted files of item 4, find flash_tool.exe and open.
7 - Click choose of Scatter-loading File and select MT6755_Android_scatter.txt from ROM folder that you extracted on item 1.
8 - Check if "Download Only" is selected, and only Recovery, Boot and System are selected like image below.
{
"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"
}
9 - Turn off the S8
10 - Click Download button of Smart Phone Flash Tool
11 - Wait for the process to complete
11.1 - Check if popup like below appear
12 - Disconnect your S8 from PC
13 - Turn on the S8
14 - Copy all files inside of Gapps folder that you extracted on item 1 to your smartphone (location doesn't import here)
15 - Turn ON USB Debugging Mode (use this guide if you don't know how to do https://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android.htm Read the item 4 (4. Android 5.0 Lollipop))
16 - Connect your S8 to PC
17 - Use command below to reboot to recovery in CMD of your PC
Code:
adb reboot recovery
18 - If appear dialogue click Yes
19 - In CWM recovery
20.1 - Wipe Menu＞Wipe Data - Factory Reset
20.2 - Install G-Killer.zip that you copied to S8 in step 14 (This is included in the Gapps folder of item 13, but you can download here https://forum.xda-developers.com/showthread.php?t=2588979)
20.3 - Check only itens below and remove gapps (if you do not do this step the google play doesn't work)
20.4 - Now install opengapps that you copied to S8 in step 14 (This is included in the Gapps folder of item 13, but you can download here http://opengapps.org/)
20. 5 - Optionally you can install Magisk that you copied to S8 in step 14 (This is included in the Gapps folder of item 13, but you can download here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
20.6 - Before reboot Wipe Cache and Wipe Dalvik Cache
20.7 - No for "Root access is missing. Root device?"
21 - Done.
thanks,
this works wit bluboo s8 ?
https://forum.xda-developers.com/general/device-reviews-and-information/bluboo-s8-information-reviews-5-7-hd-t3673085
is this multilanguage?
Point 17 – ? how do I do that to reboot to recovery with CMD.
can you say that more precisely.
is there no key function volume + power? I dont know
bananaci said:
thanks,
this works wit bluboo s8 ?
https://forum.xda-developers.com/ge...bluboo-s8-information-reviews-5-7-hd-t3673085
is this multilanguage?
Point 17 – ? CMD.Is there no key function volume + power? I dont know
Click to expand...
Click to collapse
....1. this works wit bluboo s8 ?
2. is this multilanguage?
3. Point 17 – ? how do I do that to reboot to recovery with CMD.can you say that more precisely.is there no key function volume + power?.....*///
***Note:
I do not have this device (getting 1 maybe, if *Future Custom ROMs & curiosity of $158 S8), so my answers might NOT be reliable or worth a click ?
1. Yes, the developer's OP clearly mentioned "for bluboo S8)
2 Yes(99%). *English(UK), is usually default inclusive→
OR
The specific preferred language, u say? might be the needed gem for your question "multilanguage?", Because it seems like variants and of MTK has a difference.
For example, German(Austria) included in 1, may not be there in the other.
3 .I think The Dev's OP, already stated, precisely.
Usually, after you enable those options,
(...Enable via USB debugging OEM, ADB etc [√] found under *developer mode/option* on the device),
Go to your PC, → ^ADB folder, (where you have downloaded & installed the ADB.exe,) press shift+rightclick and choose "Open with Command Prompt"
And type the command as Developer mentioned above ( instructions -OP)
(Or available commands on ADB/fastboot recovery on Linux/windows).
I havent use this (Elephone S8 Ported mini), and as I said I do not have a bluboo S8 (yet).
Do let me know if substratum theme works on this.
however, developer's effort on # Clean AOSPA minus bloatwares, is Great work already. Totally worth a click on "?". For device like this it's even hard enough to get a honest user review.
I still can't make a decision between other s8-lookalikes available. HomtomS8,Leagoo S8, Umidigi, Ulephone considering ROMs support).
Point 11,12,13. MT6755_Android_scatter.txt perfectly installed with flash tool
But the phone boots only carlycwm
so I did I followed point 19. so i do:
20.1 - Wipe Menu＞Wipe Data - Factory Reset
20.2 - Install G-Killer.zip
20.4 - Now install opengapps
20.6 - Before reboot Wipe Cache and Wipe Dalvik Cache
20.7 - No for "Root access is missing. Root device?"
21 - Done.
But always the same. the phone boots only carlycwm.
what can i do?
bananaci said:
Point 11,12,13. MT6755_Android_scatter.txt perfectly installed with flash tool
But the phone boots only carlycwm
so I did I followed point 19. so i do:
20.1 - Wipe Menu＞Wipe Data - Factory Reset
20.2 - Install G-Killer.zip
20.4 - Now install opengapps
20.6 - Before reboot Wipe Cache and Wipe Dalvik Cache
20.7 - No for "Root access is missing. Root device?"
21 - Done.
But always the same. the phone boots only carlycwm.
what can i do?
Click to expand...
Click to collapse
Hi,
you probably have skipped step 19.
Factory Reset inside of CWM recovery.
Updated the first post with TWRP version.
now my phone is dead, ican nothing do.
now when i insert cable with phone is started only cwm..phone not reboot
bananaci said:
now my phone is dead, ican nothing do.
now when i insert cable with phone is started only cwm..phone not reboot
Click to expand...
Click to collapse
Flash TWRP in SP Flash Tool and follow TWRP instruction of first post.
- Turn off S8
- Press Download button in SP Flash Tool
- Connect cable
- If flash TWRP recovery doesn't start Hold the power button until progress start
Reason that only start in CWM.
- You upgraded firmware using another recovery that does't original one
- You used factory reset of system using another recovery that does't original one (probably this it's the cause, appear that you using TWRP https://forum.xda-developers.com/showpost.php?p=74092694&postcount=21). Probably you followed my guide with TWRP. My guide only for people with original state, doesn't with modification.
You never can use factory reset of system with TWRP or CWM.
ok thanks, ill try this
it works not.Nothing.
The problem is when i plug the cable into pc or dc just boot only carlywm ported by ghost45.version 6_kk_carliv-mod.
before i flashed your ported rom with flash tool i had before twrp 3.1.1 Bluboo S8 on my phone..since everything had worked.
And now i can nothing do. it comes only cwm ghost45.version 6_kk_carliv-mod.
I`ll tried your rom
TWRP version:
- Download link: https://mega.nz/#!iRkxALgJ!kuIwBusd_...DrjN_8tJGMqOtk
with cwm ghost45.version 6_kk_carliv-mod to flash it installes it.
but when the phone first boot it comes allways cwm ghost45.version 6_kk_carliv-mod.
so i`ll tried anymethodes with flashool first press download than press power hold... down... nothing ..it comes jus cwm ghost45.version 6_kk_carliv-mod.
bananaci said:
so i`ll tried anymethodes with flashool first press download than press power hold... down... nothing ..it comes jus cwm ghost45.version 6_kk_carliv-mod.
Click to expand...
Click to collapse
So follow all step below correctly, doesn't skip steps.
Download TWRP Recovery for CWM
https://mega.nz/#!md8AAZxR!5iepVFzSKGY0F-FlPLfCxSw3nH7r6-VgpBaemAlSclk
Install recovery twrp.zip of link above in CWM.
Reboot.
Now will reboot in TWRP
IN TWRP
- Wipe Dalvik / ART Cache
- Wipe System
- Wipe Cache
- Wipe Data
- Wipe Internal Storage
- Install Port ROM (First Post of this thread)
- Install recovery original.zip https://mega.nz/#!jMMRHbTI!eU-saTyapPon8xdfa2NORdpeV5CSGFfzdQHuqkwAcRE (this is very very important step)
- Wipe Cache & Dalvik
- Reboot (wait, doesn't restart until system start completly)
- Now original recovery will restored. If you need twrp, you need install again. And doesn't use factory reset of system, samething will happen again.
bananaci said:
before i flashed your ported rom with flash tool i had before twrp 3.1.1 Bluboo S8 on my phone..since everything had worked.
And now i can nothing do. it comes only cwm ghost45.version 6_kk_carliv-mod..
Click to expand...
Click to collapse
I already explained before. This isn't my fault. You used my guide (SP Flash Method) with TWRP.
If used factory reset with TWRP, of cource that will result in that.
I will be giving this a try tonight. Is there a way to keep the Blueboo startup animation or will this change that? Not that it matters much. Do all the features of the phone work with this rom?
labellee25 said:
I will be giving this a try tonight. Is there a way to keep the Blueboo startup animation or will this change that? Not that it matters much. Do all the features of the phone work with this rom?
Click to expand...
Click to collapse
This Port Rom use elephone animation.
Yes all feature of phone work fine.
oh yes, yuppi.ya yeahh it works.
with tis TWRP Recovery for from 3.1.1 by Jemmini works now. I had that before.
and your yor port rom works fine ..
I will report you.
thank you for your understanding
bananaci said:
oh yes, yuppi.ya yeahh it works.
with tis TWRP Recovery for from 3.1.1 by Jemmini works now. I had that before.
and your yor port rom works fine ..
I will report you.
thank you for your understanding
Click to expand...
Click to collapse
Thanks for feedback.
I dont know why,
I can not bluboo connect with any PC?.
with the original software was not so.
can you help?
bananaci said:
I dont know why,
I can not bluboo connect with any PC?.
with the original software was not so.
can you help?
Click to expand...
Click to collapse
Have you tried with another PC?
I can't reproduce your issue. So unfortunately I can not help you.
yes i tried with,
winxp,win7 and win10,with my
old pc win7 til yet havent problem but with your rom can,t connect now.
so i chanced c-cable nothing happens
with another smartphones zopo,lenovo,samsung can i connnect my pc.there is no problem with this phones.
Same for me can't use sp flash tool to root too.. PC only see it in usb mode for camera or file transfer
Debug modus is on.
The problem is when i connected my phone it say just battery charging.
Here is the problem cause I can not switch usb mode for camera or file transfer.
There is a point on status bar at the top to switch usb mode for camera or file transfer.
NOTHING HAPPENS Here
What a pity this stable Rom has an error/bug here.
Test twrp build for this mediatek device (SM-C7100). Post logs etc so I can help solve issues when I am available to do so.
TWRP download: https://www.androidfilehost.com/?fid=673956719939834043
SM-C7100_C7100ZHU1ARB1.zip: https://www.androidfilehost.com/?fid=673956719939834050
Kernel download: https://www.androidfilehost.com/?fid=746010030569970527 April, 23rd, 2018
Sources
Kernel source: https://github.com/travismills82/android_kernel_samsung_mt6757
TWRP device tree: https://github.com/travismills82/twrp_android_device_samsung_jadeltechn
Kernel Features
Knox Disabled
DM-Verity Disabled
Tima Disabled
More TCP congestion control algorithms
Remove verifiedbootstate flag from /proc/cmdline (for safety net)
Conservative gov enabled
Always enforce selinux disabled
Fsync on/off Toggle
Ninendo Wiimote support
+ More not listed check git changes for a full list
Regards,
Travis82
Hi it didn't work... I think this is for J7 plus only and please Help after flashing the custom recovery my boot logo of C8 is gone.... Please help
I have tried to install using odin and it says on the phone a chinese message,which i translated with google, that read your phone needs to be unlocked to install a custom operating system, even though i enabled oem unlock and usb debugging. I used viper4android on my old phone and its annoying that im not able to install it on my new one.
Please help me when you get time:good:
the twrp cannot mount data partition unless format it first. and my device is sm c7100.
I can't install twrp in the first place.
How did you guys install it.
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
How to use the TWRP with Android Oreo?
Gautam488 said:
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
Click to expand...
Click to collapse
Brother how do you manged to unlock bootloader...? Please share with us
google play gives an error, the installation screen is not constantly installing
Hi everyone,
For those who have tried, could you please confirm whether the files are working or not.
Since there is no steps and instructions, can someone post the the procedure/code used for flashing kernel and TWRP?
Thanks
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
toto4c19 said:
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
Click to expand...
Click to collapse
Libsecure storage cannot be downloaded from anywhere could you please provide me link for the module
toto4c19 said:
For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
Hello, thx for all your hard work.
Click to expand...
Click to collapse
My C8 is 8.1 tried resetting back to factory, still 8.1
Noted your comment re ODIN, but I use Linux, Odin seems Win only.
Have successful rooted and installed Lineage on an old Note 3, but I didn't have to downgrade that!
Can you give me please, some guidance how I can return this wretched thing back to 7.1?
Actually, I am suspecting return is the wrong word as it may have come with 8.1 installed.
I'm a bit lost at this point.
Cheers
p
Install Android 9.0 Pie GSI on Moto G5 Plus (Windows/Mac/Linux)Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: If coming from stock, backup your persist and efs partitions. If you already have a backup of those partitions, upload them to Google drive. If you dont have a backup of those partitions yet, do so now. Search the guides section and you will find a tutorial.
Warning 4: You might loose all your data. Make sure to backup your data.
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
Not Working :
hotspot
Moto action option in settings does not open.
NFC (GSI side bug)
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Steps
1. Download all the files listed in downloads section and place them inside one folder say Android P.
2. Unzip arm64 Aonly GSI zip file. Unzip fastboot and adb zip file. Rename treble twrp image file to twrp-potter-treble.img. move twrp img file to platform-tools folder.
Create folder Pie in internal memory of phone.
Move below files to Pie folder on phone
* Android P GSI Image (make sure you have extracted the file).
* Gapps Zip File (needed only if GSI image does not have google apps in built).
* Trebelized Lineage OS Vendor Zip File
* Ace Kernel zip file
* Pie Fixes zip file
Reboot device into bootloader mode.
3. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot devices
Mac/Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
fastboot flash recovery twrp-potter-treble.img
Mac/Linux
Code:
./fastboot flash recovery twrp-potter-treble.img
4. Disconnect phone from computer. Use volume buttons to navigate, Once you see recovery option, press power button to select. Once you have booted into TWRP recovery. Go to wipe. Select system/data/cache/dalvik cache. Swipe to confirm flash.
5. Go to home screen -> Install, Navigate to Pie folder. Select lineage os vendor zip file. Swipe to confirm flash.
6. Go to home screen -> Install -> Install Image. Select GSI image file. Swipe to confirm flash.
7. (if gsi has no gapps) Go to home screen -> Install -> Select gapps zip file. Swipe to confirm flash.
8. Go to home screen -> Install -> Select pie fixes by Shiv zip file. Swipe to confirm flash.
9. Go to home screen -> Install -> Select Acekernel zip file. Swipe to confirm flash.
10. Reboot -> System.
11. If stuck in bootloop. Reboot to twrp. Go to wipe. Select format data. Enter yes. This will wipe your internal storage so make sure to backup. Reboot -> System.
12. Android 9.0 Pie. Profit!
To root flash Magisk zip file in recovery.
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Video Guide
Downloads :
Latest ADB & Fastboot Zip File :- https://developer.android.com/studio/releases/platform-tools
Arrow OS GSI Thread (Download arm64 A only):- https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
Treble TWRP for Moto G5 Plus:- https://twrp.me/motorola/motorolamotog5plus.html
Lineage Vendor Android 9.0 Pie Moto G5 Plus :- https://drive.google.com/file/d/1ud-54oPrw00t-0DmlIvV-9adbmWr_k7d/view?usp=drivesdk
Pie Fixes by Shiv :- https://drive.google.com/file/d/1mhXl-vLavAEMjXia6W6f0mQcYT-FoCv0/view
Ace Kernel for Android 9.0 Pie Moto G5 Plus :- https://forum.xda-developers.com/g5-plus/development/potter-acekernel-v1-10-t3801466
Google Apps for Android 9.0 Pie :- https://opengapps.org/
Xda Android GSI forum :- https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Tools to Unzip GSI
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/
Contributors
@Martichou
@kubersharma @GtrCraft
@vache
@phhusson
@Shivvvv @anshuman_1
munchy_cool
Better use the latest official twrp, it's newer and supports treble too
GtrCraft said:
Better use the latest official twrp, it's newer and supports treble too
Click to expand...
Click to collapse
Thank You. Link updated to twrp website.
Thanks for the write-up. Any idea if the camera on the rom is google cam or something aosp-like?
Was so hyped for this but sadly when installed I got the dreaded "Device Not Certified By Google"
---------- Post added at 06:29 PM ---------- Previous post was at 06:02 PM ----------
dunderball said:
Thanks for the write-up. Any idea if the camera on the rom is google cam or something aosp-like?
Click to expand...
Click to collapse
It had both when I installed it
[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!
On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)
GCam settings
But my google camera keep crashing when I want to go into camera settings
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this
bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.
"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.
Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?
[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL
cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working