Database Develop

[Q&A] [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/

[Q&A] [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/
Q&A for [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/Jan/15
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 [23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 28/Jan/15. 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!

I know these are novice questions but please bear with me as I just want to understand the process.
I have the Z3C rooted on 5.77 with SuperSU, Xposed and various modules installed plus other ‘normal’ apps.
1. So if I do as in the OP I will have a ‘stock’ Z3C without the apps listed in the OP, meaning I have to install Xposed, modules and all my ‘normal’ apps afterwards? (don’t mind this, just want to be clear)
2. Is SuperSU ok?
3. Can I sync a backup from Sony Companion to get all my personal stuff back?
4. A.If I want to get one of the deleted apps back I just install it from e.g. GooglePlay? or
B. Using RootExplorer can I just delete the App's apk & odex files with same result as flashing?
5. Main reason for wanting to try/use this is I would like to use the Xperia™ Xposed module, so once above is completed I can d/l Xperia™ Xposed , activate it and I’m good to go?
Again, thanks for bearing with me and any advice appreciated.

I softbricked my D5833, what went wrong?
Requirements:
- Z3 Compact (any) or even Z3 (to be confirmed)
- Running rooted 23.0.1.A.5.77 firmware
- Recovery
- System partition mountable as r/w
Install:
1. Enter recovery and backup your current rom (good practice)
2. Download flashable zip
3. Enter recovery and flash it
4. Wipe Cache and Dalvik Cache (and Data - optional)
Click to expand...
Click to collapse
Hi there. I had a well running rooted 23.0.1.A.5.77 firmware. After flashing the "[23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode" my phone wouldn't boot any more. It got stuck on the Sony logo.
I cant understand why. Is it because I have a D5833? Or might it be because after wiping the cache and the Dalvik cache I also ran "Prepare for flashing a new image" (I can't remember the exact phrase right now)
Please tell me what you think went wrong.

richard roe said:
Hi there. I had a well running rooted 23.0.1.A.5.77 firmware. After flashing the "[23.0.1.A.5.77] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode" my phone wouldn't boot any more. It got stuck on the Sony logo.
I cant understand why. Is it because I have a D5833? Or might it be because after wiping the cache and the Dalvik cache I also ran "Prepare for flashing a new image" (I can't remember the exact phrase right now)
Please tell me what you think went wrong.
Click to expand...
Click to collapse
Never mind.

Thanks for this, @serajr. I just had a quick question regarding recovery. I have rooted my device with this guide (all steps completed); when I boot into TWRP and flash this .zip, how do I maintain the Dual Recovery installed in the root guide?
Apologies, I've found that recovery is still maintained on the device after using the .zip but NDRUtils is uninstalled which is easily downloadable again.

apSlain said:
Thanks for this, @serajr. I just had a quick question regarding recovery. I have rooted my device with this guide (all steps completed); when I boot into TWRP and flash this .zip, how do I maintain the Dual Recovery installed in the root guide?
Apologies, I've found that recovery is still maintained on the device after using the .zip but NDRUtils is uninstalled which is easily downloadable again.
Click to expand...
Click to collapse
Thanks buddy!
Keep cool wiping everything AFTER flashing this thread zip file, it will just do changes into folders below:
/system/app (here including latest Superuser.apk)
/system/priv-app
/system/framework
Root binary (/system/xbin/su) and recovery files won't be touched!

serajr said:
Thanks buddy!
Keep cool wiping everything AFTER flashing this thread zip file, it will just do changes into folders below:
/system/app (here including latest Superuser.apk)
/system/priv-app
/system/framework
Root binary (/system/xbin/su) and recovery files won't be touched!
Click to expand...
Click to collapse
Thanks for the prompt response! So, as far as I've understood, despite NDRUtils being uninstalled after flashing, recovery is still maintained and I just need to redownload NDRUtils if I need it via the Play Store.
I just had two quick follow up questions if you have the time to answer them?
1. If I want to go back to complete stock i.e. out-of-the-box functionality with all the bloat reinstalled, recovery deleted, etc., am I right in saying all I need to do is re-flash a stock firmware from this thread with Flashtool?
2. Can I delete your flashable .zip file and the SonyRICDefeat .zip file from /sdcard0 after flashing them in recovery?​Hopefully these are simple questions. Thanks!

apSlain said:
Thanks for the prompt response! So, as far as I've understood, despite NDRUtils being uninstalled after flashing, recovery is still maintained and I just need to redownload NDRUtils if I need it via the Play Store.
I just had two quick follow up questions if you have the time to answer them?
1. If I want to go back to complete stock i.e. out-of-the-box functionality with all the bloat reinstalled, recovery deleted, etc., am I right in saying all I need to do is re-flash a stock firmware from this thread with Flashtool?
2. Can I delete your flashable .zip file and the SonyRICDefeat .zip file from /sdcard0 after flashing them in recovery?​Hopefully these are simple questions. Thanks!
Click to expand...
Click to collapse
1. Yes, you are! By fully flashing ftf file you will be on raw stock fw again!!
2. Yep, you can delete both!

First time at debloating and deleted the apks at /system/etc/customization/applications/. before first uninstalling.
Could some kind soul post the list or instruct how i can work out the list from the zip? tried exploring the system.ext4 file but that didnt help as i thought it would.
Thanks for the debloat.

Serajr, can you release next version of your modification as a fully fledged ROM, please? It would be way easier to use.
I've just bought my Xperia and i'm a bit confused. With my old Samsung Galaxy everything was easy as a dream:
- flash popular ROM
- update it via OTA for years
With Xperia everything is much more complicated. (2 bootloaders, DRM keys, flash counters, etc.)
Sometimes I think that i'm too old for this but I can't imagine to use Android phone without root, xposed framework, firewall, navbar customization...
Regards.

Newb here, so I can't find my zip file when searching for zip with CWM. I did put it on SDcard and it's mounted, heck I put it in all kinds of folders for a look, but CWM is not recognizing it.
What is the system/method you guys have flashed this rom?
What have I missed? What have I not done? Is there another method?
Thanks.
Edit:
got it, thanks

I am hopefully not the only one with this problem on this deodexed rom but I have the problem to not be able to change the lockscreen wallpaper. It only shows the wallpaper of the homescreen at my lockscreen.
Is anyone else experiencing same issue or has a solution for me?
Maybe only a missing systemapp....
Sent from my D5803 using XDA Free mobile app

Kernel Problem
The debloated ROM works fine.
Problem: If I flash a Kernel (of course with unlocked Bootloader ) for instance AndroPlus or XZDR Kernel with your ROM - -> Bootloop.
With original/generic .77 firmware - -> no Bootloop
Do I make a mistake?

[23.1.A.0.690] Debloated, Deodexed, Zipaligned, Rooted, Super User Mode - 04/04/15
Sorry everyone,
Dont know where my post ended up here???
Of course, my mistake
QUOTE
Link for the last KK version
Dear @serajr
could you post a link to your last KK version? I'm waiting for LP xposed to be become stable, and until that I'll stay on KK
I'm on rooted stock (december KK), so I just flash this in recovery and it cleans all the sh*t from an existing ROM? I don't need to start over?
UNQUOTE
Yeah, I second this request (and questions)
Much appreciated.

Finally it's here!!! A big thanks to the developer *___*

Norup58 said:
Sorry everyone,
Dont know where my post ended up here???
Of course, my mistake
QUOTE
Link for the last KK version
Dear @serajr
could you post a link to your last KK version? I'm waiting for LP xposed to be become stable, and until that I'll stay on KK
I'm on rooted stock (december KK), so I just flash this in recovery and it cleans all the sh*t from an existing ROM? I don't need to start over?
UNQUOTE
Yeah, I second this request (and questions)
Much appreciated.
Click to expand...
Click to collapse
Go to original thread and take it under "KitKat version (23.0.1.A.5.77)"

Why deodex? Deodexing impairs performance and gains nothing but the ability to mess with system apk more easily.

Worked perfectly for me.
Got Xposed with GravityBox and more all up and running. No bootloops after multiple reboots as well.

I, too, am in doubt which is the correct/easiest approach for upgrading to Lp 5.0.2 from KK .77 LB.
It appears we can piece together a working solution for a Lp with R/W, Recovery & Xposed Framework:
R/W: e.g. use the one from Meetdaleet, which we apparently can 'dirty' flash directly from .77 to 5.0.2
RECOVERY: http://forum.xda-developers.com/showthread.php?t=2261606&page=384 -Read post 3837 & jump to 3876 where *NUT* says it will be implemented in DualRecovery
Xposed Framework: see *Serajr*'s post 177
As *NUT* is planning on releasing DualRecovery 2.84 next week I think I'll wait and in the meantime hoping Xposed Framework will be updated also.

sry wrong post thx for the share

[Help] Explain systemless Root

Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.

TokedUp said:
Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 and this http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 for starters. BTW Google is your friend and you can`t be rooted to use systemless root and obtain root.

I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...

dahawthorne said:
I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...
Click to expand...
Click to collapse
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K

TokedUp said:
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K
Click to expand...
Click to collapse
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os

holeindalip said:
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os
Click to expand...
Click to collapse
True, but i always enable it by default

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
Thank you so much!

TokedUp said:
Thank you so much!
Click to expand...
Click to collapse
Tip: instead of flashing TWRP you can also boot it up ( fastboot boot nametwrp.img) to flash zip files and keep your stock recovery if you want to.

@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.

Busybox is the space efficient way of the basic Unix commands like ln, pwd, chown, chmod, etc. So all apps that want to do some low level file system dabbling, like Android terminal, Titanium backup, or Linux installs, they need it. https://en.wikipedia.org/wiki/BusyBox
From Marshmallow, Android now uses toybox instead by default, which is quite the same, with a little different licensing. It's also in the AOSP source, so all user built AOSP roms already have toybox, so there's no need for busybox to install.

dahawthorne said:
@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.
Click to expand...
Click to collapse
Apps like Rom Toolbox Pro, Franco Kernel Updater and Kernel Adiutor and lots of other application like Xposed framework (and its modules) and most (if not all) of the custom roms will not work (correctly) without BusyBox. All custom roms anyway have a BusyBox version by default installed Busybox https://en.wikipedia.org/wiki/BusyBox and https://www.google.nl/url?sa=t&rct=...6Z0ltw&usg=AFQjCNG-nKYoEI3kiDm4pgtRWbXFRTpI6A for instance.
Its an essential app for when you are rooted and want to do more with your phone and its not smart to not install it

Thanks, both. I like istperson's comment best : "there's no need for busybox to install." That would be why I haven't seen any negative impact from not having Busybox then. Still, money well spent to help development...

Rooting Brand New Nexus 6 MMB29Q Build

I've been reading forums in XDA and reddit almost the whole day and was not able to find any definite guide about my inquiries so i started this new thread..
Here's my Story, i bought a brand new nexus 6 6.0.1 with build MMB29Q, i wanted to adjust the saturation because its too high, and of course i have to root to do that. i have already unlock boot loader. PS I'm very new in roooting, as in Zero experience, i'm reading about it right now but i need some help from you guys for me to not brick my new phone. 'Im planning on doing Systemless Root BTW.
My questions are:
1. What SuperSu version and TWRP version is compatible with MMB29Q? (i know the newest version is 2.67 for SuperSU and 2.8.5.0 for TWRP) I'm having second thought in using them because MMB29Q came to my device just February. Can someone tell me which version si compatible?
2. [/B] If i would be successful in rooting my device, i plan on flashing custom kernel (I'm Planning on Using Franco Kernel because it is the one the i have read which is compatible in color saturation control and temperature. Any suggestion for other kernel will be very helpful.) My question is after i root my device can i just directly flash it (franco kernel zip file) using TWRP in my device? or are there any requisites before flashing the franco kernel?
Please anyone can give a definitive guide on this, or atleast give me forum threads that i can read about this. Will really appreciate for your help guys, i really love my nexus 6, saturation and warm temp is my only concern. Thank you Guys!!!

2.67 for SuperSU is compatible. 2.8.5.0 TWRP is also compatible.
(Kernel - I don't know)

1. SuperSU 2.65 or 2.67, TWRP 3.0.0. Keep in mind that SuperSU 2.67 is the beta version so you might want to use 2.65 instead. There are alternative superuser binaries available but those require a bit more work to use.
2. No suggestion for an alternate kernel, as I don't use one. As long as a flashable zip file is available for the chosen kernel, you can flash it via TWRP.

I used SuperSU v2.67, TWRP 3.0.0-0 and the ElementalX (3.09) kernel.
Rooted right now on stock MMB29Q.

I'm using SuperSU 2.66 on 29Q without issue. TWRP has been updated to 3.0.0-1 link: https://dl.twrp.me/shamu/
Read the OP for the kernel that you want. In there it will state if any special requirements are needed to flash before and/or after.
You'd want to flash the kernel first then flash SuperSU.

No issues with SuperSU 2.67 and TWRP 3.0.0 ElementalX is a great custom kernel. It supports screen color control (manually or pick in Aroma installer) and has a bunch of other features.
You should check out the N6 all in one beginners guide.
http://forum.xda-developers.com/showthread.php?t=2948481
Sent from my Nexus 6 using Tapatalk

Question has been answered already, but I would say newest SuperSU, version 2.67, and kernel suggestion? I love elite kernel because it supports all ROMs! AOSP and stock! PM me if you have questions, I'll help ya!

Hi I have been reading hi and low also to root MMB29q but only access to a MAC....any advice/ point me in the right direction is much appreciated, thank you

d88naimi said:
Hi I have been reading hi and low also to root MMB29q but only access to a MAC....any advice/ point me in the right direction is much appreciated, thank you
Click to expand...
Click to collapse
On the phone make sure you have USB debugging enabled, and also allow the bootloader to be unlocked.
Get the Android SDK and ADB setup on your MAC. I don't have a MAC and this guide may or may not be correct, I can't confirm. Boot your phone into bootloader mode (hold volume up + volume down + power when the phone is turned off). Connect the phone to your MAC and run the command "fastboot oem unlock" to unlock your bootloader. Then "fastboot flash recovery twrp-3.0.0-1-shamu.img" this will put on TWRP recovery.
Now using your volume rockers to boot into recovery. Now flash the version of SuperSu you want to use- 2.67 for Systemless or 2.65 for System. If you use systemless, TWRP will probably warn you you are not rooted and to swipe to install SuperSu. Don't do this!

Help requested with updating Custom ROM.

Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!

Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.

Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?

Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.

DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,

Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.

DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs

Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,

Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.

Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!

Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.

Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.

Question Install magisk

Hello, noob when it comes to rooted phones here. I'm interested in getting magisk on my phone and would like to ask about the how to.
I see that from v22 the installation process is updated, but is there any downside to doing it the old custom recovery way? That way just seems much easier/faster compared to patching images with adb and fastboot.
* Full disclosure not really sure what "Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process." is compared to without custom recovery before.
I have twrp and am currently on eu stable v12.5.10, downloading v12.5.11 as I write this.
Phone is Mi 11 Pro
Thanks!

Snusious said:
Hello, noob when it comes to rooted phones here. I'm interested in getting magisk on my phone and would like to ask about the how to.
I see that from v22 the installation process is updated, but is there any downside to doing it the old custom recovery way? That way just seems much easier/faster compared to patching images with adb and fastboot.
* Full disclosure not really sure what "Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process." is compared to without custom recovery before.
I have twrp and am currently on eu stable v12.5.10, downloading v12.5.11 as I write this.
Phone is Mi 11 Pro
Thanks!
Click to expand...
Click to collapse
just add .zip to the magisk apk and flash in twrp like you would old magisk

jons99 said:
just add .zip to the magisk apk and flash in twrp like you would old magisk
Click to expand...
Click to collapse
Thanks yeah that's what I wanted. Just asking for possible downsides since the installation guide on github suggests the patch image method.

Snusious said:
Thanks yeah that's what I wanted. Just asking for possible downsides since the installation guide on github suggests the patch image method.
Click to expand...
Click to collapse
it's all the same flash in twrp there's no downside

Very little reason to root.

For me no root no party, root a phone is mandatory

xNAPx said:
For me no root no party, root a phone is mandatory
Click to expand...
Click to collapse
Most of the things that used to be rooted for are now inluded in roms today.

Well I doubt using props or debloater without adb

While somewhat true, most of things, like recording phone calls, theming, dark mode, wifi boosting by doubling band width and even ram/swap files, as well as, many other features that we would root our phones for, are nowadays in stock roms.

Yes many are available, even debloating using adb, still rooting allows you to modify your system without using any PC and take control over it

I'm aware of the things it can still do, but there are many real performance tweaks anymore. Most stock roms are fast and smooth, due to all the ram and faster SoCs and GPUs, so there really isn't a need for overclocking or memory extenders (swap files) and theming with dark mode is available in almost every rom and you can disable any app via ADB, if need be. Not a huge need anymore.

On this I agree, at the beginning I wasn't sure to root it too, but still to debloat systemlessly and run commands with terminal I need it

You can debloat/disable via ADB command's without root. Also the way many phones are configured these days, you can't remove or delete many items within the system partition, thereby limiting your debloat capabilities.