Related
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
Hello guys, I open a Question and Answer Thread for all SuperMan Rom users, so even users under 10 posts can ask their questions here.
Below I added some basic Q&A stuff which can also be found at the main thread, if you have any question, read through them before posting, thanks!
In case you search for the changelog have a look: Changelog post
If you want to see my post with all useful links such as TWRP, magisk, xposed and more visit: useful post
Basic Questions:
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: My Phone is stuck at boot and doesn't start, what to do??
A: Update your bootloader and modem. Also make sure you have made a fresh install of the rom. Bootloader and Modem can be found in the OP. Another problem can be that you are didn't decrypt your phone. To fix this read below how to disable encryption.
Q: Do I need to update bootloader and modem after every update?
A: It's recommend to update your bootloader and modem everytime there is a new base yes. The developer will tell you if necessary on every rom changelog.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get verification FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G935F/FD/K/L/S/W8. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 820 variants?
A: No, sadly not.
Q: I want to change something in my rom setup, how can I do that?
A: Simply reflash the same rom version without any wipe and than choose the correct things you want.
Q: Some features are not present in this rom, but they are on stock rom, so where are they?
A: In aroma installer you have the option to select bloat you want to install or not, you probably didn't select all package, this is why it's missing now.
Q: After a clean install my phone is overblated with many custom settings. What to do?
A: Open my romcontrol, grant it root permissions and then my default settings will be applied.
Q: Will you add X or Y feature?
A: You can kindly ask in the thread for that, if I like your suggestion I will think about adding it to the rom.
Q: You said you fixed SD card RW but Titanium Backup can't write to external SD card, why???
A: This is because of googles changes concerning SD card, to fix this open Titanium Backup, Menu, Preferences, Backup Folder Location, Storage provider and than hit DocumentProvider Storage and select your SD card. Problem solved
Q: I can't find X and Y mod. Please help
A: I've added many links and useful stuff to this post here. Hope that's what you have been looking for!
Q: I want to have my external storage like an internal as well. Google introduced it with android Marshmallow, but I can't see this option?
A: Just follow this Guide here and you can setup your SD card as normal storage
Q: I got a new strange icon appearing after nougat update. What's that?
A: This is a new advanced calling feature introduced in android nougat. Should make your call quality better or something like this. To hide it please visit following forum: Get rid of RCS icon
Questions concerning rom updates:
Q: Do I have to do a full wipe for the new version?
A: It is always the best option to make a clean install, otherwise please don't come and report bugs!
Q: But I don't want to make a full wipe when only small stuff changed!
A: For updates using the same bases you can install the rom with a dirty flash. BUT with a new base a clean install is highly recommend!
Q: What steps should I do to update to a new version with a full wipe but keep all data?
A: There are some different ways. One way is to make a backup with Titanium Backup, you can backup all Apps and Preferences there. Make sure to store this backup on external SD card (if you have one). Second way would be to save your data onto a google account or samsung cloud and restore it after a clean install.
Q: I miss an apk after rom update, how can I get it back?
A: Simply reflash rom and select "dirty flash" in aroma + select the app this time in aroma.
Q: My battery life is so bad and performance is very poor after an update!?!?
A: This comes actually not form the rom itself, dirty flash can cause problems even if only some small things have been changed. So simply install it clean again and it will solve your problem.
Q: Performance and battery is very poor even after clean install. What should I do now?
A: I assume you installed Xposed than, some modules can cause batterydrain and performance problems. So try to make a clean install of the rom WITHOUT xposed installed.
Questions about log and logcats:
Q: I got FC's and other Problems with the rom, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grabed with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening. Same can be done if you have a terminal installed on your phone. Simply type adb logcat > log.txt and you will have the same output as on the PC.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
You can also send me a log created by your phones terminal with the exact same commands!
Questions about RomControl:
Q: None of my romcontrol changes do anything, why are you such a bad dev!?!?
A: The problem is not on my end, you installed stock systemUI (which is STOCK and does not support one single mod). Use another one in aroma instead. The same thing can happen with good lock!
Q: Romcontrol gives FC's to me. HELP!
A: Very simple answer here: wipe data and cache from superman control application. Also make sure storage permissions are given to the romcontrol.
Q: Romcontrol still FC after cleaning data and cache!
A: Make sure you allow storage permission in main settings.
Q: I try to backup my current RomControl setup, but it won't work?
A: It works. Just make sure to enable storage permission in main samsung applicatoin settings. You will find it in internal sdcard under RomControl folder.
Q: I can't restore SuperMan control settings after a clean base update, why?
A: Backup for SuperMan control only works as long as you use the same version of the app, I mostly change very much things in new releases that's why it won't work there.
Q: SystemUI reboot doesn't work in SuperMan settings app, why?
A: Since Nougat update, you need to install busybox in order to get this button working. Without busybox the button will just do nothing.
Q: I enabled weather on lockscreen but I can't see anything...
A: You probably didn't setup or even installed samsungs weather widget. Without it weather on lockscreen won't work too. So reflash the rom with the widget installed this time and set it up.
How to go back to stock:
Q: I like to go back to stock rom, how is this possible?
A: I can provide you here all steps which are needed to go back to a full stock rom.
0. Make a backup and than wipe all partitions in TWRP
1. Go to Sammobile and choose your country
2. Download the file and the attached Odin on sammobile
3. After downloading, put your phone into download mode
4. Make sure drivers are installed and your pc can detect your phone in odin
5. If the box in odin turns blue, add the AP file to AP tab, BL file to BL tab, CP file to CP tab and CSC_HOME to CSC tab
6. Hit start and wait until it is finished.
7. Reboot and you have a stock rom again
Questions about Encryption:
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the steps below to get rid of your encryption.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 of my rom instructions it tells you to be sure you're not. So, what do you need to to in case you are still encrypted.
A: HOW TO DISABLE ENCRYPTION:
1. Boot into TWRP
2. Select Wipe
3. Select format data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: And if I want to use this rom with encryption?
A: Normally we can use the stock kernel to encrypt our device, but since the Android 7.0 Nougat update samsung makes a check kernel sides to block deodexed roms from booting. This means that even the stock kernel is build by me to disable knox and tima. So encryption won't work there and you have to encrypt your device after you set up your phone. After that go to settings, security, encrypt device. It may need some additional steps to work...
Questions about CSC/Signal:
Q: Where has the CSC selection gone?
A: To include all csc files, the rom get way to big, so it got it's own thread now, take a look here: CSC installer
Q: I have a weak cellular signal, what can I do against it?
A: Two things: first, install your providers CSC using CSC installer and flash in TWRP or flashing stock CSC with Odin. Second Thing: You can install the modem from your provider, also find your modem on Sammobile and install it with Odin in CP tab.
Q: I don't have all sHealth features, how come?
A: Not all CSCs include this feature. I recommend to use AUT or DBT as it has the best compatibility!
Q: Can I flash MM CSC on N and vis a verse?
A: No, this is clearly not recommend! You can and will face call fc's!
Questions about Xposed:
Q: Does Xposed work yet on Android N 7.0?
A: No it does not! You will end up in a bootloop when you flash it on android N
Q: I selected xposed but now I don't see an app for it?
A: Maybe there went something wrong with installing the app to /data/app from my installer script. But xposed is actually installed only the app is missing, so head over to the download page of xposed app: Material Xposed Thread
Q: I selected xposed but the app shows not active or something else with xposed is not working.
A: This can have 2 reasons:
1. You have installed latest xposed version without installing magisk, magisk is required for most recent xposed version!
2. You used 86.2 xposed (which does not need magisk) but you did not install supersu. Since 86.2 does not use magisk to be systemless it uses supersu instead!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent 2.4.3 SuperStock Kernel
3. Flash Magisk V12
4. install latest Magisk Manager from playstore
5. Open Magiks Manager, go to settings
6. Enable MagiskHide, systemless hosts and systemless busybox
7. Reboot the phone and check safetynet!
Q: I got out of date binary issue?
A: Since Magisk V11.1 there is no need for phh root anymore. Everything is handled inside the MagiskManager apk!
Q: Where can I configure the root settings in Magisk?
A: Since Magisk V11.1 Magisk uses MagiskSU, you can find it in latest Magisk Manager V4.1
Questions about Snapchat:
Q: Even when I did not use xposed during my setup in rom I can't login to snapchat anymore!
A: Snapchat got updated and now detects even root access on your phone!
Q: What to do to login to snapchat then?
A: Clean install the rom without root and xposed and login to your snapchat, save the app with titanium backup, flash back xposed and root. For the next update of the rom just restore snapchat backup in TB.
Q: Any other possibility?
A: You could enable MagiskHide and check Snapchat inside it so root will be hidden from Snapchat. You will be able to perfectly login without any issues.
Q: I want to discuss this problem a bit deeper. Should I do so?
A: Do that, but this has nothing to do with this rom, so please go ahead and post your experience here on this Snapchat Thread.
Questions about Kernels:
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash Magisk and supersu (or any other zip that changes some stuff in ramdisk partition) after every change of kernel!
Q: Synapse shows no UCI support!
A: Most comon issue is that no busybox is installed. Download the one from here: Latest busybox and flash it in recovery.
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
Questions about Root:
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel, simply reflash your preferred root method and it will work again!
Q: I selected phh root but my phone tells me I am not rooted!!
A: There are two possibilities:
1. You have mixed supersu/phh with magisk.
2. You did not install phhs root app from playstore.
Q: I get a warning about binary out of date. Help!
A: That happens on latest Magisk V11.1. Reason: Root has fully moved into Magisk Manager, no additional app required. Uninstall phh or supersu apps and only use magisk!
Q: I want to use su hide on my phone, how to do so?
A: Both below variants are outdated, I recommend to use Magisk with its build in MagiskHide. Check the thread: Magisk Thread
Link to phh's hidesu: Phh's thread
Link to chainfires suhide: Chainfires thread
volte support
please help volte is not there i need that to make calls and sms
beinggamer97 said:
please help volte is not there i need that to make calls and sms
Click to expand...
Click to collapse
Flash your providers csc
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
Flash your providers csc
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Thanks man after flashing that csc my volte is working
TouchWiz page effect
I've flashed Superkernel and selected moddedUI mod in Aroma installer. No matter which TouchWiz page effect I select within the Superman Control v2.0 app, the page effect just sticks to default effect.
Am I the only one with this issue?
Grafdude said:
I've flashed Superkernel and selected moddedUI mod in Aroma installer. No matter which TouchWiz page effect I select within the Superman Control v2.0 app, the page effect just sticks to default effect.
Am I the only one with this issue?
Click to expand...
Click to collapse
You have to reboot everytime you change a settings. Plus modded services plus modded launcher are needed
Tkkg1994 said:
You have to reboot everytime you change a settings. Plus modded services plus modded launcher are needed
Click to expand...
Click to collapse
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
---------- Post added at 12:56 PM ---------- Previous post was at 12:33 PM ----------
Grafdude said:
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
Click to expand...
Click to collapse
Disregard what I said, its working now for some reason...lol.
I had another thing to point out regarding the appearance of the corners of rounded UI, I think there might be a problem with the actual image transparency? I've attached image to point out. Click link below
https://drive.google.com/open?id=0B6CqBfmqPw5ebVhDbzgyamtmUU0
Grafdude said:
Thank you Tkkg1994 for your quick reply, by the way your rom is awesome and I'd like to thank you for developing it! So yeah ive selected modded launcher plus services in Aroma, even after a reboot the page effect remains the same.
---------- Post added at 12:56 PM ---------- Previous post was at 12:33 PM ----------
Disregard what I said, its working now for some reason...lol.
I had another thing to point out regarding the appearance of the corners of rounded UI, I think there might be a problem with the actual image transparency? I've attached image to point out. Click link below
https://drive.google.com/open?id=0B6CqBfmqPw5ebVhDbzgyamtmUU0
Click to expand...
Click to collapse
Good it works for you now
I don't see any issue on this (about the rounded ones)
Ok here's a couple of closeup images, to make it clearer.
https://drive.google.com/open?id=0B6CqBfmqPw5eT1NsVl9zaS1qZlk
https://drive.google.com/open?id=0B6CqBfmqPw5eSXRJRC02ZGUzajg
---------- Post added at 01:19 PM ---------- Previous post was at 01:03 PM ----------
Also, Tkkg1994, is there a way to restore the stock Data icon in the status bar? (LTE instead of the 4G)
Grafdude said:
Ok here's a couple of closeup images, to make it clearer.
https://drive.google.com/open?id=0B6CqBfmqPw5eT1NsVl9zaS1qZlk
https://drive.google.com/open?id=0B6CqBfmqPw5eSXRJRC02ZGUzajg
---------- Post added at 01:19 PM ---------- Previous post was at 01:03 PM ----------
Also, Tkkg1994, is there a way to restore the stock Data icon in the status bar? (LTE instead of the 4G)
Click to expand...
Click to collapse
See what you mean now thanks. Can't make it more "slighter" then I already did sorry
About the 4G this is csc related
Sent from my SuperMan powered SM-G930F
Tkkg1994 said:
See what you mean now thanks. Can't make it more "slighter" then I already did sorry
About the 4G this is csc related
Click to expand...
Click to collapse
Allright much thanks for your help, really appreciate it!
How to apply themes?
Hi there, first off thanks for the time spent developing the ROM and helping us out!
When I try to go to the theme section of the stock settings the app fc (stays for forced close right? Sorry, not being an expert here).
I'm quite a dark theme fanatic and I'd really like to get one for my S7 Edge.
Is there maybe something that I don't know?
Thanks
---------- Post added at 02:23 PM ---------- Previous post was at 01:55 PM ----------
il.pella said:
Hi there, first off thanks for the time spent developing the ROM and helping us out!
When I try to go to the theme section of the stock settings the app fc (stays for forced close right? Sorry, not being an expert here).
I'm quite a dark theme fanatic and I'd really like to get one for my S7 Edge.
Is there maybe something that I don't know?
Thanks
Click to expand...
Click to collapse
OK I found the issue (thanks to Tkkg1994 for having it answered to another user), I just debloated theme store when installing the ROM!
Cannot install Stock Kernel
Whenever i try to install Stock Kernel on 1.14 i got bootloop i tried many ways , without modded services, even full stock everything and nothing is working, superstock kernel works fine but just wondering why stock kernel on G935F is not
arbreton said:
Whenever i try to install Stock Kernel on 1.14 i got bootloop i tried many ways , without modded services, even full stock everything and nothing is working, superstock kernel works fine but just wondering why stock kernel on G935F is not
Click to expand...
Click to collapse
You can install it BUT without: Magisk, xposed and phh. This things only work on superstock/superkernel!!
Tkkg1994 said:
You can install it BUT without: Magisk, xposed and phh. This things only work on superstock/superkernel!!
Click to expand...
Click to collapse
I keep getting a bootloop , did a full wipe of everything and tried without super su or magisk or xposed but the stock kernel still not working, other kernels work flawlessly
SM-G935F
deleted
arbreton said:
I keep getting a bootloop , did a full wipe of everything and tried without super su or magisk or xposed but the stock kernel still not working, other kernels work flawlessly
SM-G935F
Click to expand...
Click to collapse
I tested before with stock and all works as it should. You use any root method?
Sent from my SuperMan powered SM-G930F
Hi there, I was testing the user section of the ROM, and anytime I switch to a different user (guest or newly created), I got a persistent "unfortunately IMS service has stopped working" every couple of seconds or less. Couldn't get a solution browsing forums, it seems that must be an app conflicting with the system, but I'm not that tech savvy to know for sure...
Thanks in advance if you know what's going on!
I've flashed v1.14.5 and the "briefing" panel on the homescreen has been replaced by "6thgear TWSwipe"? Is there a setting to have the briefing panel instead?
il.pella said:
Hi there, I was testing the user section of the ROM, and anytime I switch to a different user (guest or newly created), I got a persistent "unfortunately IMS service has stopped working" every couple of seconds or less. Couldn't get a solution browsing forums, it seems that must be an app conflicting with the system, but I'm not that tech savvy to know for sure...
Thanks in advance if you know what's going on!
Click to expand...
Click to collapse
Hello
Can you please attach some logcats for your problem. Thank you
Grafdude said:
I've flashed v1.14.5 and the "briefing" panel on the homescreen has been replaced by "6thgear TWSwipe"? Is there a setting to have the briefing panel instead?
Click to expand...
Click to collapse
Yes by using stock launcher
Sent from my SuperMan powered SM-G930F
Edited Dec 22 -2017 <-- I may not always change this, but this is a work in progress!
[GUIDE][OSPREY] Moto G3 2015 - BEGIN: How to Unlock bootloader, flash TWRP, flash ROM, flash Root, Flash boot logo.
I started this because while trying to explain it to a user I kept running in to old info.
Code:
/*
* Your warranty is now void.
*
* This may destroy your phone. As with any modification to a phone,
* you must be prepared/willing to THROW IT AWAY without thinking twice.
* If you need it or it is your daily driver, don't mess with it.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the suggestions in this guide
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This may well work on Merlin but I don't have one to test.
--> NOTE: I no longer use LineageOS so can't help there. Using AOSP 8. Should be no difference.
1a) Prep - before you do anything, in stock, go to settings/Development Options (which is turned on by tapping /settings/about phone/Build Number about 10 times.)
turn "OEM unlocking" ON
turn Debugging - "USB debugging" ON.
1b) Now! - To do anything, you must unlock your bootloader: This is done by going to the Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
They want you to "Install the Android SDK.". You only need adb and fastboot on your PC (windows or Linux).
Try this guide to get ADB and FASTBOOT onto your computer: https://forum.xda-developers.com/showthread.php?t=2588979
For Ubuntu Linux simply type fastboot on the terminal and if it's missing a command will pop up as to how to add it - simple. same with adb.
ADDITIONAL THOUGHTS: a very helpful user suggested the following additional for unlock bootloader and getting adb and fastboot: @Dave here - see post 34ff.
Dave here said:
Glad it was helpful! Happy to be able to give something back. Here are some links I used...
LineageOS Osprey install guide:
wiki.lineageos.org/devices/osprey/install
LineageOS Using ADB and fastboot guide:
wiki.lineageos.org/adb_fastboot_guide.html
adb & fastboot: I used this link, which was in the LineageOS ADB guide and I think also the Motorola bootloader unlocking instructions:
Mac: dl.google.com/android/repository/platform-tools-latest-darwin.zip
Windows: dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: dl.google.com/android/repository/platform-tools-latest-linux.zip
Lenovo forum: "THERE IS AN ERROR WITH YOUR REQUEST! MOTO G ROOTING PROBLEM!" (it's actually about bootloader unlocking, not rooting):
forums.lenovo.com/t5/MOTO-G-MOTO-G-...EST-MOTO-G-ROOTING-PROBLEM/m-p/3458979#M27009
European Motorola unlocking URLs:
motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
motorola-global-portal-de.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that in step 4.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
-> Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode on your Osprey, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest.
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP. If you get the dead android it means you still have the stock recovery - boot to fastboot and flash TWRP again.
IMMEDIATELY tap Backup and select to put backup on external storage - your SDcard. NOTE - if your SDcard has been converted to "internal storage" you will have to choose "internal storage" (em0). I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
-- > For TWRP BACKUP I use the default settings of "system,data, and boot". Here is a nice article that explains the differences: https://twrp.me/faq/whattobackup.html .
At this point I recommend you boot back into stock and connect your phone to your PC via USB (slide down) and copy that backup in the TWRP folder to your PC. at least once, maybe twice, for safe keeping. You will need this if you wish to test if a problem exists only on a custom ROM but not on the stock ROM. You will also need this if you simply choose to run stock, instead of a custom ROM. Remember, you are now testing ROMs - nothing is certain!
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
Be aware there are some sites out there with logos that don't work on Moto G3.
5. To flash a custom ROM: Download to PC and put it on your SD card. Do same for gapps. (gapps - g-apps - google apps allow you to log in to your google account, use play store, etc. example http://opengapps.org/ (use arm, 7.1, whatever size you wish)(if you're new use full, mini, or micro until you know what you need. If you're on a 1GB phone, consider nano or pico.) )
https://download.lineageos.org/osprey or whatever ROM you want.
http://opengapps.org/ or whatever gapps you want.
Boot to TWRP.
Clean flash:
tap WIPE,
tap advanced, carefully checkmark:
Dalvic/ARTCache,
System,
Data,
Cache,
and then swipe the bottom swipe button. Takes a few sec. This is what makes a "clean flash".
Generally: Don't wipe "internal storage" or SDcard as this is where TWRP stores its backups/nandroids. - I always copy my TWRP backups to PC for safety.
Then back to menu screen and tap Install, select the rom, and swipe and let it do its thing.
Then back and tap Install, select the gapps and swipe to flash it.
THEN, and only then: tap Reboot (if you're at the main menu you also have to tap System to boot from system.)
The install takes 3 min or so before it starts asking questions.
Be sure to choose "Set up as New" or else you get whatever junk is in your google drive. This has cost errors and much time. <-----
6. Root: If you want to use bank apps, PokemonGo, etc, follow these instructions for Magisk:
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
read the whole thread.
- Else go to https://download.chainfire.eu/1019
and download the zip form of Chainfire's SuperSU 2.79 and boot to TWRP and flash (install) it.
Many thanks to @acejavelin for inspiration and information(which I probably shamelessly stole from him), to @squid2 for his installation guide and his version of TWRP, to @Chainfire for the tons of work that continue to go into superSU, to @coolguy_16 for the safetynet/CTS work, and all the many Devs and helpers who make these ROMs possible, and as clean as they are! And to users like you who find bugs and file bug reports! Thank you!
Remember you are working with a Development ROM - a work in progress! (Even stock isn't perfect!!!)
Enjoy!
KrisM22 said:
I started this because while trying to explain it to a user I kept running in to old info.
As with any modification to a phone, you must be prepared/willing to throw it away without thinking twice. If you need it or it is your daily driver. don't mess with it. It is YOUR responsibility alone. If you break your phone, I will laugh.
1) To do anything, you must unlock your bootloader: This is done by going to a Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that later.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
a) you need to have fastboot support on your PC
Try this guide: https://forum.xda-developers.com/showthread.php?t=2588979
You do not need to put the whole SDK on as s9ome guides would have you do.
Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest - twrp-osprey-3.1.0-r1.img
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP.
IMMEDIATELY tap Backup and select to put backup in internal (em0) storage. I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
5. To flash a custom ROM: Put it on your SD card. Boot to TWRP.
Clean flash: tap WIPE, tap advanced, carefully select Dalvic, Data, System, Cache, and then swip the bottom swipe thing. Takes a few sec. This is what makess a "clean flash".
Then back to menu screen and install, select the rom, and swipe and let it do its thing.
Then back and select gapps and flash it.
Then do supersu and flash that (optional)
Then "reboot".
6. Root:
Click to expand...
Click to collapse
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
save1
save2
Subins Mani(Tintumonn) said:
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks - hopefully it will help.
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
KrisM22 said:
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
Click to expand...
Click to collapse
Yes you are correct, gapps won't get removed for new builds of the same ROM due to a persistent ROM script. However flashing a ROM different than the one currently installed usually ignores such scripts and does a clean wipe. Doing a manual wipe just to be sure is fine, even needed sometimes.
I just wanted to point out that not performing a factory reset (twrp>wipe>swipe to factory reset) can leave potential conflicting files in aforementioned places which can cause unexpected behaviours ranging from FCs to bootloop. The potential issues are rare but I think you know how much trouble it can bring to folks trying to capture real bugs (thanks for hard work at Linage ); it was all about removing the potential factors .
Broadcasted from Zeta Reticuli
The TWRP wipe-swipe does Data, Cache, and Dalvic. That's what I used to do. After messing up some tests this past week and wasting a lot of time, I now recommend adding system to that:
In advanced, checking data, cache, and dalvic/ARTcache, and, now, system. as far as i can see, I am leaving nothing other than internal storage and sd card (and of course whatever is in OTG if there's one attached). TBPro puts its backups on "internal storage". By the way I do appreciate your taking the time to look so closely at this!
KrisM22 said:
[GUIDE]
6. Root: Go to http://www.theandroidsoul.com/supersu-2-79-zip-apk-download/
and download the zip form of Chainfire's SuperSU 2.79 . Use it in step5 above.
NOTES: this has nothing to do with rooting your stock ROM which afaik can't be done.
Click to expand...
Click to collapse
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
Edit: Not necessary anymore, just flash SuperSU zip and you're done
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
xMotoDA said:
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
Click to expand...
Click to collapse
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not since SuperSU 2.79 - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
KrisM22 said:
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not after SuperSU 2.78 (or 2.70 or something) - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
Click to expand...
Click to collapse
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
acejavelin said:
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
Click to expand...
Click to collapse
Huge thanks for that!!! Changed above post.
Never played with Magisk - others (you!) are the authority on that. I think some were saying that was a way to get a custom rom to pass safteynet... Thanks!
Huge thanks for looking in!!!
edited/updated 5-4-17
Problem!
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
GermanRodriguez said:
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
Click to expand...
Click to collapse
This is possibly a problem with that rom - ask at that thread.
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
or
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845
edited...
edited
update
changed.
A bit about this post.
I just want to share the links that was useful to me when I was working on my girlfriends phone. Its an awesome device.
I gathered the links and added some troubleshooting tips that helped me out. I hope it does help you too. Enjoy.
UPDATE 09/21/2017
For firmware, stock images and download needs .
Visit https://desktop.firmware.mobi
It was made by our lord Chainfire.
Stock ROMS for SM-G930W8
Updato Rom Download Collections
Stock Recoveries for Galaxy S7 G930W8 Rogers
Marshmallow 6.0 G930W8VLU2BQB6
Download
Nougat 7.0 G930W8VLU2BQH1
Download
How to extract Recovery from Firmwares
How To Extract Stock Recovery From Samsung Firmware
How to Root Galaxy S7 with Magisk
Click Here for MaxLee Guide or Watch Video Below
Download Root, TWRP, Magisk Kit
Video Link
Troubleshooting on Installing Magisk inside TWRP
Problem: When you can't find the zip files on the internal, external sd or otg.
Symtoms
sd card / otg / internalsd showing as 0 mb or mount error.
you can see folders but not files.
How to fix it
Follow the steps below. WARNING: Wiping DATA will delete your files on your internal storage (emulated sd)
Requirements: Copy Magiskv14 , MagiskManager ,AntirootRemoval inside External SDCARD. Insert in the phone.
Boot to TWRP Recovery (VOLUP+HOME+POWER)
Go to Wipe > Format Data
Press back key, then choose reboot > Recovery
Inside recovery, install the necessary zip files.
How to Restore the Mobile Data and Mobile Hotspot Quick Settings Toggles on Samsung Galaxy Devices
Click here for the full steps
How to Restore to Stock Firmware
Video Link
Tweaks for Battery Life
Disable Wifi Scanning - Settings>Privacy and Safety>Location>Improve Accuracy
https://www.androidcentral.com/fix-battery-life-galaxy-s7
Fix Wifi Lag on S7
Automatic
Set DNS as google using DNS Changer
Manual
Enable Developer mode on your S7 or S7 Edge.
In the new "Developer options" in "Settings" change "Use legacy DHCP client" from OFF to ON.
Anothery Way
Change DNS settings
If the above tips did not work for you, its time to take things to the next level. If the Galaxy S7 is the only device in your Wi-Fi network to suffer from slow speeds, you can try changing the DNS server used on the handset.
For this, you will first have to make the device forget the existing Wi-Fi network. Then, tap on its name to join again, but before you enter the password, tap on ‘Show advanced options.’ Now proceed to tap ‘IP Settings’ and select ‘Static’ from the list. Leave other IP settings as they are, and simply enter the DNS server you’d like to use in the DNS text field area. You can try using Google DNS first (8.8.8.8, 8.8.4.4) or OpenDNS (208.67.222.222) to see if they fix the Wi-Fi woes on your S7 or not.
Important Tools
ADB Installer
Latest Odin
Samsung USB Drivers
Wireless ADB Root - Download
Magisk Thread
Fix Odin Device Info Fail when Restoring (Credits to Original Poster)
Method 1
Open Odin, place all the necessary files into their slots.
Go the the options tab, make sure "Auto Reboot" IS ticked.
Press "start", but as soon as you do, hold down VolumeDown+Home+Power on your phone.
Odin will fail and your phone will reboot into download mode again.
Now press "Start" in Odin again, and your phone should flash without a problem.
This might take a few attempts to get right.
Method 2 (Another Variation)
Download the stock for your phone.
Boot into download mode by pressing ( power + volume down + home button) and stop at the screen of continue and reboot.
Press volume down to restart phone
Quickly boot back into download mode by pressing (power + volume down + home button)
Press continue
Install firmware with Odin
Wait for the firmware to be installed
Ready.
How I Rooted my G930W8
Don't skip any of the step.
First clean install the latest Nougat 7.0 G930W8VLU2BQH1 - Guide
Download the MagiskFilesRoot, unzip it in the sdcard, slide it inside your phone
Boot up S7 then setup the normal way
Enable Developer Options - System > About Phone > Build Number > Tap 7 Times, press back.
Select Developer Options then Turn on ADB Debugging & OEM Unlock
Disable the Samsung Factory Reset Protection if you have it enabled
Put phone in download mode
Download TWRP using this twrp-3.1.1-0-herolte.img.tar
Open Odin, uncheck AutoReboot, check AP point to the TWRP we just downloaded. Hit Start
Once its finished, do Recovery Combo (Power + VolumeUp + HomeButton)
It will reboot in TWRP Recovery, flash MagiskV14.zip, if you have problem seeing files wipe DATA and then reboot to recovery again using TWRP, select SDCARD as storage then flash MagiskV14.zip
Reboot the phone, wait 10-15 minutes then install MagiskManager.apk
Optional - Open Magisk Manager, select SuperUser then open Download. Install Busybox by 0sm0sis.
You are now running systemless root
Refer to MaxLee Video on Rooting S7 with Magisk - Guide
Did you manage to root the G930W8 on nougat 7.0 build with this method? I've had nothing but problems attempting to root for the last few days. Tried cf-auto root and this magisk method early on in my attempts with no success. I've just fine a full clean build flash and restore and would really like to root but am worried I'm just going to get no where again and spend hours getting back to where I'm at now...
v2kai said:
Did you manage to root the G930W8 on nougat 7.0 build with this method? I've had nothing but problems attempting to root for the last few days. Tried cf-auto root and this magisk method early on in my attempts with no success. I've just fine a full clean build flash and restore and would really like to root but am worried I'm just going to get no where again and spend hours getting back to where I'm at now...
Click to expand...
Click to collapse
Yes. Refer to second post. I'm now running the latest nougat with magiskv14 systemless root. Its better that way, I can still use snapchat and banking applications.
What was the problem you are having?
Xygote said:
Yes. Refer to second post. I'm now running the latest nougat with magiskv14 systemless root. Its better that way, I can still use snapchat and banking applications.
What was the problem you are having?
Click to expand...
Click to collapse
Having trouble as well.
I get message "integrity check failed" after flashing magisk via twrp a step 11 then makes me reset the phone but because of the custom recovery it only bootloops.
Then i restart the whole process again only to stop at step 11.
Is there a step i'm missing?
Start all over again, but on step 11 follow this.
Try it this way:
When you boot up to TWRP, swipe allow modification. Flash MagiskV14.zip, then if it says install TWRP app, press "do not install".
If you have problem seeing files wipe DATA and then reboot to recovery again using TWRP, select SDCARD as storage then flash MagiskV14.zip
I tried it but i accidentally let the phone reboot after flashing twrp and it failed the integrity check and started bootlooping. I entered recovery and grabbed the log which i attached here.
So I did the steps again but used this steps from the other guide for exynos models
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to use Systemless DevBase, then do not swipe. Keep it as read only.
Go to Wipe and click on format data. Type "yes" and it will format.
Now go back to home and click on "Reboot" then click on "Recovery" Option.
Then went from step 11 here and what you said to flash magisk and it worked.
My phone is finally debloated.
I tried your steps many times but everytime it's failing. Everytime it fails when installing "system". I've tried with different CSC version firmwares but it failed with each one of them. I', 100% sure that it is G930W8 S7 Flat because it was running on the same version of custom ROMs.
cy56 said:
I tried your steps many times but everytime it's failing. Everytime it fails when installing "system". I've tried with different CSC version firmwares but it failed with each one of them. I', 100% sure that it is G930W8 S7 Flat because it was running on the same version of custom ROMs.
Click to expand...
Click to collapse
Same here... I tried it on two different stock roms with no luck.
I almost soft bricked my s7 which was working perfectly before applying the patch. It was giving me dm-verity error at boot...
I was able to flash it back and make it working using full stock rom.
I highly recommend readers to NOT apply the above Magisk Root on their G930W8 (S7).
DeCoDish
sorry if this is in the wrong section i have galaxy s7 its on android 7.0 my power button is broken doesnt work at all i normally dont let my phone power down completley cause of it and it has ive tried rebooting the phone usin volume down and then plugging into computer and it just brings up the charge screen is there any other ways i can get this phone powered on even if i have to download something on my computer i will pleaqse help if possible
Have you tried these suggestions?
https://www.addictivetips.com/android/turn-on-an-android-phone-with-a-broken-power-button/
I just want to confirm this, since it's not explicitly mentioned in the post... When you root it trips KNOX, which locks you out from Disconnect Pro, Samsung Health, and Samsung Pay. Does this also mean that Android pay will not work either? Or does this method allow for Android pay to work?
If not, is there a workaround yet?
Scraggarax said:
I just want to confirm this, since it's not explicitly mentioned in the post... When you root it trips KNOX, which locks you out from Disconnect Pro, Samsung Health, and Samsung Pay. Does this also mean that Android pay will not work either? Or does this method allow for Android pay to work?
If not, is there a workaround yet?
Click to expand...
Click to collapse
There are many reports on the XDA forums that Android Pay works with Magisk systemless root and with tripped Knox on S7 (as opposed to Samsung Pay which will not work once Knox is tripped).
Xygote said:
A bit about this post.
I just want to share the links that was useful to me when I was working on my girlfriends phone. Its an awesome device.
I gathered the links and added some troubleshooting tips that helped me out. I hope it does help you too. Enjoy.
UPDATE 09/21/2017
For firmware, stock images and download needs .
Visit https://desktop.firmware.mobi
It was made by our lord Chainfire.
Stock ROMS for SM-G930W8
Updato Rom Download Collections
Stock Recoveries for Galaxy S7 G930W8 Rogers
Marshmallow 6.0 G930W8VLU2BQB6
Download
Nougat 7.0 G930W8VLU2BQH1
Download
How to extract Recovery from Firmwares
How To Extract Stock Recovery From Samsung Firmware
How to Root Galaxy S7 with Magisk
Click Here for MaxLee Guide or Watch Video Below
Download Root, TWRP, Magisk Kit
Video Link
Troubleshooting on Installing Magisk inside TWRP
Problem: When you can't find the zip files on the internal, external sd or otg.
Symtoms
sd card / otg / internalsd showing as 0 mb or mount error.
you can see folders but not files.
How to fix it
Follow the steps below. WARNING: Wiping DATA will delete your files on your internal storage (emulated sd)
Requirements: Copy Magiskv14 , MagiskManager ,AntirootRemoval inside External SDCARD. Insert in the phone.
Boot to TWRP Recovery (VOLUP+HOME+POWER)
Go to Wipe > Format Data
Press back key, then choose reboot > Recovery
Inside recovery, install the necessary zip files.
How to Restore the Mobile Data and Mobile Hotspot Quick Settings Toggles on Samsung Galaxy Devices
Click here for the full steps
How to Restore to Stock Firmware
Video Link
Tweaks for Battery Life
Disable Wifi Scanning - Settings>Privacy and Safety>Location>Improve Accuracy
https://www.androidcentral.com/fix-battery-life-galaxy-s7
Fix Wifi Lag on S7
Automatic
Set DNS as google using DNS Changer
Manual
Enable Developer mode on your S7 or S7 Edge.
In the new "Developer options" in "Settings" change "Use legacy DHCP client" from OFF to ON.
Anothery Way
Change DNS settings
If the above tips did not work for you, its time to take things to the next level. If the Galaxy S7 is the only device in your Wi-Fi network to suffer from slow speeds, you can try changing the DNS server used on the handset.
For this, you will first have to make the device forget the existing Wi-Fi network. Then, tap on its name to join again, but before you enter the password, tap on ‘Show advanced options.’ Now proceed to tap ‘IP Settings’ and select ‘Static’ from the list. Leave other IP settings as they are, and simply enter the DNS server you’d like to use in the DNS text field area. You can try using Google DNS first (8.8.8.8, 8.8.4.4) or OpenDNS (208.67.222.222) to see if they fix the Wi-Fi woes on your S7 or not.
Important Tools
ADB Installer
Latest Odin
Samsung USB Drivers
Wireless ADB Root - Download
Magisk Thread
Fix Odin Device Info Fail when Restoring (Credits to Original Poster)
Method 1
Open Odin, place all the necessary files into their slots.
Go the the options tab, make sure "Auto Reboot" IS ticked.
Press "start", but as soon as you do, hold down VolumeDown+Home+Power on your phone.
Odin will fail and your phone will reboot into download mode again.
Now press "Start" in Odin again, and your phone should flash without a problem.
This might take a few attempts to get right.
Method 2 (Another Variation)
Download the stock for your phone.
Boot into download mode by pressing ( power + volume down + home button) and stop at the screen of continue and reboot.
Press volume down to restart phone
Quickly boot back into download mode by pressing (power + volume down + home button)
Press continue
Install firmware with Odin
Wait for the firmware to be installed
Ready.
Click to expand...
Click to collapse
I followed these directions exactly but when I boot into TWRP and attempt to install the Magisk.zip I recieve the following errors stating "could not mount /data partition" then causing the phone to bootloop until I flash the stock firmware again.
Why is this happening?
benberger88 said:
So I did the steps again but used this steps from the other guide for exynos models
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to use Systemless DevBase, then do not swipe. Keep it as read only.
Go to Wipe and click on format data. Type "yes" and it will format.
Now go back to home and click on "Reboot" then click on "Recovery" Option.
Then went from step 11 here and what you said to flash magisk and it worked.
My phone is finally debloated.
Click to expand...
Click to collapse
can you clarify(link to) what combination of steps you used to achieve a successful root? I havent attempted again since my last attempt but it sounds like you had some success. If you'd share it'd be really helpful and appreciated. Would really like to get root back on my phone
also just to clarify, I'm on nougat 7.0 with security patch Nov 1, 2017
Thanks
Avengement said:
I followed these directions exactly but when I boot into TWRP and attempt to install the Magisk.zip I recieve the following errors stating "could not mount /data partition" then causing the phone to bootloop until I flash the stock firmware again.
Why is this happening?
Click to expand...
Click to collapse
If its first time TWRP installation then you need to Format data (Caution: Format data will format the Phone internal storage and you need to backup files first if you have in phone storage like photos video and etc) After formatting data it Will allow to read and write the data partition). Further once you Flash TWRP then Super SU or Magist (Root) is compulsory to boot normal unless its bootloop
Any of you recommend holding off on the root till the Oreo update? Also, does rooting change the kernel to a different one? I wanna avoid battery/performance issues if I can by staying on the stock kernel.
MirzaAwais said:
If its first time TWRP installation then you need to Format data (Caution: Format data will format the Phone internal storage and you need to backup files first if you have in phone storage like photos video and etc) After formatting data it Will allow to read and write the data partition). Further once you Flash TWRP then Super SU or Magist (Root) is compulsory to boot normal unless its bootloop
Click to expand...
Click to collapse
How do you format the drive? What type of file system do you format it to? At what point in this tutorial is this done?
hi
can someone confirm a procedure for rooting s7 on exynos cpu
would be more than appreciated
thanks
nate
DISCLAIMER
I am not responsible for anything that happens to your device on following these steps. These are untested steps that worked for me and might work for you.
PREREQUISITES
1. PC with adb
2. Unlocked Bootloader
3. TWRP
4. MIUI 9 [Might work with other ROMs, not tested]
5. Lazyflasher zip
NOTES
1. If you are on a custom ROM, chances are that camera2 api is already enabled. Use Manual Camera Compatibility to verify.
2. If you are on MIUI, updating using ota might reset build.prop file. This might help, not tested. Update: I successfully updated to MIUI 9 Global 7.10.19 | Beta, see below for steps,
3. I am using Google Camera v4.4.020.163412804 on MIUI 9 Global 7.9.7 | Beta, and it is a HUGE improvement over the stock camera.
STEPS
1. Boot into TWRP. (Guide if you don't have TWRP)
2. Mount System.
3. Take NANDroid backup. (Optional but HIGHLY RECOMMENDED)
4. Connect to PC and execute the following command in terminal:
Code:
[SIZE="3"]adb pull /system/build.prop[/SIZE]
5. This copies build.prop to the current directory. (C:\Users\[USERNAME] by default on windows)
6. Copy it to another directory for backup.
7. Open in editor and add the following line at end:
Code:
[SIZE="3"]persist.camera.HAL3.enabled=1[/SIZE]
8. Save and exit.
9. Execute following commands:
Code:
[SIZE="3"]adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
[/SIZE]
10. Copy lazyflasher to internal storage.
11. Flash using TWRP.
12. Reboot to system.
13. Use Manual Camera Compatibility Checker to verify.
14. PROFIT!
15. Install the latest Google Camera HDR+ Port. (Optional but HIGHLY RECOMMENDED ;P)
UPDATING MIUI
1. Download the official recovery zip from here.
2. Download latest TWRP from here
2. Reboot into TWRP.
3. Take NANDroid. (Optional, just in case . . .)
4. Transfer ROM zip, TWRP img and Lazyflasher zip to internal storage.
5. Flash ROM zip. (Took about 10 minutes)
6. Flash TWRP img. (Go to flash -> select flash image -> select twrp-[v].img)
7. Flash Lazyflasher zip.
8. Follow steps 4 through 9 of above instructions. (Yes, build.prop also gets replaced on update)
9. Reboot to system.
10. Wait patiently.
11. VOILA !!
LINKS
1. Manual Camera Compatibility Checker
2. Lazyflasher Zip
3. Google Camera HDR+ Port
4. Latest MIUI Recovery Image
5. Official TWRP for mido
6. Sources: (1) (2) (3)
Hope this helps. Try and comment if this works for you in other ROMs. Also let me know if anything is unclear.
TWRP Tweaks (MIUI 9 Beta)
The method in this thread basically allows you to edit build.prop without rooting, which opens up a lot of possibilities. Here are some other useful tweaks to build.prop that I use.
(Note: If a line is already present in the file, edit the line otherwise add at end.)
1. Enable MIUI's full screen gestures
Code:
[SIZE="3"]
qemu.hw.mainkeys=0
[/SIZE]
2. Add EIS and disable noise cancellation
Code:
[SIZE="3"]
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
[/SIZE]
3. Turn off noise cancellation for audio recordings
Code:
[SIZE="3"]
persist.audio.fluence.voicerec=false
[/SIZE]
4. Fix Google Assistant talkback
Code:
[SIZE="3"]
mm.enable.qcom_parser=245389
[/SIZE]
Sources: (1)
Do reply if you are using some build.prop tweak and I'll add it here!
is it possible to make the flash-able zip work with stock recovery?
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
joefso said:
is it possible to make the flash-able zip work with stock recovery?
Click to expand...
Click to collapse
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
mato_d007 said:
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
Click to expand...
Click to collapse
The source of the lazyflasher zip (2 in sources) says:
This device uses dm-verity
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
When I was trying the adb method, I was getting a bootloop, because (I think) the system partition had been modified (new build.prop replaced old one). Flashing this zip solved this, so I guess it essentially allows modifications to the system partition.
A_K_S_H_ said:
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
Click to expand...
Click to collapse
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
joefso said:
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
Click to expand...
Click to collapse
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
A_K_S_H_ said:
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
Click to expand...
Click to collapse
I assumed that if OTA updates can be flashed through bootloader then by that logic /system could be modified too, right? hmmm
In Android devices, Recovery is an Android-based, lightweight runtime environment separate from and parallel to the main Android operating system. Recovery's original purpose was:
to apply software updates to the device, e.g. OTA updates, and
to erase user data and cache, e.g. for troubleshooting or preparing the device for resale (factory reset) and
to run (another) external tool from microSD flash memory
https://forum.xda-developers.com/wiki/Recovery
Click to expand...
Click to collapse
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
amit.tiger12 said:
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
Click to expand...
Click to collapse
Read the title : WITHOUT ROOT
A_K_S_H_ said:
Read the title : WITHOUT ROOT
Click to expand...
Click to collapse
yep I found..
do you have any solution for locked bootloader or everything stock??
amit.tiger12 said:
yep I found..
do you have any solution for locked bootloader or everything stock??
Click to expand...
Click to collapse
Unfortunately I don't have access to a stock mido right now, and I don't want to lock my bootloader.
If you're willing to risk it, you could try these steps:
1. Go to developer settings and enable adb.
2. Follow steps 4 to 9 of main post (with device switched on)
3. Reboot.
You might get a bootloop on rebooting, in which case you'd have to get into stock recovery and factory reset, because afaik, stock recovery doesn't give you adb.
Do tell what happens if you try this, good luck!
When I replace the build.prop the phone goes bootloop. It does not matter I use adb or root explorer or something... Why is that? BTW only this method worked: I used an app called build prop editor and worked like a charm! Thank you. If you did not tell that it was possible to enable camera 2 api on miui 9, all my hopes would be lost. So I suggest everyone to use another methods in case this does not work.
Does this work for MIUI 8? I dont want to root my phone but would like camera2
qun said:
Does this work for MIUI 8? I dont want to root my phone but would like camera2
Click to expand...
Click to collapse
It should, provided you have unlocked bootloader, but I haven't tested yet. Take a backup and try! Also, don't forget to reply what happens if you do try.
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Ghavio1516 said:
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
Click to expand...
Click to collapse
These are configs, check and see which one works best for you.
foxhunt said:
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Click to expand...
Click to collapse
No, once should be enough, but flashing twice won't cause any trouble either.