Related
Hi There,
I've the Problem that I havent't TWRP-Recovery and SuperSu after Updating to OOS 4.1.1 and Android 7.1.1.
Do someone know if i had to flash TWRP with qiping all Data? Or is there a Way to Flash TWRP and SuperSu without wiping? =(
Sorry I'm new to Android and started with the oneplus 3t. So i didn't know that i hadn't to update the Phone.
Or is the best opinion for me to choose a custom rom? But there are so much, i don't know what to choose.
Thanks for help! =)
Neither TWRP nor SuperSU will wipe anything.
It's totally up to you whether you need a custom ROM or not. If you want features like switching tracks just with your volume keys, you'll totally need a custom ROM since stock ones don't provide this feature. But this is just one example of many.
Regards.
Sent from my OnePlus 3T using Tapatalk
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
Click to expand...
Click to collapse
If you need help with anything, just ask.
I never had to wipe anything. I just wipe the phone when I want to remove the encryption.
EDIT: regular security patches is one big reason for me to install a custom ROM.
Thanks, I'll ask my questions
But why did the update delete trwp and supersu?
I was happy with OOS but missed the future of centering the clock.
May I ask which custom rom you use?
Updates remove SuperSU because they essentially flash over all non-user partitions (everything except /data, where your files, settings and user apps are stored). To root the OS, SuperSU installs its files in the /boot partition, which gets overwritten during ROM flashes. Root gets deleted any time you flash any mod (including most custom ROMs, since they also replace /boot). The only exception to this is if you flash a custom ROM that comes pre-rooted.
TWRP does not get deleted immediately during flashing, but rather when you first boot up afterwards. OOS will attempt to replace any custom recovery with the stock recovery when it first boots up after updating. You can get around this by either flashing TWRP again, or rooting immediately after flashing a ROM update, before you reboot (flash ROM, wipe cache/delvik, flash root, reboot). Most custom ROMs will not replace your custom recovery.
There's a few threads containing OPSystemUI.apk mods in the Themes, Apps and Mod section, though most of them also contain a bunch of other graphical modifications. If you only want to center your clock and nothing else, it can be achieved by modding OPSystemUI.apk yourself, though there is a bit of a learning curve to it.
m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
Click to expand...
Click to collapse
You are mixing things up a bit but don't worry, I'll explain.
You need to unlock the bootloader first, and that always wipes your data for security reasons. So if your phone is stolen, the thief won't be able to access your data by installing TWRP or a custom rom. After unlocking you install TWRP (custom recovery), and use it to flash stuff. (roms, mods, etc)
After that you only lose data if you (or a rom) mess things up, and your data becomes unaccessible, or you relock your bootloader for whatever reason. That's why you should always backup to a computer before doing major flashing/upgrades, etc.
If you upgrade the rom you'll lose root and/or TWRP, but you can flash it again as explained by others.
Hi there,
so I've flashed TWRP and SuperSu again. You are all right, i haven't to wipe anything. I really mixed up things. But now everything is working for me.
Okay, i have to learn how to get my OPSystemUI.apk modify it and flash it back?
I will seach the threads and learn.
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.
Hello!
I am currently using a nontreble build (RR Nougat) and I want to try out a treble build (perhaps Havoc Pie) soon and I wonder what is needed to make sure I can switch back to my current setup without effort in case of problems. It would be nice if someone can give me some input and prevent me from shooting in my own foot
What partitions do I have to backup (using TWRP) and to whipe for making a clean install and still being able to revert everything?
I think there are parts of the data that can not be backed up with TWRP. Which data is affected of this, and will the be destroyed/modified when I install a treble build?
I am a bit nervous as I do not have much time for reverting in case of problems, and I cannot test my backup in advance.
Thanks!
theBoatman
theBoatman said:
Hello!
I am currently using a nontreble build (RR Nougat) and I want to try out a treble build (perhaps Havoc Pie) soon and I wonder what is needed to make sure I can switch back to my current setup without effort in case of problems. It would be nice if someone can give me some input and prevent me from shooting in my own foot
What partitions do I have to backup (using TWRP) and to whipe for making a clean install and still being able to revert everything?
I think there are parts of the data that can not be backed up with TWRP. Which data is affected of this, and will the be destroyed/modified when I install a treble build?
I am a bit nervous as I do not have much time for reverting in case of problems, and I cannot test my backup in advance.
Thanks!
theBoatman
Click to expand...
Click to collapse
First of all you need treble supported twrp.
If you have your old rom zip.
Then just backup data
Then wipe everything just leave vendor partition.
If you dont like pie than again wipe everything just leave vendor.
Install the old zip with gapps
Then restore the backup of data.
Thats it.
I have a Samsung Note 8 released and I want to install Lineage OS 17.1, I know I lose a lot of functionalities but, I love Pure Android. I already have the ROM downloaded, I have installed ROMs several times in other devices but I always made the mistake of not making a backup to the original firmware. This time, I want to. Before installing TWRP Recovery and all the necessary I would like to make a complete backup of the Samsung Firmware and so in case of anything always have it back from the factory.
What is the problem? I do not know with what tools I would have to make the backup, I do it before installing TWRP recovery, I can do it through software using a PC. The truth is, I'm a bit disoriented.
The other part is that after making the copy, where do I start. What Recovery should I install and where can I find the instructions for its installation?
In advance thanks a lot for your response.
Hello my friend,
Looking for any way to do a full OP10PRO backup (all partition, modem, nvram...), and since there is no TWRP available, is there any other way to do this please ?
Thanks
Is there way to do FULL backup since there is not TWRP actually
Hello People, Just ordered an OP 10 pro and waiting the shipment ( yeah, my OP3T is now old :D) I saw there isn't TWRP actually on this device. I always like to do a FULL backup of my phone in case of emergency ( brick or something else). Is...
forum.xda-developers.com