Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **
A few answers to common questions:
YES - this breaks Samsung Pay and probably Android Pay (you will NOT be able to use Samsung Pay after root)
YES - this process is reversible by several methods, one of which would be simply doing a factory reset and re-flashing the complete Nougat Android 7.0 Firmware files in Odin, More details on this below.
NO - this process does NOT trip the KNOX counter
NO - there is no TWRP or custom recovery for this method of rooting
NO - there is no XPOSED framwork for Android 7.0 currently (as of today's date)
YES - There is a Android 7.0 custom rom! Thanks to @jrkruse https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Many thanks to the people who released the files! I am only posting the file's in a single easy to find post along with my experience and instructions which may or may not work for you! these instructions may or may not be right. these instruction may or may not be missing crucial steps. USE AND PROCEED AT YOUR OWN RISK! No one is responsible if you damage your device. CERTAINLY NOT ME!
PLEASE GIVE THANKS WHERE ITS DESERVED! Thank you :good:
MANY THANKS TO
@JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
@princecomsy https://forum.xda-developers.com/member.php?u=5028474
@jrkruse https://forum.xda-developers.com/member.php?u=1949695
@jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
@Chainfire for creating SuperSU and other great android utilities.
I'm sure there are many others, but I don't know who all created what, so I'm only listing those who I know - if I messed this up, I'm sorry in advance.
ENG (AP) files for S7 and S7E (from this post https://forum.xda-developers.com/showpost.php?p=71271898&postcount=28 )
https://www.androidfilehost.com/?fid=457095661767141717
(This is the ENGINEER boot kernel boot.tar file you'll be flashing in the special modified Odin software from your PC)
*edit: newer method available!* SuperSU 2.79 root.bat file (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=817550096634750763
(This is the command prompt script you'll execute from a CMD prompt from a windows PC that installs the needed files for root access like SuperSU)
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
jrkruse said:
This root method will reset your fingerprints and lockscreen security it will also fix fingerprint issue this should help with issues of not recognizing your fingerprint after you root. I had to modify the latest SuperSu to get root to stick on SuperSU 2.82.
Here is a what I did:
The new supolicy from 2.82 Version was causing root not to stick. So I used the supolicy from 2.81 Version. I modded the SuperSu.apk to ingnore the supolicy not being 2.82 Version So you wont get asked to update the SuperSU binaries.
The SU binary is updated to 2.82 and all other files.
If you delete SuperSU apk dont reinstall it from playstore use the one in Above zip
Click to expand...
Click to collapse
**Alternative** Many thanks to active contributor of this thread @Quickvic30 for the info in post #688
https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
Who offer's another root.bat alternative which gave him better performance. Please check out that post for the file, and click the thanks button.
PLEASE REMEMBER: Results for rooting vary on each and every device. Lag, Performance, Heat - These things vary from device to device. YOUR MILEAGE WILL VARY!
** You will use either the originally posted SuperSU 2.79 root.bat, or the ALTERNATE version posted by Quickvic30 - DO NOT USE BOTH - CHOOSE ONE METHOD OR THE OTHER ** OR TRY EACH INDIVIDUALLY AND SEE WHICH GIVES YOU ACCEPTABLE RESULTS **
VoLTE VMM - IMservice hurricane icon fix thanks to jrkruse post #453
https://www.androidfilehost.com/?fid=457095661767144116
jrkruse said:
Sorry about all the VOLTE Icon problems
If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix
This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk
Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!
Click to expand...
Click to collapse
ALTERNATIVE SOLUTION from Post #413: Thanks to @sabresfan post #413
You will need to download and use only the PrinceComsy modified Odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Kernel Adiutor can be downloaded from Play Store
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Original stock firmware files can be found on these sites or searching XDA
https://www.sammobile.com/firmwares/
http://updato.com/
** Edit: More information about returning to STOCK below on this first post **
**EDIT: Samsung USB driver's direct from Samsung web site http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I'm not sure if you need the ADB files installed system wide or not? But you can also download and install the 15 minute ADB drivers. (use google or search XDA)
AGAIN: I did this to my Samsung Galaxy S7 Edge on T-mobile G935T RUNNING ANDROID 7.0 NOUGAT I believe this will work with other USA released carrier variants using Qualcomm chipset (T-mobile, AT&T, Verizon and Sprint)... BUT YOU DO THIS AT YOUR OWN RISK.
EDIT: MAKE SURE YOU ARE ON ANDROID 7.0 NOUGAT - OBVIOUSLY. (Baseband Version: G935TUVU4BQB1 in the case of a G935T S7 Edge) :fingers-crossed:
This process did NOT cause any data or application loss for me. I did this procedure from an OTA upgrade to N from MM.
Obviously, Download all needed files in advance and unzip accordingly.
Put your phone in download mode (Volume Down, Home and Power) then click home again to continue to download mode
Launch the modified ODIN on your PC
Unzip ENG BOOT file and get the boot.tar for your device (in my case it was the S7edge_qualcomm.tar was the file I needed for the S7 Edge) DO NOT UNZIP THE TAR FILE.
Put that .tar file in AP section of ODIN
Connect your phone, you should see a lighted COM port selected in ODIN meaning your good to go.
CLICK START in Odin. You Phone will flash the file quickly and restart.
Let it boot up fully and wait until you can unlock the phone (go to desktop of the phone)
Now open a CMD prompt on the computer and navigate to where you downloaded and unzipped the SuperSU 2.79 earlier
in the CMD prompt type root.bat this will push the required files to the phone and it will be rooted when its completed.
After a few minutes your phone will restart, and you will have SuperSU and root access on Android 7.0 Nougat.
This is how I rooted my SM-G935T Samsung Galaxy S7 Edge on Android 7.0 Nougat. Yes this is a bootloader locked T-mobile branded device.
Please feel free to add or correct anything here in the posts below!
EDIT: You'll want to install Kernel Auditor from the Play store, grant it supersu permission, and set both cpu govenors to ONDEMAND and set apply on boot. (core 1&2 default to performance and core 3&4 default to interactive - set both to ondemand and apply on boot)
EDIT2: You may want to experiment with the CPU governors in Kernel Adiutor (that's actually the correct spelling according to the author). It's been suggested CONSERVATIVE will give you better battery life than ONDEMAND. So you'll want to try the available options and see which results in acceptable balance of performance and battery life for you.
GOOD LUCK! AND THANK YOU!
I HOPE THIS HELPS PEOPLE GET ROOT ON THEIR USA QUALCOMM DEVICES
PLEASE TAKE A MOMENT TO THANK THE PEOPLE WHO BROUGHT THIS INFORMATION TO YOU.
Returning to STOCK Android 7.0 Nougat
You will need to have Odin installed (same modified Odin linked above should work fine)
You can download stock Android 7.0 Nougat firmware from
https://www.sammobile.com/firmwares/
http://updato.com/
For the T-mobile S7 Edge G935T ONLY
File: SM-G935T_G935TUVU4BQB1.zip
Google Drive Link: https://drive.google.com/file/d/0B9QvmNs9dpD-LTdwQUgzejk5ZGM/view
From thread (thanks to it's OP): https://forum.xda-developers.com/tmobile-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3558242
Thanks to @Krog18 for linking to Verizon firmware files in post https://forum.xda-developers.com/showpost.php?p=71383942&postcount=359
G930V QA2 Stock fw: https://www.androidfilehost.com/?fid=529152257862709174
G935V QA2 Stock fw: https://www.androidfilehost.com/?fid=817550096634752305
Thanks to @Quickvic30 for linking to the AT&T firmware files in post https://forum.xda-developers.com/showpost.php?p=71601821&postcount=608
G935A QA6 https://www.androidfilehost.com/?fid=745425885120713605
When you extract the .zip file for your device, you have 2 options for the CSC section. One file will erase all existing data and apps, reverting your phone to a like new state. The other will preserve your currently installed apps and data.
CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL ERASE ALL EXISTING DATA ON THE DEVICE
HOME_CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL PRESERVE (*NOT ERASE) ANY EXISTING DATA FROM THE DEVICE
Obviously you can only choose 1 of the CSC files. Using the HOME_CSC keeps your existing data, and the other CSC formats your phone.
Thanks to @billa (https://forum.xda-developers.com/member.php?u=293193) for taking taking the time to put these tips together for everyone.
Slightly edited by me
billa said:
Note (and suggestions)
----
Before and after rooting wipe the cache.
For tweak settings to stick, must reboot multiple times.
Security Updates OFF
--------------------
Settings > Lock Screen > Security > Other Security > Security Policy Updates > OFF and Wi-Fi only
Disable (things to disable after root - Use Titanium Backup or Package Disabler Pro for Samsung, both available from the Play Store - Worth the price to buy!)
-------
Samsung DM Phone Interface
Samsung DM Service
SecurityLogAgent
com.sec.android.soagent
com.wssyncmldm
tethering.automation
tethering.provisions
After Eng-Boot (root is complete)
--------------
Install Kernel Auditor, and set both CPU govenors to "OnDemand" and set apply on boot.
Set cores 1&2/3&4 to "OnDemand" and apply on boot.
EDIT: Experiment with governor settings until a balance of power and performance is reached. Kernel Adiutor is available from the Play Store
Performance tweaks
------------------
GovTuner - set to interactive and performance
Kernel Auditor
Kernel Toolkit
LSpeeds
SSD Boost
SHealth fix
-----------
Set ro.config.tima to 0 in build.prop
WiFi passwords fix
------------------
Set ro.securestorage.support to false in build.prop
VOLTE/RCS icons OFF
-------------------
Copy the imsservice.apk from the root zip to
/system/priv-app/imsservice/
and set permissions to -rw-r--r--
Data toggle
-----------
Use SQLite editor and add MobileData to a string in settings.db
Busybox fix
-----------
Install busybox to /system/xbin instead of /su/xbin
Sprint LTE fix
--------------
In Build.Prop change the following:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
OR
Go into settings
Click Connections
Click Wi-Fi Calling
Click Cellular Network Preferred
Go back two times and click on Mobile networks
Select Network mode and select 3G/2G (auto connect)
Restart your phone and call 611 just to make sure the call goes through
Hangup and go back to Network mode and switch back to LTE mode
Click to expand...
Click to collapse
As always THANKS to all the users who continue to contribute to this thread, and to all the people involved in bringing you this information so you can ROOT your Samsung Galaxy S7 or Samsung Galaxy S7 Edge on Android 7.0 Nougat!
I will continue to update this first page with relevant links, details and information in an attempt to keep the information easier to find for everyone.
Take a moment to press the THANKS button!
So how's the lag for you compared to the eng boot on marshmallow?
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
nitroevo said:
So how's the lag for you compared to the eng boot on marshmallow?
Click to expand...
Click to collapse
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
vazquezcmp said:
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
Click to expand...
Click to collapse
I think the SuperSU root file has the needed ADB files, so once you navigate to that folder in CMD (command prompt on the pc for those a little lost), I assume those files are whats used to push the root.bat script to the phone? I think we are both right? but I'm not 100% that's why I mention the ADB drivers, which were already installed on this PC I used. This information was scattered in several threads, I was hoping to put all the links in 1 place so we can maybe get this working smoothly for EVERYBODY.:good:
Since you did it too, and you're getting smooth results what steps did I miss? if any.:fingers-crossed:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
vazquezcmp said:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
Click to expand...
Click to collapse
Excellent.. Glad it worked.
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer app or ADB and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Reboot and you have Google assistant!
Quickvic30 said:
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
LMAO... That's funny, we should be getting in legit soon... :good:
(but, I'm gonna enable it too! :silly: )
Will this work for Sprint? Thanks
Regnuf said:
Will this work for Sprint? Thanks
Click to expand...
Click to collapse
I believe so... but since I don't have a sprint device to test, I have no idea. (but I think YES)
Thank you sir! Going to be doing this to my S7 standard right now.
Araltd said:
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
Click to expand...
Click to collapse
to make it stick on reboot i think there should be a setting there that says apply on boot
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Araltd said:
VoLTE VMM icon fix (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=673368273298935963
You will need to download the PrinceComsy odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Click to expand...
Click to collapse
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
jrkruse said:
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
Click to expand...
Click to collapse
Hey thanks for coming over here...
As I mentioned, I don't care about the big hurricane looking icon, but the com.sec.vmimservice icon notification (looks like a red face) pops up multiple times in my status bar whenever there is texting activity. Send or receive. That's what I want to get rid of.
Edit: here's the notification pulled down so you can see.. I have that little red icon in my status bar several times right now... I am using Android messages, and I use Tmobile digits on my other phone (note 4) just fyi... Not sure if everybody is seeing that or if it's unique to either Android messages (formerly Google messenger) or digits service by Tmobile?
{
"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"
}
nitroevo said:
to make it stick on reboot i think there should be a setting there that says apply on boot
Click to expand...
Click to collapse
Somewhere between reboots (of which there have been many tonight) the setting finally stuck. I also set kernel auditor (adiutor) to set the settings immediately on reboot with no delays.
To me, there is still significant lagging, even with on demand Governor set. I read somewhere about setting the min/max also, those values are always fluctuating in the kernel adiutor program, I'm not sure how to properly set those.... But I also tried kernel tool and had similar results. Just fyi.
cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
Araltd said:
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
Click to expand...
Click to collapse
If you set govenors to conservative you will get way better battery life.
jrkruse said:
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
If you set govenors to conservative you will get way better battery life.
Click to expand...
Click to collapse
Please refresh, I posted a picture of the imservice notification I'm getting. Thanks!
Related
NabiRootXD v2
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible
Weeee more Easter goodies haha.
thanks aicjofs
Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time
Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?
aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?
I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.
ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?
i am trying to get this tablet to use my network opendns settings and web filters
Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.
Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.
yup getting the dead droid
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse
aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.
Q&A for [MOD]/[HOWTO] Unlock your native hotspot app [UPDATE 11/10]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD]/[HOWTO] Unlock your native hotspot app [UPDATE 11/10]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
wtb better instructions.
yeah dude. I was thinking the instructions weren't very well explained.
You need to give some indication as to which version is appropriate to download.
Your initial instructions are pretty vague and leave one guessing/assuming to upload the latest version of the update. Which softbricks the CFRooted S5s (sprint).
....
ALso there are issues with both of the ADB downloads you recommend. the SDK has issues with path length on install. The other installs fine but in windows there is no path 'ie e:\'
so .... how to unbrick
Pherox said:
yeah dude. I was thinking the instructions weren't very well explained.
You need to give some indication as to which version is appropriate to download.
Your initial instructions are pretty vague and leave one guessing/assuming to upload the latest version of the update. Which softbricks the CFRooted S5s (sprint).
....
ALso there are issues with both of the ADB downloads you recommend. the SDK has issues with path length on install. The other installs fine but in windows there is no path 'ie e:\'
so .... how to unbrick
Click to expand...
Click to collapse
Unbrick with odin.
The downloads are named after the version of the rom you are on.
I didn't really recommend those adb, other people did so I provided the link.
Theres video tutorials floating around, not done by me. FWIW, I barely have time to make this mod and I don't even use the stock roms anymore, so I dont really have the time to hold peoples hands. You should do research before you flash anything on any phone.
If you wanna write something up that you feel would make it easier for an inexperienced person to understand, feel free to shoot me a link and I will include it in OP. Until then you are the first person I have heard of to softbrick, I am assuming this is because you flashed the wrong version. This which version do I flash question has been asked several times in the thread, so the answer is there, but to recap:
The last three letters of your rom version should match the three letter code on the download file.
Use the version tagged odex for odexed roms, and deodex for deodexed roms.
The first versions modify your APNs, they should work on any version of the stock rom, however it is unreliable and will need to be reflashed after a PRL update.
Flash the zip from recovery.
I will update the OP to have less directions since they seem to have mislead you, my apologies.
Native Hotspot S5 NE5
Hey I just flashed the 1.4 version for NE5 for the Sprint version of the S5.
My issue is that there is no toggle in the notification pull down. Is there anyway I can add it?
Thanks
Yes there is. I don't know how, but search for variations of "how to add toggles"
Please help
I have a Sprint Note 3 running on 4.4.4 with a Build Number ending with NH7. Does anyone know of a way to get the hotspot to work with this build? Any help would GREATLY BE APPRECIATED!
Dw4yne187 said:
I have a Sprint Note 3 running on 4.4.4 with a Build Number ending with NH7. Does anyone know of a way to get the hotspot to work with this build? Any help would GREATLY BE APPRECIATED!
Click to expand...
Click to collapse
Have you tried Galaxy tools? It works on the S5 with 4.4.4. It is not in the play store, search for it on XDA and install.
No, I haven't used galaxy tools yet. I will give it a try now. Thanks for trying to help man, I appreciate it.
Sprint detailed procedure to unlock your native hotspot?
I have a Sprint Galaxy S5 version 4.4.2, NE5 type stock and want to perform the unlock your native hotspot routine by miked63017.
I have completed his step 1 under prerequisites and the root went fine I think. I am a little concerned since I am a first time rooter and pretty much a
Nooby to the process. I am a little concerned about step 2 and beyond:
Can I use the TWRP from the playstore for this custom recovery?
Can i make a backup with TWRP also or Titanium backup?
Would the .zip be unlockHotspot-1.4-NE5-ODEX.zip and would I flash it with ODIN?
Here is the process as best I can tell from the XDA posts. The asterisks are my notes :
NOTE---
This has been tested by a few people in the original thread with success, your mileage may vary. As always, you are responsible for your phone, and it's warranty.
--PREREQUISITES--
1 Your phone must be rooted, I have followed the guide here http://forum.xda-developers.com/show....php?t=2696537
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) ! NE5***************
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices (Galaxy S1, S2, S3, S4, Galaxy Note, Note2, Note3, dozens of Tab models, etc!) and has clocked over 22.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter and trips the KNOX warranty flag!
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
ODIN Installation (detailed)
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Download
SM-G900F (International Qualcomm): CF-Auto-Root-klte-kltexx-smg900f.zip
SM-G900H (International Exynos): CF-Auto-Root-k3g-k3gxx-smg900h.zip
SM-G900I (Oceania?): CF-Auto-Root-klte-kltedv-smg900i.zip
SM-G900L (Korea): CF-Auto-Root-kltelgt-kltelgt-smg900l.zip
SM-G900M (Middle and South America?): CF-Auto-Root-klte-klteub-smg900m.zip
SM-G900R4 (US Cellular): CF-Auto-Root-klteusc-klteusc-smg900r4.zip
SM-G900T (T-Mobile US): CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
********* SM-G900P (Sprint): CF-Auto-Root-kltespr-kltespr-smg900p.zip **************
SM-G900T1 (Metro PCS): CF-Auto-Root-kltemetropcs-kltemetropcs-smg900t1.zip
SM-G900W8 (Canada): CF-Auto-Root-kltecan-kltevl-smg900w8.zip
SM-G900S (Korea?): CF-Auto-Root-klteskt-klteskt-smg900s.zip
SM-G901F: http://download.chainfire.eu/481/CF-...xx-smg901f.zip
SM-G906K: http://download.chainfire.eu/539/CF-...tt-smg906k.zip
SM-G906L: http://download.chainfire.eu/540/CF-...gt-smg906l.zip
SM-G906S: http://download.chainfire.eu/541/CF-...kt-smg906s.zip
Other models
CF-Auto-Root is not yet available for all models - one stock firmwares for these models become available, let me know, and I'll make the corresponding CF-Auto-Roots. Make sure to check the main CF-Auto-Root site as well, as models may be listed there that are not listed here.
2 You must have a custom recovery installed, I have used the one from here http://forum.xda-developers.com/show....php?t=2697762
Quote:
Originally Posted by Dees_Troy
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
Sprint SM-G900P Samsung Galaxy S5
So here is the step by step:
1. Make a backup------with the above TWRP from play store? *****************
2. Download the appropriate zip for you rom version. The three letter code in the filename should match the last three letters of your rom version. Odex version is for odexed roms, deodex version for deodexed roms.
*********File Type: zip unlockHotspot-1.4-NE5-ODEX.zip ************
3. Flash the zip and reboot. ****** Using ODIN? *****************
Thanks to @Scolias for jumping on the zip creation so fast, and being the first one to test the modification (other than me)
**UPDATE***
For the original mod version:
If you update your PRL you will need to reflash and reboot:
Thanks for the heads up @Y.G.
**UPDATE 2***
Added Icon in Notification panel, Thanks @eyecon82 for providing the SQL data for Notification panel. Also added some SQL to try to enable bluetooth and usb tethering, let me know how they work. Download and flash version 1.2 for these updates.
***Update 3***
Since it has already been pulled into a DeOdex for our phone, and the same modification used on the s3 KitKat I figured I would post the services.jar files here too. You need to be on DeOdex for these to work, and note that the latest DeOdex available for our Sprint S5 from @sleshepic already has this built in. These are mostly just for reference, and so all the hotspot downloads are in one easy to find place.
ND2 Services.jar - http://forum.xda-developers.com/atta...8&d=1398719510
NCB Services.jar - http://forum.xda-developers.com/atta...9&d=1398822075
Rename the file to Services.jar for your baseband version, backup your old copy and put the new one in. Using the Services.jar survives PRL updates and does not require the usage of the previous mods.
If anyone needs it I can post the changes in the smali files here, its pretty simple though using grep in tethering.smali, it involves setting a var to 0x0 from 0x1, in the tethering.smali by the dun_required string.
***Update 4***
Big thanks to @rocket321 for helping me out with odexing. I have made a flashable zip that uses services.jar instead of modifying the APN. Flashing the new version will remove all APN modifications from the previous versions and install the new services,jar for odex or de-odex versions. Currently I have only built for ND2 roms, if there is any need for NCB let me know and I will work on it. New files attached below, just flash from recovery and tether . Enjoy and if this helps you please give thanks, and don't forget to thank @rocket321 as well.
Anybody making ROMs feel free to incorporate the files below, otherwise they should be able to be flashed right on top of the rom, assuming there are no modifications to the services.jar file in the desired ROM..
***Update 5***
Added NCB zips, built jars and odexes using my new tool modStudio
***Update 6***
Added NE5 versions to downloads, big thanks to @crawrj and @townsenk for making them
***Update 7***
Added NI3 versions, need testing the size of the ODEX package has shrunk and I am not sure why. Please let me know if you guys notice anything weird, so far so good for me but YMMV. Added back new dynamic way of adding to the notification panel, again let me know how this works out.
***Update 8***
Added new NI3 versions for testing, make a backup before testing JIC
***Update 9***
Cleaned up OP a little
Attached Files
File Type: zip unlockHotspot.zip - [Click for QR Code] (396.5 KB, 1275 views)
File Type: zip unlockHotspot-1.2.zip - [Click for QR Code] (396.8 KB, 2590 views)
File Type: zip unlockHotspot-1.3-ND2-DEODEX.zip - [Click for QR Code] (3.59 MB, 491 views)
File Type: zip unlockHotspot-1.3-ND2-ODEX.zip - [Click for QR Code] (6.72 MB, 969 views)
File Type: zip unlockHotspot-1.3-NCB-DEODEX.zip - [Click for QR Code] (3.45 MB, 246 views)
File Type: zip unlockHotspot-1.3-NCB-ODEX.zip - [Click for QR Code] (6.47 MB, 551 views)
File Type: zip unlockHotspot-1.4-NE5-DEODEX.zip - [Click for QR Code] (3.71 MB, 807 views)
------------File Type: zip unlockHotspot-1.4-NE5-ODEX.zip - [Click for QR Code] (6.96 MB, 1874 views)----------------
File Type: zip unlockHotspot-1.5-NI3-ODEX.zip - [Click for QR Code] (3.72 MB, 252 views)
File Type: zip unlockHotspot-1.5-NI3-DEODEX.zip - [Click for QR Code] (3.72 MB, 248 views)
File Type: zip unlockHotspot-1.6-NI3-DEODEX.zip - [Click for QR Code] (3.72 MB, 74 views)
File Type: zip unlockHotspot-1.6-NI3-ODEX.zip - [Click for QR Code] (7.02 MB, 190 views)
Last edited by miked63017; 16th November 2014 at 08:32 AM.
flashing NI3 appears to disable private mode
new poster, but def been checking this forum out for a while. ive been doing a fair amount of testing to solve my private mode not working issue. i flashed stock rom NI3 using Odin one-click mentioned in the forum, added philz and CFroot and tested root. all is well and private mode is still working.
after flashing the unlockHotspot-1.6-NI3-ODEX.zip mod, private mode is broken. i ran a nandroid back to before flashing the NI3 zip, and all is well. i then decided to install the unlockHotspot-1.6-NI3-ODEX.zip mod again to test my theory, same results...private mode not functional.
i did a thread search and did not see this mentioned previously. just a warning for all those out there that do use private mode and want wifi tether functionality.
also is anyone aware of a workaround?
Thanks!
Hotspot kikat and Sprint Solved Finally...
HOTSPOT sprint for free!!! SOLVED could be at&t Verizon or another COMPANY but need some support I left you my video and a Description But now those people with kikat that application works fantastic
¡¡¡HOTSPOT¡¡¡ Sprint Free, Solved
{
"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"
}
wifi tethering sprints s5 with 4.4.4
So there is no nk4 builds for wifi tethering on sprints s5 with 4.4.4? Really need access to wifi tethering. Any help is appreciated.
randomh3ro1 said:
So there is no nk4 builds for wifi tethering on sprints s5 with 4.4.4? Really need access to wifi tethering. Any help is appreciated.
Click to expand...
Click to collapse
Download Galaxy Tools and select hotspot. Done.
Sent from my icrap 2 using Tapatalk HD
Anybody available to test my new hotspot project? PM me with your email address if you are interested, let me know what build you are on and what device, this should work for any sprint device but I have only tested on my SM-G900P running the NKD Lollipop build.
Forgot to mention, you must be rooted.
Started thread here http://forum.xda-developers.com/spr...apps/app-gs5-native-hotspot-unlocker-t2980905
Just rooted my s5 the wifi tethering zips you have for it don't have the same build #
My device ends build BOA6 it's a sprint s5. (excuse me, I'm a noob)
E2online said:
My device ends build BOA6 it's a sprint s5. (excuse me, I'm a noob)
Click to expand...
Click to collapse
Install the latest version of the app available via the link one post above yours.
Software Version and build number ends in 0A6
Hi today I Rooted my phone and installed a custom recovery but then I saw that you said in your post that the 3 letters or numbers of the rom determined which file I would download but my galaxy s5 software version and build number (which I dont know if the software version or the build number is the rom) ends in 0A6. What should I do or is this mod not for me? Thanks for your help!
Install zip for G900PVPU2BOD3
Is there an install zip for G900PVPU2BOD3?
Tethering Problem on Samsung GS5 au SCL23
Brought this phone from Japan.....i'm having the same tethering issue....the hotspot turns off instantly the moment i turn it on....my phone is not rooted and the build number of my phone ends with NJ1....please help me to fix it.....thanks in advance
Verizon S5 Hotspot Validation Error Msg
So i have a Verizon S5 whenever i try to turn on my Hotspot Validation Error pops up after configuration. i am not in the USA so i cannot contact Verizon and im using a dofferent sim in my GS5. Any solutions to fix my problem???
First and foremost
As per the standard, anything and everything you do with your device is your responsibility, I nor the creators are responsible for what you do. I personally haven't mastered mind control yet, but I'm getting there. So the only person you can blame if something goes wrong is yourself. This doesn't mean you're on your own if you do mess up, which is why I started this.
You're gonna need these
LG drivers
http://www.lg.com/us/support/software-firmware-drivers
Stock firmware
LG LV3 (TMO)
LG ms210 stock. Always download firmware with TMO region code. https://lg-firmwares.com/lg-m210sv-firmwares/firmwares/
Mpcs
LG ms210 stock. Always download firmware with MTP region code. https://lg-firmwares.com/lg-ms210-firmwares/firmwares/
Rooting and installing a rom
Foreword
Same warning applies as usual. Anything you choose to do with your device at any point is your responsibility. I nor the original creators are liable for what you happen to do with your device.
You're gonna need these
TWRP https://forum.xda-developers.com/android/development/twrp-lg-aristo-aka-lv3-t3656019
SuperSU + Data partition encryption disabler or no Dmverity https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047
Universal adb drivers for windows https://forum.xda-developers.com/showthread.php?t=2317790
A little bit of patience.
Unlocking your bootloader and installing your recovery
Starting off, you'll want to install the ADB drivers (which will always help down the line) and activate USB debugging by going to settings/about/software and clicking on build number until you get the toast about developer mode. Now go back to settings and head to developer mode and clicking debugging+enable oem unlock. once finished plug your device in using your USB and open up a privileged command prompt (windows key + x).
I'd recommend copying any relevant data from your phone because the next step will lead to a clean format.
From here you can type in adb reboot bootloader and switch to fastboot before now typing in fastboot oem unlock.
Yay, your bootloader is unlocked.
Now, upon starting your phone, a new notification will pop up that looks worrisome. It's not, the screen is just a warning that your device cannot be covered under warranty basically. (Just reflash to stock and lock your bootloader fastboot oem lock to remove this warning and return fully to stock)
From here you can install your preferred recovery. Since TWRP is what's available, we'll go with that.
Now you can go to your downloads folder on your computer and decompress the TWRP archived (if it's been compressed), for ease of access we're gonna extract the file to C:/ which will allow the command prompt to pull the file without having to sort through your files.
Double check the file name making sure it is set as recovery.img, now go back to your command prompt and type in fastboot flash recovery C:/recovery.img
Once the prompt finishes with the install, you can type in fastboot reboot recovery
Once in recovery, swipe to allow system modifications and go to wipe before formatting the data partition. Now you can go to the folder on your computer which contains the SuperSU and no Dmverity packages you downloaded prior. Open a new file explorer directing to your device's memory, since you installed the LG drivers you can simply drag and drop the pertaining files directly into your aristo's storage even though you're still in TWRP. The moment you've been waiting for, just flash no Dmverity then SuperSU. Congrats, you've just rooted your phone and didn't start nuclear war.
Custom and stock roms
You're gonna need these
SuperSU (just in case)
A backup of stock (just in case)
Patience
Xtremelora's iPioneer stock rom. Based on the metro 10i firmware
Flash from recovery, wipe data and cache for a clean wipe or just install for a dirty flash.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Xtremelora's iPioneer slim rom based on the metro 10i firmware
Do a full wipe for the first time around to avoid conflicts with the original set up. After that, you can just flash the rom for a dirty flash.
https://forum.xda-developers.com/android/development/rom-ipioneer-slim-10i-v1-t3662043/post73530917#post73530917
Note 1; Both roms can be flashed without wiping system due to @xtremelora thinking ahead and adding a line to wipe system in the update script.
Note 2; both roms can be flashed on the TMobile model (the LV3), but you'll have to make changes to the apn settings to make it work.
[email protected]'s lineage 14 port
This is gonna be a step out of the ordinary. I've tried turning this into a flashable zip, but without a proper update binary, it's gonna remain a backup package.
To start off, you're gonna want to make a backup of your current system on TWRP. (This will help twice over)
Once the backup is finished, reboot. Follow this link and download from herehttps://forum.xda-developers.com/showpost.php?p=73943988&postcount=65
Once that's finished, decompress the archive. Take the folder you created and move it to the location of where ever you created a backup. There should be a single folder in the TWRP location (it's name will have lgms210 in it) drop the lineage backup folder here next to the backup you made previously.
Once the files are moved, reboot into recovery and wipe system/data/dalvik/cache to avoid any incompatibility. (You can keep your sd)
Restore the backup, wipe dalvik and cache.
Presto change-o
apn settings quoted from T-Mobile support
From any Home screen, tap Apps.
Tap Settings.
Scroll to 'NETWORK CONNECTIONS,' then tap More networks.
Tap Mobile networks.
Tap Access Point Names.
To reset your APN, tap the Menu icon and then tap Reset to default.
If available, tap the T-Mobile US LTE APN (the bullet point fills with green).
To verify your APN, tap T-Mobile US LTE with the bullet point filled with green.
Verify and update the following settings for the Data APN:
Name: T-Mobile US LTE
APN: fast.t-mobile.com
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
Multimedia message proxy: <Not set>
Multimedia message port: <Not set>
MCC: 310
MNC: 260
Authentication type: None
APN Type: default,supl,mms OR Internet+MMS
Default Android provides a text field to enter: default,supl,mms
Samsung provides an Internet+MMS radio button to select.
APN protocol: IPv6
APN roaming protocol: IPv4
Turn APN on/off: APN turned on
Bearer: Unspecified
Mobile virtual network operator type: None
Mobile virtual network operator value: <Not set>
Tap the Menu key in the top right.
Tap Save.
Tap the desired APN profile you want to use. The bullet point fills with green next to the APN profile
Click to expand...
Click to collapse
Common fixes for common problems
captchas
An issue I've been hearing about recently is captchas won't load on certain sites. 4chan being the primary problem, but any site using disqus have also had a couple issues with the captcha mechanism.
If your captcha won't load, switch to desktop mode on your preferred browser. If that doesn't work, wipe cache. Not data.
installing Magisk
A couple users may hit a wall on both of xtremelora's roms where you cannot modify the boot partition while installing magisk. It's a completely normal problem and no, youre not screwed out of that mod managing love.
For this you're gonna need:
an unmodified boot partition or a boot backup: https://www.dropbox.com/s/v6lnq6cymzhzyu2/boot.img?dl=0
the latest magisk found here: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Magisk init.d enabler: https://forum.xda-developers.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305
The no-dmverity package found in the rom flashing section.
a little patience.
Starting off, reboot into recovery with your preferred method. (terminal, adb, hard button) We're gonna do this as a dirty flash to avoid the heartbreaking rebuild of lost data. Now, start off by flashing your rom of choice (will be updated if need be for new roms), once finished you can navigate to where ever the boot.img was saved to. On the bottom of your screen, you should see a tab saying Install image click it and all your files (minus folders and any image files) will vanish.
Now boot.img should be visible. Click that and you'll be directed to a new screen asking where you want to flash the img to. Select boot and click on flash, swipe when it asks if you're sure. (You're sure) Finish this off by flashing no-dmverity.
Now that your system has been hooked up right, the next step would be installing magisk itself. Just click and flash since there's nothing that interesting here. Once magisk is installed, finish it off by installing the Magisk init.d package. (this will allow you to use init without having to move certain files to Post.fs, which means different mods like feradroid and KITANA mod can be used systemlessly)
Finishing up, youre gonna want to remove all instances of supersu since it's installed by default. (titanium backup can do that for you)
Congrats, you now have a fully functioning magisk on your device and dont have to worry about incompatibility.
Lineage is slowing down
A small issue I've noticed with lineage room over the last few months are abrupt slowdowns involving the entropy pool availability. This is a relatively simple fix.
Download any kernel manager (I'm currently using device manager) enter the app and look for the section either pertaining to the kernel itself or to the entropy pool. You'll notice that the availability is pretty low in regards to how fast it is being used. Just change the availability up to 1024 and save it.
Bam, massive speed up for everything.
(You may have to reset the settings once you restart since the kernel resets too)
I think I messed up, wat do
There's a plethora of issues one can run into during their time using an Android device. Some being easier than other to figure out and resolve. This little section is gonna cover problems that'll arise with the Aristo
So you deleted your boot animation
This one is an easier fix.
Just drop this Zip file into the media folder on /system
https://www.dropbox.com/s/ouoy2rdlcz6k7mr/bootanimation.zip?dl=0
Tips and tricks for power users
A recent contribution brought around by new member @unicornsw4g
Disabling thermal throttling on the LG aristo/lv3
now for those who would like to disable hardware throttling on the LG Aristo I've come up with my own way to disable that rather than to go through to each core and tweak their control file as Need4Sneed has done. for my little trick you simply need to navigate to /system/etc. now from there scroll down until you see two thermal engine files: thermal-engine-8937.conf and thermal-engine-default.conf
simply change conf from within the file extension name to bak then restart. NO NEED TO DELETE THE FILES. Safer than sorry. after that your cpu will by default reach 1.4ghz. now that may be sweet as heck but you gotta remember; speed generates heat. also the snapdragon 425 is known to get hot. well thats a lie... its known to get scorching hot. like teabag a volcano hot. well you get the point. this is NOT for heavy gaming, trust me I've tried. and well my finger got burnt, yes it gets that hot. without thermal files your phone will not take preventative measures to dissipate heat but rather hit the max temperature and shut itself down all while grilling your fingers like chicken tenders. yum. so with that said its only natural. though this cannot in any way prevent your phone from booting it may cause hardware damage which may get so bad it eventually may prevent your phone from booting in that instance I TAKE NO RESPONSIBILITY FOR BROKEN HARDWARE OR SOFTWARE.
upon messing around with the clock speeds with kernel auditor which does require root (messi2080) <-- da root mon --> seems the best clock speed is around 1.094ghz and the gpu speed must be lowered to at least 400mhz if your feeling ballsy then maybe you can fade 523mhz but never 598mhz. lets just say its like a really fast motorcycle with no cooling. simply put the motorcycle explodes. same concept and I wouldn't push a phone that hard as sadly :'( its my daily driver I suppose maybe the same does or doesn't apply to you but do have fun just be careful.
Click to expand...
Click to collapse
Or simply put, you can reboot into recovery before mounting the system partition and traveling into the file browser from the advanced tab on the TWRP main screen.
From there you can explore to /system/etc and look for thermal-engine-8937.conf and thermal-engine-default.conf. click on one and add .bak to the end of the file's name. Do the same for the other. (This way, if anything happens. You can boot into recovery and just change them back to normal)
Restart your phone and your CPU has been unlocked.
Now you wanna program the CPU and GPU using a kernel manager.
I used kernel audiutor for this next step, not much work now.
Cpu Min-960
Cpu Max-1094
Cpu Governor-ondemand
Input boost freq-1094 for the first two cores and 1248 for the last two.
Thermal-vdd restrictions. (Undervolts the kernel to safe levels at higher speed to mitigate heat)
Gpu max-484.
DO NOT TOUCH THE GPU GOVERNOR.
With these settings, i can play a couple different games at full brightness without worrying about heat dispersal.
TURBO GPU MAGISK MODULE
Been using a new magisk module recently. After a couple days of using it, my battery drain has slowed down to maybe 3% an hour while gaming. Module can be found in magisk manager or in the link provided below. If this helps you like it helped me, make sure to throw a thanks or 3 at EmperorEye.
https://forum.xda-developers.com/apps/magisk/module-gpu-turbo-boost-t3808541
Credit where credit is due
@messi2050 for delivering the original TWRP and his work on the build tree allowing us to progress.
@xtremelora for both the ipioneer stock and the ipioneer slim roms
@[email protected] for the new and improved TWRP and now including the lineage 14.1 rom he ported.
@unicornsw4g for the CPU/gpu throttling trick
@jcadduono for providing the no-Dmverity package.
@topjohnwu for magisk.
androidexpert35 for the init.d Magisk module.
@Chainfire for just about anything else.
I found a new update today (29th, may be was there before????)
BTW: don't install it on top of the Slim rom, you may face several issues.
{
"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"
}
xtremelora said:
I found a new update today (29th, may be was there before????)
BTW: don't install it on top of the Slim rom, you may face several issues.
Click to expand...
Click to collapse
It won't install on top of your slim rom since we have a custom recovery thankfully.
ninjasinabag said:
It won't install on top of your slim rom since we have a custom recovery thankfully.
Click to expand...
Click to collapse
A little FYI about the current OTA update. I'm not running a custom ROM, but Ive successfully applied the newest firmware (M21010r) using LGUP and was able to reflash root and custom recovery with no issues..
hifi1969 said:
A little FYI about the current OTA update. I'm not running a custom ROM, but Ive successfully applied the newest firmware (M21010r) using LGUP and was able to reflash root and custom recovery with no issues..
Click to expand...
Click to collapse
Does still say 7.0 or 7.0.x under Android Version
What about the software patch date??
xtremelora said:
Does still say 7.0 or 7.0.x under Android Version
What about the software patch date??
Click to expand...
Click to collapse
Still says 7.0
Android Security Patch Level September 1, 2017
hifi1969 said:
Still says 7.0
Android Security Patch Level September 1, 2017
Click to expand...
Click to collapse
It's a small security update with a couple of minor tweaks to the kernel. 1400 mhz was locked out to avoid overheating. Still attainable if you do the thermal config trick.
Otherwise, this was only about the security update. Nothing fancy.
Updates will be slightly delayed.
Friend handed me the Galaxy on5 and I just received the note 4 the other day. Now I'm swimming in samsungs on top of the S4 and my tab 2. This is gonna be fun.
It's been recently brought to attention that lg pulled some sneaky beaky business with the background code for their devices. There is a small applet that checks for elevated privileges (root) on stock software and forces a mild to massive slowdown on different devices. I don't know exactly how bad it is on other devices, but it would explain why the aristo goes from battery friendly before root, to just barely skimming the average discharge rate.
For anyone still using stock software, the fix can be found here. https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
This is in alpha, make sure you create a proper backup of your boot partition just in case.
For those of you who still want to use magisk in the process. Flash the original boot image, flash magisk, install the root check Disabler, reflash magisk.
It's been recently brought to attention that lg pulled some sneaky beaky business with the background code for their devices. There is a small applet that checks for elevated privileges (root) on stock software and forces a mild to massive slowdown on different devices. I don't know exactly how bad it is on other devices, but it would explain why the aristo goes from battery friendly before root, to just barely skimming the average discharge rate.
For anyone still using stock software, the fix can be found here. https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
This is in alpha, make sure you create a proper backup of your boot partition just in case.
For those of you who still want to use magisk in the process. Flash the original boot image, flash magisk, install the root check Disabler, reflash magisk.
ninjasinabag said:
It's been recently brought to attention that lg pulled some sneaky beaky business with the background code for their devices. There is a small applet that checks for elevated privileges (root) on stock software and forces a mild to massive slowdown on different devices. I don't know exactly how bad it is on other devices, but it would explain why the aristo goes from battery friendly before root, to just barely skimming the average discharge rate.
For anyone still using stock software, the fix can be found here. https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
This is in alpha, make sure you create a proper backup of your boot partition just in case.
For those of you who still want to use magisk in the process. Flash the original boot image, flash magisk, install the root check Disabler, reflash magisk.
Click to expand...
Click to collapse
I don't have issues with the battery at all... Maybe depends on how you use the phone.
xtremelora said:
I don't have issues with the battery at all... Maybe depends on how you use the phone.
Click to expand...
Click to collapse
I already did my tests on it. The battery was discharging a lot faster after rooting, deep sleep was never reached and it started to waste battery when the screen was off.
has anyone tried sound tweaks?..
i.e. like dolby/viper mods
mixer_paths.xml settings?
i've been trying to bump up the incall ear and speaker ..
it's not overly obvious what it's called in the mixer_paths...
i bumped up the speaker overall a little....
but,that seemed to lower incall ear/speaker for some reason
oh...and a huge favor i need to ask...can anyone post a copy of the stock mixer_paths.xml please??? ...
i backed up mine and somehow lost it ...the remaining backup is after the first tweaks...before finding out the poop with incall...
thanks for even reading this
i know i post alot of hot air....
Hey guys, I think I have a slight situation. I unlocked my phones bootloader, rooted it and put a custom recovery on it. had an init script that was on there and my phone got messed up after installing an update. Anyway, my problem is that while in recovery, my internal storage can not be seen or accessed. I'm thinking that the update couldnt install because of that. Should i be worried that I cant see my internal storage while in recovery? I have installed a couple of black gapps through recovery though, so i know i can install from micsd at least. Any thoughts or help please?
Cyconumnum said:
has anyone tried sound tweaks?..
i.e. like dolby/viper mods
mixer_paths.xml settings?
i've been trying to bump up the incall ear and speaker ..
it's not overly obvious what it's called in the mixer_paths...
i bumped up the speaker overall a little....
but,that seemed to lower incall ear/speaker for some reason
oh...and a huge favor i need to ask...can anyone post a copy of the stock mixer_paths.xml please??? ...
i backed up mine and somehow lost it ...the remaining backup is after the first tweaks...before finding out the poop with incall...
thanks for even reading this
i know i post alot of hot air....
Click to expand...
Click to collapse
Sorry about the lateness.
I've actually been testing a lot in this general direction.
You can extract the original mixer_paths file from either xtremelora's slim rom, or his OG stock rom.
On the matter of a decent sound mod. I've been using the Quasar mod chain since some of the other mods involving Dolby don't take memory into consideration. Leading to Dolby running into force closes the completely screw things up.
(Also, don't install any sound mods using magisk. The systemless setup is slightly out of control.)
[HOWTO] root Galaxy S8 S8+ CRGH CRI5 CRI1 CRJ5 CRK1 CRL3 TWRP&ambasadii stock kernel
[Guide]How to root Galaxy S8 or S8+ SM-G95xF/D with CRGH, CRI5 CRI1 CRJ5 CRK1 CRL3 ROM using TWRP and ambasadii stock kernel (which is including magisk)?
This topic is showing how to root à Samsung Galaxy S8 or S8+ (Oreo - 8.0.0) Exynos with the CRGH or CRI5 ROM where Samsung has again added some security features to avoid the rooting device.
Previous found topics seem running fine until the device reboot. It is stucked on SAMSUNG starting message with on top "Only official released binaries are allowed to be flashed"
WARNING:
- At end of this process, keep checked your OEM unlock.
- Rooting and bricking your device is at your own risk.
Tested on:
- S8 SM-G950FD Exynos model ROM G950FXXU3CRGH from sammobile G95xF_Stock_Kernel_CRGH_v2.zip and TWRP 3.2.3-2-dreamlte
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI5 from sammobile G95xF_Stock_Kernel_CRI5.zip and TWRP 3.2.3-2-dreamlte
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI5 G95xF_Stock_Kernel_CRI5_v2.zip and TWRP 3.2.3-2-dreamlte thanks @gtrs36 for testing this new version of rooted boot loader
- S8 SM-G950FD Exynos model ROM G950FXXU4CRI1 G95xF_Stock_Kernel_CRI5_v2.zip and TWRP 3.2.3-2-dreamlte thanks @Jon Saridjan for tests using the mix of ROM and rooted boot loader
- S8+ SM-G955F Exynos model ROM G955FXXU4CRJ5 Stock_Kernel_G95xF_CRJ5.zip and TWRP 3.2.3-2-dream2lte thanks @.RadziU. for testing this new version of rooted boot loader
- S8+ SM-G955F ROM CRJ5 Stock_Kernel_G95xF_CRJ5.zip and TWRP 3.2.3-2-dream2lte thanks @DarthKyria for testing this version of rooted boot loader
Please keep me in touch to update this list!
Download links:
- TWRP
** Thanks @teamwin
** For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
** For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
- @ambasadii stock kernel
** For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
Link unavailable, use the below version** For S8 and S8+ G95xF_Stock_Kernel_CRI5.zip download from https://androidfilehost.com/?fid=1322778262904009192
** For S8 and S8+ G95xF_Stock_Kernel_CRI5_v2.zip download from https://androidfilehost.com/?fid=1322778262904024753
** For S8 and S8+ Stock_Kernel_G95xF_CRJ5.zip found there: https://androidfilehost.com/?fid=11410932744536984254
** For S8 and S8+ Stock_Kernel_G95xF_CRK1.zip found there: https://androidfilehost.com/?fid=11410963190603872259
** For S8 and S8+ Stock_Kernel_G95xF_CRL3.zip found there: https://androidfilehost.com/?fid=11410963190603878451
** Other versions are there https://androidfilehost.com/?w=files&flid=260111
- Odin3-v3.13.1 download on https://samsungodin.com/
- Samsung drivers download on https://samsungodin.com/
- MagiskManager-v6.0.0.apk from MagiskManagerDOTcom
- RootChecker.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
- RootCheckerPro.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheckp&hl=en
- Titanium Backup from https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
1. Backup your important data from internal storage before proceeding towards the installation. (I'm using smart switch and helium for some other apps. Unfortunately, smart switch is not able to fully backed up bluemail, Call Recorder Pro and so on)
2. Now go to Settings - About Phone - Software Information - Tap on Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON. (It should be blue) If not found, set the date 8 days ago, uncheck "Automatic System Update" and reboot.
4. Power off device and boot into download mode by pressing the VOLUME DOWN, BIXBY KEY, and POWER buttons then VOLUME UP button to continue
5. Connect your device to the PC.
6. Now open Odin3-v3.13.1 as administrator and you should see a blue-highlighted box with a random COM number, which means you have proper drivers installed.
7. Put on our SD card (or on USB key - in case of USB key, you gonna use the usb dongle to flash/install - )
** MagiskManager-v6.0.0.apk
** RootCheckPro.apk
** G95xF_Stock_Kernel_CRGH_v2.zip
____ or
** G95xF_Stock_Kernel_CRI5.zip
8. In the tab Options, uncheck "Auto Reboot" and kept checked "F. Reset Time". Click on the AP button and choose the twrp-3.2.3-0-dreamXlte.img.tar file.
9. Press the START button.
10. Now after Odin says PASS,
____10.1 Press the VOLUME DOWN, BIXBY KEY, and POWER buttons until the screen goes black
____10.2 Press VOLUME UP, BIXBY KEY, and POWER buttons for about 4 seconds until you should be in TWRP recovery.
11. Now allow the modifications by swiping and go to WIPE option.
12. <WARNING> Disconnect your device from your PC </WARNING> and choose "Format Data" - Type "yes" - ENTER.
____<WARNING> If at the Format Data step, you got red messages, complete the below step 13 and redo both step 12&13 </WARNING>
13. Go back to Home menu and choose “Reboot” then “Recovery” also choose “Swipe to Install”.
14. Once rebooted, choose “Keep Read Only” if needed then “Install” then flash G95xF_Stock_Kernel_CRGH_v2.zip or G95xF_Stock_Kernel_CRI5.zip
15. The device should reboot, it's taking a long time. Enter your PIN code. Select your language and so on... Ignore the popup asking you to reboot because of the SIM Card changed"
16. Enjoy, your phone is rooted, Magisk and TWRP are both installed!
17. Install RootCheckPro.apk and start it, tape VERIFY ROOT the app should said your device has root access. Don't be afraid about SuperSU @Chainfire not installed.
18. Install MagiskManager-v6.0.0.apk, start it. Control the SafetyNet, all should be green.
19. Install Titanium Backup, start it. You should see a popup asking you to agree the root access.
20. Start TWRP app, agree the new installation, reboot.
21. Reboot once the device is stable without any notifications.
22. Restore your data thru smart switch and helium or other apps.
Thanks for
@ambasadii for the updated stock kernel
@teamwin for TWRP
@topjohnwu for Magisk
@joeykrim for Root Checker Pro
@Titanium Track for Titanium Backup
@Ruturaj Kadam for the initial topic
@max lee for video and photo topic
@coyote950 for the help
@Chainfire for SuperSU
Please find below the rooting result displayed by root checker pro. Thanks @joeykrim
{
"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"
}
And the ROM version even OEM unlock ON
I am G955F ; Still on R16NW.G955FXXU1CRB7 boot loader not unlocked yet. Is best practice (Sept, 23rd 2018) to upgrade and use this guide? Or use another for my U1 (older) bootloader?
Loupps said:
[Guide]How to root Galaxy S8 or S8+ SM-G95xF/D with CRGH ROM august 2018 using TWRP and ambasadii stock kernel (which is including magisk)?
This topic is showing how to root à Samsung Galaxy S8 or S8+ (Oreo - 8.0.0) Exynos with the CRGH ROM from august 2018 where Samsung has again added some security features to avoid the rooting device.
Previous found topics seem running fine until the device reboot. It is stucked on SAMSUNG starting message with on top "Only official released binaries are allowed to be flashed"
WARNING:
- At end of this process, keep checked your OEM unlock. Maybe, the risk is to flash back an official ROM if you restart your phone with OEM unlock unchecked.
- Rooting and bricking your device is at your own risk.
Tested on:
- SM-G950FD Exynos model ROM G950FXXU3CRGH from sammobile patch august 2018
Please keep me in touch to update this list.
Download links:
- TWRP
* For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
* For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
- @ambasadii stock kernel
* For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
* Other versions are there https://androidfilehost.com/?w=files&flid=260111
- Odin3-v3.13.1 download on https://samsungodin.com/
- Samsung drivers download on https://samsungodin.com/
- MagiskManager-v6.0.0.apk from https://******************/
- RootCheckPro.apk from https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
- Titanium Backup from https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
1. Backup your important data from internal storage before proceeding towards the installation. (I'm using smart switch and helium for some other apps. Unfortunately, smart switch is not able to fully backed up bluemail, Call Recorder Pro and so on)
2. Now go to Settings - About Phone - Software Information - Tap on Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON. (It should be blue) If not found, set the date 8 days ago, uncheck "Automatic System Update" and reboot.
4. Power off device and boot into download mode by pressing the VOLUME DOWN, BIXBY KEY, and POWER buttons then VOLUME UP button to continue
5. Connect your device to the PC.
6. Now open Odin3-v3.13.1 as administrator and you should see a blue-highlighted box with a random COM number, which means you have proper drivers installed.
7. Put on our SD card (or on USB key - in case of USB key, you gonna use the usb dongle to flash/install - )
- MagiskManager-v6.0.0.apk
- RootCheckPro.apk
- G95xF_Stock_Kernel_CRGH_v2.zip
8. In the tab Options, uncheck "Auto Reboot" and kept checked "F. Reset Time". Click on the AP button and choose the TWRP.tar file.
For S8 twrp-3.2.3-0-dreamlte.img.tar download on https://dl.twrp.me/dreamlte/
For S8+ twrp-3.2.3-0-dream2lte.img.tar download on https://dl.twrp.me/dream2lte/
Thanks @teamwin
9. Press the START button.
10. Now after Odin says PASS,
10.1 Press the VOLUME DOWN, BIXBY KEY, and POWER buttons until the screen goes black
10.2 Press VOLUME UP, BIXBY KEY, and POWER buttons for about 4 seconds until you should be in TWRP recovery.
11. Now allow the modifications and go to WIPE option.
12. <WARNING> Disconnect your device from your PC </WARNING> and choose FORMAT DATA - Type yes - ENTER.
13. Go back to Home menu and choose “Reboot” then “Recovery” also choose “Swipe to Install”.
14. Once rebooted, choose “Keep Read Only” then “Install” then flash G95xF_Stock_Kernel_CRGH_v2.zip
For S8 and S8+ G95xF_Stock_Kernel_CRGH_v2.zip download from https://androidfilehost.com/?fid=1322778262903989728
Other versions are there https://androidfilehost.com/?w=files&flid=260111
Thanks @ambasadii
15. The device should reboot, it's taking a long time. Enter your PIN code. Select your language and so on... Ignore the popup asking you to reboot because of the SIM Card changed"
16. Enjoy, your phone is rooted, Magisk and TWRP are both installed!
17. Install RootCheckPro.apk and start it, tape VERIFY ROOT the app should said your device has root access. Don't be afraid about SuperSU @Chainfire not installed.
18. Install MagiskManager-v6.0.0.apk, start it. Control the SafetyNet, all should be green.
19. Install Titanium Backup, start it. You should see a popup asking you to agree the root access.
20. Start TWRP app, agree the new installation, reboot.
21. Reboot once the device is stable without any notifications.
22. Restore your data thru smart switch and helium or other apps.
Thanks for
@ambasadii for the updated stock kernel
@teamwin for TWRP
@topjohnwu for Magisk
@JoeyKrim for Root Checker Pro
@Titanium Track for Titanium Backup
@Ruturaj Kadam for the initial topic
@max lee for video and photo topic
@coyote950 for the help
@Chainfire for SuperSU
Click to expand...
Click to collapse
Can we use fresher driver from ? Driver : USB_Drivers_1.5.27.0.rar 26-Aug-2016 02:35 10636k
https://samsungusbdriver.com/category/download
https://samsungusbdriver.com/download/samsung-driver-v1-5-65-0
Or -v1.5.65.0 as the best ?
Also why are you installing Titanium Backup, what was intended for it?
futiless said:
I am G955F ; Still on R16NW.G955FXXU1CRB7 boot loader not unlocked yet. Is best practice (Sept, 23rd 2018) to upgrade and use this guide? Or use another for my U1 (older) bootloader?
Click to expand...
Click to collapse
Hello,
The stock G95xF_Stock_Kernel_CRB7.zip found there https://androidfilehost.com/?fid=746010030569956301 does'nt contain magisk nor twrp.
So you have to flash both stock G95xF_Stock_Kernel_CRB7.zip and magisk.
Please refer this topic https://www.xda-developers.com/how-to-install-magisk/ to download magisk
Then you will have to install "magisk manager" and "official twrp app"
futiless said:
Can we use fresher driver from ? Driver : USB_Drivers_1.5.27.0.rar 26-Aug-2016 02:35 10636k
https://samsungusbdriver.com/category/download
https://samsungusbdriver.com/download/samsung-driver-v1-5-65-0
Or -v1.5.65.0 as the best ?
Also why are you installing Titanium Backup, what was intended for it?
Click to expand...
Click to collapse
If you are able to communicate with the device thru odin (the box COM should be blue with a random port number and you should see Added!!! or Removed!!! when you connect or disconnect your device) or backup your device thru smart switch, it's mean your driver are running fine.
Titanium Backup is able to perform a full backup on SDcard as there is a root access.
Smart Swich is not able to fully backed up (right access issue) the configurations for some applications. And it's forgot the SMS notification configuration, strange!!
Helium (without root access) is able to backed up few applications but said it's ok for some others even if it's failed. Don't properly work on SDcard, so you have to move the carbon directory from internal device to SDcard before flash or format any things.
Regarding installing magisk I understand … but would you recommend me to upgrade my bootloader and phone or use CRB7 and upgrade after. Which is a better option?
After rooting, how do we update with next version of the firmware without loosing root?
Probably flash the new firmware using Odin without restart and then flash the corresponding kernel version from the link above using TWRP?
futiless said:
Regarding installing magisk I understand … but would you recommend me to upgrade my bootloader and phone or use CRB7 and upgrade after. Which is a better option?
Click to expand...
Click to collapse
I don't know the release date for the CRB7 but according to sammobile the latest version seems CRI5. I hope the previous number is not important. For my tested version, it's 3 and for this version it's 4.
I've checked the G95xF_Stock_Kernel_CRI5.zip is containing TWRP and magisk for S8 and S8+.
So my advise is to
- upgrade first to G950FXXU4CRI5 (download from sammobile ; from my point of view, the country is not an issuer) using odin without restore your data at end then
- apply the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip
- restore your data
alexander_sirakov said:
After rooting, how do we update with next version of the firmware without loosing root?
Probably flash the new firmware using Odin without restart and then flash the corresponding kernel version from the link above using TWRP?
Click to expand...
Click to collapse
Of cause you will lost the root access if you're upgrading your device except if you use some specific tools. This is because, the upgrade consist to put an image into a partition. I don't know if you're talking about automatic system update but on my side, it's off as I want to stay to my current stable version.
CRI5 gas got sama path for rooting
Can be rooted by using sama method
950f CRI5
Loupps said:
I don't know the release date for the CRB7 but according to sammobile the latest version seems CRI5. I hope the previous number is not important. For my tested version, it's 3 and for this version it's 4.
I've checked the G95xF_Stock_Kernel_CRI5.zip is containing TWRP and magisk for S8 and S8+.
So my advise is to
- upgrade first to G950FXXU4CRI5 (download from sammobile ; from my point of view, the country is not an issuer) using odin without restore your data at end then
- apply the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip
- restore your data
Click to expand...
Click to collapse
First of all the data partition is of no value ... yet..
This almost completes my question yet, my CRB7 is from Feb and you say upgrade to CRI5 which would in fact be a downgrade. This still begs the question as well,,, I guess I should have mentioned I want to run the latest bootloader and 8.1/9 roms with recent modem etc.
Should I CRI5 provide me any benefit lost by upgrading the bootloader?
futiless said:
First of all the data partition is of no value ... yet..
This almost completes my question yet, my CRB7 is from Feb and you say upgrade to CRI5 which would in fact be a downgrade. This still begs the question as well,,, I guess I should have mentioned I want to run the latest bootloader and 8.1/9 roms with recent modem etc.
Should I CRI5 provide me any benefit lost by upgrading the bootloader?
Click to expand...
Click to collapse
I mean about an upgrade from CRB7 to CRI5 using an official released version. The CRI5 has been officially released on september 2018.
The ambasadii stock kernel seems to collaspe the boot partition (to avoid the stucking message) and the recovery partition (to install TWRP instead of the official recovery tool) and root the system.
So adventure is adventure, it should work to only flash the CRI5 bootloader, flash TWRP and then flash the ambasadii stock kernel. At end, you shoud be root and kept your CRB7 rom.
But keep in mind that at the format data step, you will lost all your personal configuration. So I'm clearly don't understand why you are trying to mix rom.
Where to get the CRI5 original bootloader?
I’m in catch 22, shall i root or wait for slow Mo and emoji’s updates? Man I’m on the exact firmware, that your guide is written for. Would there be any way to update once I’m rooted to slow Mo emoji firmware without breaking root? Sorry last time i rooted was Android 4.4.4 and Android 6.0.1.. Since them days, so much has changed Samsung really is making it harder to root there high end smartphones, i am rooting Galaxy Tab S4 10.5 but that feels so easy to root, as i don’t want to go through re-root backing up process etc. on the S8+?
So my question is shall i wait for the slow Mo update? And then root? Or shall i root and then apply slow Mo update? What’s the best course of action? Or what would you do? Thanks..
N1NJATH3ORY said:
I’m in catch 22, shall i root or wait for slow Mo and emoji’s updates? Man I’m on the exact firmware, that your guide is written for. Would there be any way to update once I’m rooted to slow Mo emoji firmware without breaking root? Sorry last time i rooted was Android 4.4.4 and Android 6.0.1.. Since them days, so much has changed Samsung really is making it harder to root there high end smartphones, i am rooting Galaxy Tab S4 10.5 but that feels so easy to root, as i don’t want to go through re-root backing up process etc. on the S8+?
So my question is shall i wait for the slow Mo update? And then root? Or shall i root and then apply slow Mo update? What’s the best course of action? Or what would you do? Thanks..
Click to expand...
Click to collapse
Please have a look on this video https://www.youtube.com/watch?v=Npc-PCutvvA CRI5 is compatible with slow Mo and emoji’s.
So, my advice is to download the official CRI5 version (on SamMobile firmware) then rooting using the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip and you will have slow MO and be able to install emoji's apps.
futiless said:
Where to get the CRI5 original bootloader?
Click to expand...
Click to collapse
You have to download the fully ROM on SamMobile firmware (that's should be a good thing in case of recover process to have the fully rom on your side)
Loupps said:
Please have a look on this video https://www.youtube.com/watch?v=Npc-PCutvvA CRI5 is compatible with slow Mo and emoji’s.
So, my advice is to download the official CRI5 version (on SamMobile firmware) then rooting using the root process following this topic by flashing G95xF_Stock_Kernel_CRI5.zip instead of G95xF_Stock_Kernel_CRGH_v2.zip and you will have slow MO and be able to install emoji's apps.
Click to expand...
Click to collapse
Thank you so much! Quick question i purchased my S8+direct from Samsung website there's no BTU CRI5 ? Does it matter lets say i pick poland or spain ? See pics for what i mean.. Thanks again..
P.S.S Sammobile sucks for firmware download speeds, updato.com is so fast 2 mins fully donwloaded, sammobile 2 hours unless your on a piad plan!
N1NJATH3ORY said:
Thank you so much! Quick question i purchased my S8+direct from Samsung website there's no BTU CRI5 ? Does it matter lets say i pick poland or spain ? See pics for what i mean.. Thanks again..
P.S.S Sammobile sucks for firmware download speeds, updato.com is so fast 2 mins fully donwloaded, sammobile 2 hours unless your on a piad plan!
Click to expand...
Click to collapse
The country is not an issue except if you phone is locked to a network. That was the case in the past but now we brough phone from china and network operator from another way. So two ways: wait a couple of day the UK released version or download the south africa one as they are speacking british english too.
You're right about sammobile but I'm downloading and go to another activity... I've never tried updato.com, sammobile is more readable from my point of view.
Anyway to use this without sd card?
RikoudoS said:
Anyway to use this without sd card?
Click to expand...
Click to collapse
After the format data, reconnect the device and you will be able to see the internal storage with only the TWRP directory. (at the step 14. for this topic)
Copy/paste or drag/drop the G95xF_Stock_Kernel_CRGH_v2.zip at the root and you will be able to flash it.
Another way should be to connect an USB key thru the usb connector delivered with your S8.
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.