Related
INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. 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 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). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
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.
**VIDEOS**
excellent
great
great share!
Will this work for rooting the XXALI9?
this is great,
lithium86 said:
Will this work for rooting the XXALI9?
Click to expand...
Click to collapse
It will work on everything upto ALJ7 and beyond.
Final checks and uploading now.
Mark.
The Toolkit will be finished uploading in less than 10 minutes but before I release it publicly I need someone with a GT-I9305 to download and test the root and nand backup features. Please message back in here if you can test it right away as I can't post the link until I know it works properly.
Theres absolutely no risk of any damage as Stock Firmware images exist for your device so if anything doesnt work a simple flash will fix anything.
Mark.
Download link posted in OP.
Thread officially open
If anyone spots any bugs or errors in V6.0.0 please let me know right away as this was a major major rewrite to be able to incorporate I9305 and while I think everything looks fine I may have missed something.
Enjoy.
Mark.
Thanks Mark!
I know it is not your bag but any idea when CWM-Touch may be available for the I9305?
Thanks!
ALI9 ??
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Edit... didn't see before after posting that this q already has been answered....
[email protected] said:
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Click to expand...
Click to collapse
Did you read the text on the Model Selection Screen?
FOR ROOTING AND PERFORMING ADB TASKS ON YOUR DEVICE, IF YOU CANNOT FIND THE BUILD
IN YOUR DEVICES SECTION THEN YOU CAN SELECT THE CLOSEST BUILD IN THE LIST (AS LONG
AS IT IS THE SAME ANDROID NUMBER IE. 4.0.4 or 4.1.1).
Click to expand...
Click to collapse
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.
mskip said:
Did you read the text on the Model Selection Screen?
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.
Click to expand...
Click to collapse
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:
[email protected] said:
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:
Click to expand...
Click to collapse
Correct
Mark.
Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2
Thanks for your hard work. I love the Nexus toolkit.
Do you have any plans to expand this G3 toolkit for verizon? It is the d2vzw.
lyriquidperfection said:
Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?
lithium86 said:
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?
Click to expand...
Click to collapse
Yes and I'm also updating my application to support Qualcomm NV item backup and restore.
Sent from my GT-I9305 using Tapatalk 2
Hi,
I'm new to this forum and a beginner to learn about android devices. I have a Gionee E3 android device (Asian version - English) with Android 4.2.1 on it. Unfortunately I have forgot the pattern lock and to make matter worse the following problems are also included -
1) No root - the device is not rooted
2) No USB Debugging
3) No custom recovery (I guess, only (stock recovery), Android system Recovery is displayed when tried pressing volume + and power key combination )
4) No wi-fi or mobile data could be enabled as the lock won't allow even to slide the screen from the top to get quick access to these things.
5) Windows Xp on my pc
I have tried the following -
1) ADB method to delete the gesture.key, but as the device is not rooted, failed with this attempt with several errors.
2) Tried from Cygwin, but the SU command gave error - -bash: su: command not found
3) Tried Aroma file manager zip file from Android system recovery ----> apply update from SD card, returned error - Installation aborted. Tried to resolve by fixing the updater script file through Notepad++ with different versions of Aromafm but nothing works.
4) Tried with several pattern cracking software zip files through Android system recovery ----> apply update from SD card, still getting error - Installation aborted.
Kindly help me to recover my data intact.
Don't want to root the device and there may be the risk of wiping the data off.
I have also tried to backup from Android system recovery ----> backup user data and 300 MB of data has been backup on SD card. Does this include SMS and phone contacts too with whatsapp data also?
Thanks in advance and sorry for long description, just wanted to make sure you guys know all the things I have tried. Your help will be greatly appreciated.
Sam
sam_h said:
Hi,
I'm new to this forum and a beginner to learn about android devices. I have a Gionee E3 android device (Asian version - English) with Android 4.2.1 on it. Unfortunately I have forgot the pattern lock and to make matter worse the following problems are also included -
1) No root - the device is not rooted
2) No USB Debugging
3) No custom recovery (I guess, only (stock recovery), Android system Recovery is displayed when tried pressing volume + and power key combination )
4) No wi-fi or mobile data could be enabled as the lock won't allow even to slide the screen from the top to get quick access to these things.
5) Windows Xp on my pc
I have tried the following -
1) ADB method to delete the gesture.key, but as the device is not rooted, failed with this attempt with several errors.
2) Tried from Cygwin, but the SU command gave error - -bash: su: command not found
3) Tried Aroma file manager zip file from Android system recovery ----> apply update from SD card, returned error - Installation aborted. Tried to resolve by fixing the updater script file through Notepad++ with different versions of Aromafm but nothing works.
4) Tried with several pattern cracking software zip files through Android system recovery ----> apply update from SD card, still getting error - Installation aborted.
Kindly help me to recover my data intact.
Don't want to root the device and there may be the risk of wiping the data off.
I have also tried to backup from Android system recovery ----> backup user data and 300 MB of data has been backup on SD card. Does this include SMS and phone contacts too with whatsapp data also?
Thanks in advance and sorry for long description, just wanted to make sure you guys know all the things I have tried. Your help will be greatly appreciated.
Sam
Click to expand...
Click to collapse
Hello,
Try posting your query here Android Q&A with all relevant details, the experts there maybe able to assist you.
-Vatsal
Hello Vatsal,
Thanks for your reply. I have moved it to the appropriate place.
And yes, I like your Iron Man.:good:
Latest video: https://youtu.be/o6cpMa2Fo_c
Since 01.16 update Gigaset Me and Me pro use same ROM. So read carefully and take responsibility what you are doing on you device.
Gigaset Pure is not supported here.
GPL Source codes:
Me/MePro/ platform tools full : http://www.gigaset.com/de_de/cms/lp/open-source.html
Me/MePro platform tools uploaded in 1 file (gdrive): https://drive.google.com/uc?id=0B_81lkQEKce4bFlaRXk3dFFwQzA&export=download
Me/MePro kernel source (my repo on github): https://github.com/Eddie07/GIgaset_Me_MePro_3.10._kernel
Terms of Usage:
1. Everything posted on this post should be reposted with links to original post.
2. I'm not responsible for any damage to your phone.
3. If you are aware of bricking device by this or you don't understand some of processes described below - close this thread and leave it alone.
4. If you agree with p.1,2,3 go on to Step2.
GIGASET secret codes:
*#*#4636#*#* - phone info
*#*#2580#*#* -engineer mode (wif, bt tests, usb ports, adb root (pass:gigaset001), ota settings.
*#*#708#*#* - float system info (cpu speeds, m|b temp), shake test.
*#*#801#*#* - wifi test.
*#*#802#*#* - bt test.
*#*#803#*#* - bt test 2.
*#*#2588#*#* - factory hardware tests.
*#*#2581#*#* - Camera callibration??.
(Only ME/MEPRO)TWRP CUSTOM RECOVERY, UNBRICKING:
-FLASH CUSTOM RECOVERY ON ME/MEPRO HERE
-UNBRICK SOLUTION back to rom EU00_V1.1.20160616R ME/MEPRO (if you deleted system, recovery, boot) : BACKUPS--- UNBRICKING
(Only ME/MEPRO)CUSTOM ROMS:
LAST CM 12.1
(Only ME/MEPRO)PATCHES TO STOCK ROM TO BE INSTALLED VIA CUSTOM RECOVERY:
LAST MY "TUNED" TWRP BACKUP https://forum.xda-developers.com/showpost.php?p=71180342&postcount=371
-PATCH#1 TWRP PATCH ME/MEPRO for CPU speeds uncap (1,9ghz), Thermal config fix, Fix of display size MePro HERE
-PATCH#2 Enable 4K video recording in stock camera app HERE
-PATCH#3 Enable Callrecording button in stock dialer app HERE
-PATCH#4 READ DESCRIPTION HERE
-PATCH#5 SystemUI patch HERE
ADB ROOT FOR STOCK ROM WITHOUT ROOT AND CUSTOM RECOVERY:
- Unlocking Me/Pro abd root via factory tool hidden in rom. (usage for Gigaset Me/Pro/Pure)
1) Type in dialer: *#*#2580#*#* to get in Engin. tool
2) Select "priviledge" tab.
3) Type "gigaset001" in pw field.
Get adb root
to check if is done enable USB debugging and try adb command from PC:
"abd shell" if command prompt ends with "#" then adb is rooted, if "$"-isn't!
4) Turn off adb root- type password again.
Thank friend
GaulCrixus said:
Thank friend
Click to expand...
Click to collapse
You are able to install Supersu via abd (you can find manuals on internet).
But if you copy wrong files, or even update binary on purpose in SuperSU gui, you are risking to get bootloop or stuck on ANdroid logo.
There is no way to recover (YET). But im on my way to test something.
So you are warned!
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
I emailed Gigaset support and asked about the Marshmallow update and they said its not ready yet but would be at some point, I have read on German forums that no one replies when asked about updates.
Getting CM or PacROM for this would be great.
imkrl said:
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Click to expand...
Click to collapse
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
heineken78 said:
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
Click to expand...
Click to collapse
I cant expand the images in your post.
typos1 said:
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
Click to expand...
Click to collapse
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
# #ifdef GIGASET_EDIT
# /*[email protected], 2015/08/20. added. add root mode for release build */
#ifeq ($(TARGET_BUILD_VARIANT),user)
persist.sys.root.enable=none
# /* [email protected], 2015/10/29. added. add feature to reserve pictures when doing 'Factory data reset'.*/
sys.root.wipedataless=false
#endif
# #endif /*GIGASET_EDIT*/
Click to expand...
Click to collapse
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
heineken78 said:
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
Click to expand...
Click to collapse
Yes, I realise that, I do get a #, I was just pointing out to @imkrl that nothing appears to happen on the phone from looking at the screen, but something does actually happen
After removing from adb and installing SuperSU, SuperSU says its not rooted.
I ll do the dump and upload later.
On the German forums people say that no one from Gigaset replies to messages and that support has been dropped, but that is not official, it is just people's assumptions, when I contacted Gigaset I DID get a reply saying "it will happen automatically", not "we have dropped support", so maybe support has been dropped, maybe not, nothing has been officially said by Gigaset.
But dropped or not getting support for custom ROM like CM of PACrom would be good.
typos1 said:
After removing from adb and installing SuperSU, SuperSU says its not rooted.
Click to expand...
Click to collapse
Right, root is only for adb. But advanced users could push some files in device via adb root# and get supersu working too.
But its quite risky, if you made a mistake, then device can no boot to android anymore (ex. bootloop). Then is bricked.
-You cant access partitions from fastboot - is completely factory locked. (even :"fastboot reboot" doesn't work. fastboot don't listen to any command)
-factory recovery not allows to use adb or view files.
Everything points to have custom recovery.
Another thing if you got su working by pushing files, some system files became modified by supersu and with next OTA update, by security check, OTA will fail to update (patch). So you need system partition backup to restore it on demand.
There is one way to hard unbrick to use "edl" mode (QUALCOMM 9008) (switched phone, hold vol-down, connect usb). I have idea how to but I didn't test, cos I don't want to take a risk to erase memory of my working phone.
To avoid all risks, have to flash custom recovery TWRP from android, within you will be able to restore everything and install supersu normal way. What ever you change from recovery: flashing zip's, installing backups or getting bootloops after, you will be able to load custom recovery again and fix from it. Before installing of custom recovery, backing up of recovery, boot and system partitions should be done, also have to check devinfo partition of your device to be insured that bootloader is unlocked, because if bootloader is locked it will ignore not signed recovery or any boot images.
Yes this is all backdoor and hard to do if you are rokkie in this, but 100% working methode. There is no any Kingaroot or other working roots for Gigaset, cos android security of Gigaset is very high, even with 5.1.1 version.
Why I need your files, typos1: recovery, boot and devinfo. To check them if they are same with Me pro, if not to make another custom recovery for me device.
Sure I will try to make rom ports, may be someone else will do it, cos root is found by me after on second day of device usage, while device was one year on market and lost interest of many. Btw custom recovery source was taken from OnePlus2, hardware +- is similar.
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
xueyaotianxia said:
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
Click to expand...
Click to collapse
Device?
reply
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
Mine came from China (they ALL do, thats where theyre made !!) and mine does have the Playstore.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
No way to root yet with common ways. Only via adb shell or via recovery.
But Me and Me Pro have same platform, so take a look what you have at ls dev/block/platform/f9824900.sdhci/by-name/. Use this command in adb shell and write me the list of partitions.
If you get error, Gigaset Me may have different storage name (not f9824900.sdhci as me Pro I own). so try ls dev/block/platform/ and find right name of storage, then ls dev/block/platform/STORAGENAME/by-name/ shows list of partitions.
Guys I need partitions of Me!
After I typed ls dev/block/platform, it shows this:
f9824900.sdhci
f98a4900.sdhci
what should I do now?
Thank you..
---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------
I would guess your device is made for oversea's market...so that is why it has playstore pre installed...I bought mine in China (which made for Chinese market, by law no google)...it makes life so much more difficult, as I have to install 3rd party app store...cannot root the phone now so whenever I open play store it shuts down immediately.
---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------
After I typed this ls dev/block/platform/f9824900.sdhci/by-name, it shows:
DDR
aboot
abootbak
apdp
bluetooth
boot
cache
config
devinfo
dpo
fsc
fsg
hyp
hypbak
keystore
limits
misc
modem
modemst1
modemst2
msadp
persist
pmic
pmicbak
recovery
rpm
rpmbak
sbl1
sbl1bak
sdi
sec
splash
ssd
system
tz
tzbak
userdata
that is all.
I went back tried step 2 again, it shows 01. But when I tried step 4 to do the recovery it says:
aset-me.img of=dev/block/platform/f9824900.sdhci/by-name/recovery <
0 records in
0 records out
24 bytes transferred in 2.347 secs <10504398 bytes/sec>
recovery seems still the old factory one.
---------- Post added at 09:51 PM ---------- Previous post was at 09:39 PM ----------
Hahaha I tried step 4 again it worked!! Now I am in Team win recovery project v2.8.7.0
What should I do now to root the phone??
Thank you very very much you saved the day!!!
xueyaotianxia said:
Thank you very very much you saved the day!!!
Click to expand...
Click to collapse
Download and install supersu.zip
Notice, you have to disable engineering menu root (type password again), because factory adb root and another (supersu) will have conflicts.
So confirmed that this recovery works on Gigaset Me too!
thank you
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
xueyaotianxia said:
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
Click to expand...
Click to collapse
You have messed up. Suggest to restore system.img or if you done system backup in twrp and try root again.
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
xueyaotianxia said:
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
Click to expand...
Click to collapse
You should do backwards procedure to restore system image. Better if you do it while in TWRP recovery.
1) Open TWRP recovery and connect to PC
2) In adb shell on pc: dd if=sdcard/systembackup.img dd of=dev/block/platform/f9824900.sdhci/by-name/system
Where systembackup.img name of backup image you done stored on internal memory. This will overwrite system partition to previous state.
For next time I suggest you to make backup in TWRP normal way. It will be faster.
Disclaimer: This guide and the tools included are provided as-is. Testing has been limited and nothing is guaranteed to work. I take no responsibility for lost data, bricked devices, etc. Continue at your own risk, and please read carefully. THIS GUIDE WAS WRITTEN FOR PHONES ON ANDROID 8.1 - MAY NOT WORK ON DEVICES WITH THE PIE UPDATE.
Note that Magisk and TWRP can interfere with downloading and installing OTA updates. At this time the only updates are security patches, so it would be best to make sure all OTAs are installed before starting.
Mounting and decrypting the data partition is still hit-or-miss. If you haven't set up a passcode or password, TWRP should be able to mount it, and you still might be able to even if you have. Magisk will corrupt encrypted partitions and force a factory reset, and TWRP will not be able to help you back things up if Magisk has been installed before disabling encryption. You've been warned.
Guide: Installing TWRP and Magisk on the Visible R2
Tools:
prog_emmc_firehose_8917.mbn - firehose for flashing system partitions
Latest available TWRP zip - contains TWRP recovery image and the necessary files for flashing
fstab.qcom - for removing forced encryption
Patched boot image - for installing versions of Magisk newer than v16.7
Stock firmware - optional, but handy to have in case something goes wrong.
Windows users: QPST/QFIL and the QDLoad drivers (possibly the first set of ZTE drivers as well, but likely not necessary). Installing drivers in compatibility mode for XP or Windows 7 might help resolve issues.
Install adb if you don't already have it set up.
Linux users: qdl source code; the guide will cover compiling and installing it. You'll also want to install adb from your distro's repositories. There is a snap package for qdl, but it doesn't work for the purposes of this guide, so please don't use it.
Part 1: Installing TWRP
TWRP is an easy-to-use, touch-based custom recovery for Android devices, designed to make backups and installs simple and painless. Unfortunately, the installation of TWRP on the R2 is going to be a little less simple and painless; the device's bootloader isn't locked down, but it doesn't support fastboot commands, meaning we'll need to get our hands dirty to flash partitions.
Before starting, it's also worth noting that the current TWRP build cannot always decrypt encrypted data partitions, and the device is encrypted by default. This means that TWRP may not be able to mount or back up your data partition unless it's formatted and forced encryption is removed (see part 2).
To flash TWRP, we need to put the device into EDL mode and forcibly overwrite the existing partitions using an EDL tool and the firehose linked above, which unfortunately requires a PC of some sort. Enable USB debugging on your phone, then follow the steps for your operating system below.
For Windows:
1. Install the Qualcomm driver package. Before continuing, you will need to make sure Driver Signature Enforcement is disabled on your PC; QFIL may have issues communicating with the device if Windows blocks the driver.
2. Install the QPST package, then open QFIL from the Start menu.
3. Select 'Flat Build' under Select Build Type.
4. Extract the TWRP zip to an accessible directory (something like C:\TWRP works fine). Place the firehose.mbn in the same directory.
5. Press 'Browse' under Select Programmer, then navigate to the TWRP directory and select the firehose file.
6. Press 'Load XML'. Select rawprogram_recovery.xml, then patch0.xml
7. Connect the phone to your PC and make sure USB debugging is enabled. Make sure your PC is trusted by the phone for ADB commands, then send 'adb reboot edl'.
8. If everything went well, the phone should have rebooted with a blank screen, and QFIL should be asking you to select a port. Press Select Port, and then choose (hopefully) the only item available).
9. The 'Select a port' message should now read something like Qualcomm HS-USB QDLoader 9008 (COM#). IF it does, simply press download.
10. There should be some output in the status window, ending a few seconds later with a blue Download Succeeded message. If so, you're done, and can restart your phone. If there's a red error message, or the status window seems to be stuck on sending, double-check that your device is registered properly in Device Manager.
11. Once you're done flashing, you can reboot into TWRP by holding down the Vol Up button as the phone reboots.
For Linux:
1. Unzip the qdl zip into its own directory, then enter the directory.
2. Compiling qdl requires libraries that may not be installed. For Ubuntu users, you simply need to run ' sudo apt install libudev-dev libxml2-dev' to install them; people with other distros should know how to use their package manager and may have to find the packages under a similar name. If any other packages are required (errors compiling, etc.), let me know so I can update this.
3. Actually compiling should be as simple as opening a terminal in the working directory and running 'make && sudo make install'. If you get no errors, qdl should be installed and able to run from any location, and the compile process shouldn't take much time at all.
4. Before running qdl, ModemManager needs to be disabled, as it can interfere with accessing the phone in EDL mode. In Ubuntu (and most systemd-based distros) you can ensure that it's stopped by running ' sudo systemctl stop ModemMangager'. If you need the ModemManager service, make sure to restart it when you're done.
5. Extract the TWRP zip to an easily-accessed folder, like ~/twrp, and place the firehose mbn in the same folder.
6. Navigate to the TWRP folder and open a terminal there. Now would be a good time to plug in your phone and enter EDL with 'adb reboot edl'.
6a. If your phone was already connected in EDL mode before stopping ModemManager, you might need to reboot it and enter EDL again.
7. If you're in the same directory as the TWRP files, you should be able to start flashing by running 'sudo qdl prog_emmc_firehose_8917.mbn rawprogram_recovery.xml patch0.xml'.
8. If everything's good, you should see some output on your screen, and the phone should reboot momentarily. If the command finishes without output, ModemManager or something similar may have interfered. Make sure ModemManager is stopped, reboot your phone into EDL mode again, and try again. If it hangs at Waiting for EDL device, you're not running the program with admin privileges or your phone isn't in EDL mode.
9. Once the process has finished and your phone has rebooted, you should have TWRP installed. Boot into it by holding Vol Up while rebooting.
That's it! Verify that TWRP is working as expected by doing some test backups and restores, etc. Note that TWRP builds for this device are still sort of experimental; decrypting the data partition may not work for some users, and keeping data encrypted while trying to flash Magisk will not work - you will need to wipe and decrypt the device. If you're satisfied just with TWRP, there's not much else you need to do. If you want to run Magisk or decrypt your device for other reasons, keep reading.
Part 2: Removing Forced Encryption
By default, the device encrypts the data partition without input from the user. This is not ideal, and even if TWRP can decrypt and mount your data partition, from my experience Magisk's init process apparently gets things wrong and tries to write to data before its decrypted - whether that's actually the case or not, the fact of the matter is that Magisk has corrupted my data partition every time I've tried to install it while data was encrypted.
DO NOT flash any zip that removes dm-verity and force encryption - these modify the boot and recovery partitions, and the stock kernel doesn't like the way they do it. If you've flashed the patched boot.img first then you'll at least be able to boot to your system partition afterwards, but it'll still nuke recovery even with a custom kernel installed on it. If you're still using the stock boot.img, you'll get boot loops and won't be able to access recovery; your only choice is to enter diagnostic mode, and reflashing anything from that point is a gigantic pain in the ass, so please, just don't. If you feel the need to do it regardless, please please please reflash your boot and recovery images before rebooting.
Counter-intuitively, the quickest and most painless way to stop the device from force-encrypting itself is to modify the fstab on the vendor partition - the boot partition has no fstab files, and the ones in the TWRP recovery image are already set to make encryption optional. Place the fstab.qcom on the phone's microSD card (internal storage will work if you don't have one, as long as TWRP can access your internal storage; if not, use adb push/pull rather than the below commands), boot into TWRP, and adb shell into your device by USB; if done while in TWRP, you should have root permissions. If your PC doesn't see your phone as an ADB-ready device, go to Mount settings in TWRP and tap on the option to disable MTP; after confirming that ADB works, feel free to re-enable MTP. Once ADB is working, run the following commands:
Code:
mount /vendor
cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak
cp /external_sd/fstab.qcom /vendor/etc/fstab.qcom
chmod 644 /vendor/etc/fstab.qcom
umount vendor
.
That's the simple part - you've replaced the fstab on the vendor partition with one that tells the device that encryption is optional, and backed up the original to your microSD as fstab.qcom.bak, just in case. Now you need to actually remove the existing encryption, which will wipe all the user data from the device. If that hasn't scared you out of continuing, read on.
While we're still in TWRP, we need to go to the Wipe menu. From there, we need to Format Data. It'll give you warnings in a scarier color than I did, but you'll have to type yes and continue regardless. Once that's done, hit the back button a couple times before rebooting. Do a standard factory reset, then reboot.
From there, it may take a couple tries for the device to boot normally as it reformats and repopulates the data partition. If you find yourself stuck on a black screen, reboot again, and if it keeps happening, boot into TWRP and then reboot to System from the reboot menu. Eventually, you should be able to get back to the device setup screen, and depending on your security settings beforehand, you may be prompted to enter your PIN, password, or Google account information.
From here, you should be able to mount, backup, and restore your data partition in TWRP without any issues. If you want to go further and root your device, keep reading for the Magisk guide.
Part 3: Any Magisk You'd Like
Note: Magisk and encrypted data partitions do not play nicely together. Follow through Part 2 first, or you'll have headaches.
ZTE's kernel has a custom SELinux plugin called policyproc, which in short doesn't play nice with a lot of things that modify what happens during the kernel's startup sequence. Unfortunately, modifying the startup sequence is what Magisk does best, and versions of Magisk past v16.7 don't play well with the stock kernel.
If you're fine with v16.7, you can download the zip from its Github release page and flash it through TWRP. However, it doesn't support current versions of Magisk Manager or the uninstaller zip, and naturally it doesn't have all the features of newer versions.
This is where the patched boot image comes in. Basically, it's the stock kernel, rebuilt with policyproc disabled, stuffed into the stock boot.img and replacing the original kernel. It's not entirely perfect as ZTE deliberately left out bits of the source, but even working around that, the kernel seems to run fine after nearly a week of testing on my own device. Still, if you run into any issues that don't show up with the stock kernel, please let me know.
So. you can take that patched boot image and install newer versions of Magisk whichever way you'd like. The default method would be to use TWRP to flash the patched boot image, then flash the latest Magisk zip (v20.1 at the time of writing). Alternatively, you could put the patched boot.img on your microSD or internal storage, install the Magisk Manager app, use it to patch Magisk into the patched boot image, then use TWRP to flash the patched-patched-image to the boot partition. Either way should work fine, and honestly I'm hoping if you've made it this far you don't need further instruction on how to get Magisk installed.
Note that on the first reboot after installing Magisk, the phone may reboot again before loading the system normally. I assume this is standard practice for initializing Magisk, but honestly I have no idea.
With that, you've done just about everything you came here to do. If you still feel like tweaking and possibly bricking your phone, however, scroll on down to Part 4.
Part 3.5: Updating Your Magisk Install
When a Magisk update is available, the Magisk Manager app will generally push a notification to you. Letting the manager handle the upgrade is a good way to get bootloops, unfortunately; upgrading requires re-patching and re-flashing the boot image, and most apps running in system mode seem to handle the task poorly on the R2. If you want to update to a newer version of Magisk, it'd be best to reboot into TWRP, flash the 'clean' Magisk-ready boot image, then install the zip for the version of Magisk you want to update to. You don't need to uninstall previous versions of Magisk to do this, and it should be doable even if a previous Magisk upgrade left you stuck in a boot loop. Note that if you previously told the Manager to 'hide' itself, you may end up with two Manager apps after the update; it should be safe to remove either of them, although the one with the Magisk Manager name will need to be re-hidden if you choose to keep it.
Part 4: Going Even Further Beyond - Project Treble and You
Google requires that all Android phones releasing with Android Oreo or newer must support the Treble framework: generally speaking, anything that's 'stock' Android lives on the system partition, and anything manufacturer or carrier specific exists on the vendor partition. This has allowed for developers to create generic system images, or GSI, consisting of particular Android system partitions that should run on a variety of Treble-enabled devices. And wouldn't you know it, the R2 launched with Oreo, and you've got a couple handy methods of writing system images to your device, through TWRP and EDL flashers.
So, does that mean the R2 supports these GSIs? Not really! Honestly, it's more that it's up to curious people to find out. I've been able to get phhussons's Oreo image working, but that's a bit boring on a device that supports Oreo out of the box. A couple more highly modified Pie builds failed to boot properly, either hanging on their splash screen or crashing the display manager before getting through setup.
There's also the fact that they're generally only distributed as sparse system.img files, something I had trouble flashing with QFIL, and up until about 18 hours before this guide went live, the only TWRP build I had for the R2 could only write images to the boot and recovery partitions, not system, so writing them meant I had to decompress them to a standard EXT4 image and then flash them with QFIL, which wasn't a lot of fun to mess with. In short, testing's been pretty limited, but this build of TWRP should make it much easier for anyone to flash whatever image they'd like. If you feel like being a guinea pig, we'd all love to hear the results! If you want to test, you should look for A-only, ARM64 images.
Questions and Issues
My phone is bootlooping after leaving recovery!
If you haven't messed with system partitions in a way that might cause a bootloop, reboot to recovery and try to boot to system from there. If it continues, reflash your boot image (and Magisk afterwards, if necessary, removing the extra Manager app that might pop up in your app tray if you've got Manager disguised in its settings).
I can't access ADB or MTP from recovery.
It happens sometimes, especially in Windows; just toggle MTP on/off from inside TWRP, or unplug and replug your USB cable.
My phone says I need a factory reset, but TWRP just reboots.
This generally happens if something messed with the encrypted data partition. Do not tap the factory reset button on your phone; instead, power off entirely and manually reboot into TWRP by hilding Vol Up while booting. Perform a factory reset (and format data if necessary) from there, then reboot.
(to be populated)
Credits
@deadman96385 - for uploading the tools that made this possible and the stock ROMs that saved my ass more than a few times
@famewolf - for feedback on what did/didn't work in the last guide
@asderdd - for his Axon 7 kernel work which I shamelessly copied to get Magisk working
Anyone who's contributed to Magisk or TWRP over the years, and the maintainers of the moto e5+ device tree for TWRP since I used most of their branch.
Sources
Kernel source, specifically the tree used for the Magisk patch
TWRP device tree
@FEGuy
Attempted to flash the new twrp via zip....acted like it worked but when I when to install section only boot and recovery were options....so I installed the twrp image itself to recovery....rebooted back into recovery and got a black screen. Additional attempts to go into recovery did same thing. I'll attempt to use the flashify app under factory rom to restore previous copy of twrp. It should work as I had magisk going...I think.
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
FEGuy said:
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.
What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
Click to expand...
Click to collapse
Always possible I hosed something....I grabbed the img of the previously good twrp and flashed it via flashify app...said it worked but when booted to recovery got same black screen. I'm about to experiment with the usb drivers you mentioned vs the ZTE USB ones in the op...they conflict with each other so uninstalling old ones.
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
FEGuy said:
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.
Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.
I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.
In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
Click to expand...
Click to collapse
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
---------- Post added at 02:01 AM ---------- Previous post was at 01:48 AM ----------
famewolf said:
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?
If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.
Click to expand...
Click to collapse
I tried dd if=twrp-3.3.1-1-z5151v.img of=/dev/block/bootdevice/by-name/recovery and did same with new signed one. I still get black screen when recovery "loads". At this point I'm going to have to get something figured out with qdl or qfil.
Yeah, I wasn't sure if dd was going to work or not.
Try the QDLoad drivers again in Windows, make sure that the device is using them. If it's not showing up as a COM port in device manager, force it to use the proper Qualcomm driver, which on my system installed to C:\Windows\system32\qcusbcer.sys - I don't know if that installed with the QDLoad drivers or with QPST/QFIL itself.
As for qdl, I don't know; it's been hassle-free for me, for the most part. If you're sure you're in EDL mode and not diagnostics or something, an output from lsusb might help diagnose the issue. If the debug flag isn't providing useful info, might as well try it without. I don't know if there's services other than modemmanager that might interfere with qdl, it could depend on distro.
EDIT: I'll also preemptively warn against trying the TWRP app to flash; it'll do about as much good as flashify.
Will tackle it "later" in the morning. Thanks for the quick followup. I might see more clearly in morning when not so frustrated with it. I swear I haven't had this many issues with getting twrp installed in a long time.
*update* Ok so I lied....I completely recompiled qdl from https://github.com/andersson/qdl and it's working as expected..I used it to flash the original twrp. I then used that twrp to flash the twrp-signed.img and rebooted back into it with no issues.
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
The Treble pie loaded ok...I did do a factory reset so data would not conflict..it did do one reboot before loading normally. See screenshots.
The First 4 are from when it was initially installed. The later photo's I had added gapps, a few apps, snapped a picture to use as wallpaper and various other minor things. I found it to be faster under treble pie than it was with factory oreo. I haven't found anything that didn't work yet on it.
Launcher: Evie Launcher
famewolf said:
I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
Click to expand...
Click to collapse
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I tried the current installer which failed. I didn't locate the 16.7 uninstaller.
*update* I did finally locate the 16.7 Magisk Uninstaller.
FEGuy said:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.
In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
Click to expand...
Click to collapse
I also installed open gapps pico pie amd64 version on top of the pie rom without issue. I have magisk 16.7 working with treble without issue so maybe it was just the newer versions that had issues?
My 2nd R2 (You are a bad influence) arrived today. Anything you need tested on a stock model? Here's hoping qdl/qfil cooperates 1 last time.
When you were patching the kernel did you see anything that was keeping the phone in LTE only mode for calls? When I get a minute I'm going to put my t-mobile sim into the R2 and see what it will do under the pie rom but since it's still using same kernel I wondered if that would be an issue. We know on the stock rom all calls have to use VOLTE.
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
FEGuy said:
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.
I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
Click to expand...
Click to collapse
Had a couple of thoughts...a quick and dirty method to provide "flash and go" rom's might be to do a nandroid of just system or maybe system and boot for whatever rom and make that available for download. I also know there are methods to convert a nandroid into a flashable zip although I haven't done it before. This was more a thought for folks wanting to go to b12 that already had twrp...simple enough for an existing b12 user to back up system. I have verified swapping between nandroid pie vs stock oreo works ok (assuming you are restoring the right data for each). Also the fingerprint "images" continued to work fine after a restore.....on a previous device when we did a nandroid restore we would have to delete the file storing pin/fingerprints as they wouldn't let you into the phone until re-recorded. It also worked if you remember to turn those OFF before doing the backup....wasn't an issue with the R2. The phone is noticeably more responsive on pie than it was with stock oreo. I'm curious whether you found that to be the case with treble oreo?
Oh minor annoyance....I changed the device id to z5151 which is what it showed under stock but when doing an adb shell the command line is "phhgsi_arm64_a:/" Do you know how to change that? This will change it temporarily till next login: https://stackoverflow.com/questions/33069161/how-to-change-adb-shell-prompt-name-before-the-mark
You could try using setprop as root to set ro.build.product or ro.product.device back to Z5151, or manually edit the build.prop; beyond that, I don't know of a simpler way.
I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.
thanks!!!!!!!!
rangolizardy said:
I'm having trouble getting the mobile data working on pie,
I can search for networks and it finds visible but it wont connect.
Click to expand...
Click to collapse
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.
rangolizardy said:
The visible apn was missing from my pie,
If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Remove the () Someone else can maybe post the intact link as i seem to be unable to.
After this 4G works like a charm.
Click to expand...
Click to collapse
Posted for rangolizardy: http://mega.nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY
Any other important tweaks anyone has made to the treble pie image?
Factory Wallpapers are here: https://forum.xda-developers.com/showpost.php?p=79011562&postcount=2
I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0