Need help with going back to OOS stable - OnePlus 3 Guides, News, & Discussion

Right now i am on Open Beta 16 and I am looking to go back to stable and install TWRP to install new custom roms. I have been MIA in the scene for a while now but I am so ready to start again. If someone could guide me on what TWRP to use and how to go back that would be appreciated. I also want to go to the F2fs system unless it is worse, i am not sure on that. Thanks
-kabrty

kabrty said:
Right now i am on Open Beta 16 and I am looking to go back to stable and install TWRP to install new custom roms. I have been MIA in the scene for a while now but I am so ready to start again. If someone could guide me on what TWRP to use and how to go back that would be appreciated. I also want to go to the F2fs system unless it is worse, i am not sure on that. Thanks
-kabrty
Click to expand...
Click to collapse
I assume you know the basics? If not.
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
Now you don't want to use the TWRP from that thread. @eng.stk is having the most updated TWRP and I personally did not face any issues with it yet.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Now for root. I do recommend Magisk, why? I found it more user friendly and with the correct settings you can pass safety net which means you can play Pokémo GO and such with root. Note: Root is disabled by default if you go to Magisk manager you can enable this in the settings!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you have any more questions feel free to ask.

That would be vdry easy to do. Just follow the steps carefully:
1. I guess you are having a locked bootloader. So first unlock it and install TWRP. To do these follow this thread: here
Instead of using twrp from the above page download it from here: here
2 go though several rom and kernel threads, read the maximum number of pages you can so get kind of idea about what other users are experiencing and figure out what would work best for you. I again insist read. Particularly go though the thread of the rom, kernel or mod or whatever you'd be flashing. You'd be happy to help yourself later.
3 last but surely not the least. Learn to use the search function here on xda. This would help you save your time. For example, all the links i have mentioned above are from oneplus 3 's xda section only. If you had searched efficiently you would have got everything right away.
have a ball

Thanks guys but I figured it out on my own. The real reason why i asked is back when i followed the scence more, there was a problem with twrp and Community builds.

Related

First Things To Do After Getting My Mi Mix?

Just found out that I have a Mi Mix waiting for me when I get home. I've made a checklist of what I want to do to it to get it setup for my use. I wanted to know if anyone had anything to add or has done any of what I'm planning on.
Unlock Bootloader
This should be relatively simple. I already have my unlock permission and will be using the directions from here: http://en.miui.com/thread-202290-1-1.html
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
I will also follow the top reply to this thread which mentions linking your device to your Mi account before unlocking to prevent errors: https://m.reddit.com/r/Xiaomi/comments/5co8t1/mi_unlock_approval/​
Install TWRP
My plan is to follow these instructions: http://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960
This is where I start having questions. I've been out of the rooting and ROMing game for a couple of years. Does anyone recommend rooting with anything other than SuperSU? I'm reading that it was bought by a Chinese company and shouldn't be trusted. I've also read that using Magisk you can have root that is easily turned off. I'll admit I'm pretty lost at the moment when it comes to what Magisk does and how to use it. But if it is the recommended way of doing things I will do the research to learn it.​
Flash The EU ROM
I think my plan is to flash this EU ROM which debloats everything and seems to come with gapps and a lot of other nice optimizations: https://xiaomi.eu/community/threads/6-11-10.36056/
My first question is has anyone tried this?
My second question is will I need to reinstall TWRP and re-root? I think I will have to re-TWRP because on the TWRP page there is one version for stock and one for the EU version. I will be on stock first and I can't flash EU until after I flash TWRP. So I think the procedure will have to be:
Flash stock TWRP
Flash EU ROM
Flash EU TWRP
Re-Root?
Turn Off All Battery Optimizations
Don't have a guide for this yet but I'm guessing it's not hard to find. Feel free to reply with one if you have one.​
Personalize
Launchers/Themes/Icon Packs/etc. Don't need suggestions here since I already know what I have in mind.​
Anything else?
The only other thing I can think of that I might want to install is Xposed. I've never used it and don't know how to install it but I'll learn if I can be convinced that it's something I want.
What else am I missing?​
I think right now the biggest thing I'm curious about is if anyone has used the EU ROM and what the procedure is if you use that ROM since there are 2 different versions of TWRP for the Mi Mix. But any other suggestions on what to do with the initial setup or how to make my experience better are welcome. I'd also love to hear about any "gotchas" that aren't mentioned in the guides from people who have actually done it.
Well I took the plunge without waiting for feedback and for anyone who is interested, I'll answer my own questions. Read the posts that I linked in the OP to understand what I'm doing below. I will not cover how to get unlock permission as this has been covered elsewhere.
Unlock Bootloader
As far as I can tell by reading that thread, I do not need to install the developer ROM first. Is this correct?
Click to expand...
Click to collapse
This is not correct. You must install the Dev ROM and connect to WiFi and follow the steps to enable Developer options and login to your Mi account in developer options.​
Install TWRP
Before installing TWRP you must update back to the stable ROM. The non-EU version of TWRP will not work with the Dev ROM as of this posting. You can update to the stable ROM using the same steps as updating to the developer ROM. In the TWRP install guide I linked above, I stopped right after step 6 and continued below.​
Flash the EU ROM
Instead of flashing SuperSU after installing TWRP, I copied over the EU ROM linked above and flashed that. Then I followed the instructions starting from step 3 of this post to flash SuperSU, Magisk, and suhide: https://www.reddit.com/r/pokemongod...k_v7_systemless_xposed_v866_released/d8d7ziw/
The only change I made is that in between steps 4 and 5, I flashed the EU version of TWRP before continuing because otherwise the touchscreen would not work in TWRP. I used the most recent versions for the SuperSU, Magisk, and suhide and I did not flash Xposed yet but I believe I can do that in the future if I want to.​
That's where I'm at now. The rest of my checklist was mostly personal preference so I won't go into that. Hope this helps.
@chimera533
THX for taking the plunge & sharing your results with us.
I'm sure I'll be doing the same once mine arrives, hope you don't mind if I look this way if I have any questions regarding TWRP/Root/etc.....
Thank you for posting this, this is the exact list of what I will be doing when my Mi Mix comes in the mail (C'mon Ibuygou).
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
jim380 said:
I couldn't seem to find a EU rom for Mi mix though it is listed in the thread as a supported drive. Will you please drop me the link to download? Thank you.
Click to expand...
Click to collapse
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
It would be nice if you did an edit of your original post, rather than a 'by the way' post below it. It would be much easier to follow the instructions.
I've installed TWRP on multiple phones. The dm-verity stuff is new to me (A xiaomi/MIUI thing I guess),
so the sequence appears to be:
install Official MIUI China developer ROM
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
< Do you reboot now and go back into fastload now? or stay inside TWRP? >
Install EU TWRP
install supersu (again, before you exit TWRP?)
Install Magisk, suhide?
Apologies but I'm away from home at the moment. I'll update the OP with more detail when I have a bit more time. But I'll give you some quick answers below.
install Official MIUI China developer ROM
Remember to log in to your Mi account in the developer options
<unlock>
install Official stable rom
install Official (Non-EU) TWRP (requires stable)
copy/install EU ROM after step 6 (aka before exiting TWRP)
While still in TWRP, install SuperSU in systemless mode.
Boot to system once
Boot back to fastboot and install EU TWRP
Boot to TWRP and install Magisk, suhide
Boot to system and install magisk manager
Got the Mi Mix 128GB overpriced in Thailand, but without any waiting time.
Love your early thread, very helpful.
I also want to get twrp, suhide, magisk and xposed, but I like to stay on the Chinese Dev or official ROM, not xiaomi.eu, because I like the paid themes which are only available on official ROMs.
I've got a MIUI developer account for 4 years, so I can unlock the device directly, being on stable ROM.
Now the steps are a bit unclear for me. Do I understand them correctly?
1. Unlock bootloader
Download and install the developer rom: http://en.miui.com/download-317.html
Create/Login with your MI Account on the device.
Apply for unlocking the bootloader here: http://en.miui.com/unlock/
Install stable ROM if desired
2. Install official TWRP (NON-EU)
Boot into fastboot mode by turning off your device then pressing volume up and power button
Install Minimal ADB and Fastboot on your PC: http://forum.xda-developers.com/showthread.php?t=2317790
Download the correct TWRP image file: https://dl.twrp.me/lithium/twrp-3.0.2-0-lithium.img.html
Copy the twrp file to where minimal adb and fastboot has been installed and rename the twrp file to twrp.img
Open fastboot on your computer and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
3. Install SuperSU in systemless mode
Download newest SuperSU: https://play.google.com/store/apps/details?id=eu.chainfire.supersu / http://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
In ADB shell or TWRP shell, type
Code:
echo SYSTEMLESS=true > /data/.supersu
if you don't already have this file to configure SuperSU to install in systemless mode.
Flash SuperSU.
4. Boot to system
5. Boot into TWRP, install Magisk, suhide, Xposed
suhide: http://forum.xda-developers.com/apps/supersu/suhide-t3450396
systemless xposed 86.2: http://forum.xda-developers.com/attachment.php?attachmentid=3897543&d=1475913773
magisk: http://tiny.cc/latestmagisk
6. Boot to system and install Magistk Manager
magisk manager: http://tiny.cc/latestmanager
7. Install XPosed
chimera533 said:
I think I got mine from here: https://megadysk.pl/f/6.11.10
Just scroll down to the Mi Mix one.
There are 3 repositories to the 6.11.10 weekly ROMs at the top of the page here: https://xiaomi.eu/community/threads/6-11-10.36056/
As far as I know there are no stable EU builds for the Mi Mix probably because it's so new.
Also I believe the weekly updates show up here: https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
The Mi Mix was skipped for 6.11.17 as evidenced by the note at the top of the 6.11.17 thread.
That's about all I know. I highly recommend reading all or most of every link I posted here. I'll confess that if I had, I would've known things like having to flash back to stable before TWRP-ing as well as some other things.
Click to expand...
Click to collapse
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
jim380 said:
Thank you so much for your help. I installed the ROM and have had it running for 2 days now. Coming from a HTC 10 (custom ROMed and everything), I;m really not digging MIUI on this phone. Lags so much it's literally driving me crazy. My 2 yrs old LG G2, which also has amazing screen-to-body ratio btw, runs circle around this phone. Really disappointed about this phone due to the software performance issues.
Click to expand...
Click to collapse
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
underlines said:
I don't experience any lags on the original ROM.
From my experience those micro-lags and performance issuese showed up on various devices in my Android past whenever something was wrong with the ROM. A clean flash mostly helped solve the problem.
I'm currently on the original Chinese stable with SuperSu and TWRP. It's blazing fast. What's the reason to flash the xiaomi.eu rom?
Click to expand...
Click to collapse
I had a nightmare trying to get to the EU Rom yesterday, I was mostly successful, however after a reboot i'd lose Touch in both TWRP and System. Thanks to this post from Chimera533 I was finally able to do it!
Anyway the main reason for the EU ROM is to get rid of all the Bloat and Chinese throughout the ROM that you cannot get rid of. It also has Google Services baked in properly so everything works correctly.
I also had a few other little niggles while on the Chinese ROM :-
Purchases from Google Play Movies wouldn't work
No Smart Lock while connected to Android Wear
No way to replace BAIDU and set Google as the search
So far i'm loving the EU Rom, i've not seen any lag at all while using it and pretty much everything seems to work exactly as it should - it has enhanced the MIX experience so much for me - love this thing!
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
yakuzlin said:
Guys, how do I disable all battery saving optimizations / memory management optimzations? My background apps keep shutting automatically off after a while.
I'm on the default ROM without root (still waiting for developer approval)...
Click to expand...
Click to collapse
Go to the battery section & have a look around, you should find several settings for battery management.
You're gonna need root & an app such as Titanium Backup Pro, or, SD Maid Pro to disable a lot of the MIUI & Cheetah Mobile applications.
Fine tuning on a per app basis isn't enough (do not optimize battery savings for the apps you want to work properly, notifications, messaging, etc) .....
I highly recommend flashing the EU ROM, it seems to have better memory management than the Global ROM, but, you'll still need to disable a lot of the MIUI apps & all of the Cheetah Mobile s***ware to get memory management more to what you're used to experiencing.
One other item, go to Developer Options & disable MIUI Optimization, it should be the last item or close to it....

Most stable Custom ROM upgrade and HOWTO for Droid 4

Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Shplad said:
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Click to expand...
Click to collapse
see the index for correct safestrap version, 3.75 is latest, but you need the Droid 4 one
[INDEX] Development Motorola Droid 4
GApps are android version specific, opengapps.org are good
I haven't used the Droid 4 much since cm11, it's likely still a good option
sd_shadow's How-To Videos for Droid 4
Sent from my XT1254 using XDA Labs
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
The link for safe strap is not dead there are two versions. One from stargo and the other is a modified safe strap for unused partitions redone by some one else. You need to look in the correct posts and thread. Here is the download: http://www.internauta37.altervista....afestrap-maserati-v3.75-unused-partitions.apk
As far as for gsm keep looking you'll probully find something. I can't help you with that because I never needed to use but it shouldn't be to hard to do or figure out.
As far as wich rom you want to use just try a few different ones and see wich one you prefer to use as a daily driver.
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
moodroid said:
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
Click to expand...
Click to collapse
Shplad said:
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
Click to expand...
Click to collapse
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
moodroid said:
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Click to expand...
Click to collapse
Shplad said:
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
Click to expand...
Click to collapse
As far as I understand it (which could be totally wrong), 11 and 12 are no longer being developed and will only receive security updates, so from that point of view, I guess they will be more stable. But 13 and 14 will work, but there may be the odd issue here and there (particularly with 14 which is still quite new). You'd have to have a quick scan through the comments to see if there's anything that's like to be a problem for you.
With reagrds to GSM, I should just try it and see if it works to begin with. If it doesn't, then download the patch, reboot, go into safestrap, install the zip then reboot.
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provides superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Wow, this is a lot to take in. Thanks. So, I don't quite understand the repercussions. Once I root, does that mean any ROM OS that boots is somewhat more vulnerable, cause it's like being logged on as root in Linux, or does it depend which ROM I'm using or something else?
Bobcus Leper said:
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provided superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Click to expand...
Click to collapse
Okay, I figured out after my last post that root status depends on which ROM you are running, and of course installing a ROM without root status would put you back to unrooted status.
I downloaded Lineage OS 13 and verified the MD5SUM. I rooted the phone using Shadow's video.
Now I want to make an image of my NAND or have some other method of restoring the stock ROM before I install a new ROM. At what stage in the process do I do that and what is the safest tool / method to do that? RSDLite? Adding another ROM slot and using Nandroid backup?
Awaiting anxiously...
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Shplad said:
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Click to expand...
Click to collapse
As far as I understand it, and again, this could be wrong, using RSDLite is usually a last resort in the unlikely event that you've completely messed up your phone. You will lose everything, and your phone will back to how it was when you bought it. I've never needed to use RSDLite myself, but from what I've read, it's a pretty reliable way to get your phone working again. As long as you follow all the instructions, and install CM (LOS) 13 into another slot, it's very unlikely that you'll damage your original stock rom and you'll still be able to boot into if ever you need to. Hopefully, someone who knows more about it will comment also...
I got Safestrap 3.75 special version for unused partitions installed. I didn't realize it allows you to make TWRP ROM backups.
I made a backup of the stock ROM. The first time I did that, I got an error stating it couldn't find or access /boot.
Strangely, the second time I tried, it seemed to work fine.
I copied the folder with the stock ROM backup to my PC, just in case. I managed to flash with Lineage OS 13. It booted fine, but I forgot to select the Gapps zip as well. It does not appear to be rooted after bootup.
1. Do I need to reinstall Lineage 13 or is there way to install the apps without reinstalling Lineage?
2. What is the normal state of this ROM? I'm not sure if I have to root Lineage 13. If I don't enable root, will I be unable to run TWRP recovery and add the Gapps zip file and reinstall? I don't want to be stuck with a successful Lineage install and no apps. I'd find another way to install the apps, but I'm guessing you can't without the apps themselves, no?
Help!
Okay, I figured out how to install just gapps 5.1-2015-05-23-24 . However, during configuration, I cannot get the phone to connect to gmail via WiFi (I don't have a data plan).
"Validating Server Settings...
Couldn't open connection to server."
I see other people had this in other version of Android. Is this a particular problem in Lineage 13? Any solutions known?
...AAAANDDD Google Play Services has closed.
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
EDIT:
I tried these suggestions, just in case.
https://productforums.google.com/forum/#!topic/gmail/ACSvDiQoufI
Now, I'm getting the error:
"Problem with account setup
Username or password is incorrect"
Google Play Services keeps closing. Should I uninstall the gapps and install a more compatible one? I think network connectivity is not stable.
Shplad said:
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
Click to expand...
Click to collapse
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
moodroid said:
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
Click to expand...
Click to collapse
Shplad said:
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
Click to expand...
Click to collapse
I meant on this website. In the 'Droid 4 Android Development' section (https://forum.xda-developers.com/droid-4/development), there a thread for each of the roms. The one for CM (LOS) 13 is https://forum.xda-developers.com/droid-4/development/cm13-0-marshmallow-unofficial-builds-t3270938
moo:
Thanks for that. I didn't post there earlier because I thought it was only for developer reports of bugs, and my coding skills are exactly zero. Should I wait to see what happens in that other thread and not post back here until I hear something from there?

Got new One+ 3T Some questions

I have received today my new mobile 1+ 3t a3010
oxygen 4.1.3
where should i start ?
tweaking kernel, roms...
please refer me to the right threads
thanks in advance.
- Unlock bootloader first: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
- Flash OOS 4.1.5 or the newest Openbeta (or Freedom OS if you understand what you do)
- if you need root: flash supersu or magisk
- if you want: Flash Kernel (ElementalX, Franco, Blu, Flash, etc)
- very optional: https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
How one decides to mod the phone (custom ROMs, kernels, etc.) is completely up to personal preferences and tastes. Everyone will give you a different answer to your questions, and many owners of this phone will never mod it at all, and be completely happy. Read up on existing threads, and you'll figure out what are the best options for you. There are also plenty of existing threads with suggestions and favorites regarding ROMs, etc. so no need to start another such discussion.
So really, my advice on where to start, is to read read read. Understand the methods and steps before you begin (and that goes with any of these devices). The previous answer had some good resources, for a start. And you'll find many more useful threads in the "Guides" forum section. My additional suggestion would be to know how to return to stock with the full zips: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Along similar lines (and in agreement with the prevous answer) I would recommend updating to latest OOS 4.1.5 or Open Beta, to ensure you are on the latest firmware and modem, before doing other mods.
Thank you both for great answers,
i did successfully bootloader unlocked and twrp flashed
Now which is oos 4.1.5 you talking about ?
like https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
and this https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
is ok to flash now ?
You posted the same thread twice. But yes, that is correct. You'll want the full zip from Post #2 of that thread. Then follow the instructions in Post #3, using second method, for users with TWRP. It also says for root users, but it's irrelevant whether you are rooted or not, as long as you have TWRP installed you'll need to use the full zip; as stated at the bottom of Post #3, if you use the OTA with TWRP, it will fail or you will soft brick!
Also, if you root, TWRP will stick (this is what I always do after flashing the updates). If you choose not to root after installing 4.1.5, you might find that TWRP is removed. But you might be able to avoid this by booting back to TWRP after installing 4.1.5, butbefore rebooting to OS. Otherwise, if you find TWRP is gone, just flash again using fastboot.
Tell me please,
can i flash custom kernel being on stock 3.1.5 with stock recovery?
Just stick with stock. LineageOS is kind of awful. Theres a million bugs that affect daily usage even on a perfect install and setup. Its just not worth it. I'd go with freedomOS CE 2.10. Very solid rom with nice extra options to remove useless google apps like photos and google music youtube and the like. It even allows magisk which is a fantastic rooting systemless method. I would also add the adblocked youtube module or app from a thread by Master_T. Just stick with basic rooting function and your experience will be superb. The more advanced you go with this phone the more prone to breaking something you get.
You were already advised how to mod the phone, back up in Post #2 above. I assume you mean locked bootloader along with stock recovery. I believe what you suggest won't work, and the stock recovery will not let you flash an unsigned zip. You need to unlock your bootloader and flash custom recovery TWRP. Then you can flash a custom kernel. But again, it's already been described by another back up on Post #2.
Also, I'm pretty sure you mean 4.1.5 (not 3.1.5), as you already stated the phone came with 4.1.3 (so 3.1.5 wouldn't make much sense). So please proofread before posting, to avoid confusion (and I was really confused by the number 3.1.5 at first).

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.

[GUIDE] Oneplus 6T Android Q BETA TWRP & MAGISK TUTORIAL

So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
kluongo said:
So this is my first thread and had a heck of a time trying to successfully root the 6t using Magisk and TWRP. Why might you ask? Because the unofficial TWRP for the Oneplus 6T has a bug with the Media Transfer Protocal (MTP) so once TWRP is installed, you can't use it to install flashable zips. The device shows the 6T internal storage as empty and therefor you cant flash a zip if TWRP cant find a zip to flash. So anyways heres what I did to get this working.
*****NOTE***** I am not a dev, i simply stumbled across a solution (work-around), to the TWRP MTP issue, and therefor if anything goes wrong with your device, it is on you. DO NOT BLAME ME if you brick your device. If you so choose to follow this guide, ANY/ALL risk and the subsequent consequences, are YOURS AND YOURS ALONE.
***CREDITS*** TO: @topjohnwu for MAGISK & @mauronofrio for his unofficial android Q TWRP
STEP1: Grab this TWRP https://androidfilehost.com/?fid=1395089523397961761
STEP2: Grap magisk beta v19.2 https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
STEP3: Run the following command: fastboot flash boot twrp.img
***NOTICE ABOVE COMMAND*** (uses "flash boot" instead of "boot")
STEP4: Manually reboot into back into recovery
***NOTE*** once in recovery I used "swipe to allow modifications" , dont know if it matters
STEP5: Go to adb sideload tab from within TWRP Recovery
STEP6: Once adb sideload finishes loading, run the following command: adb sideload magisk.zip
STEP7: Let sideload finish, reboot device, open magisk app and follow its instructions to finish install.
Click to expand...
Click to collapse
The twrp we have works fine dude
Lol
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
JUST FYI
The mtp issue is a known bug with the Q developer preview.
Rite from download page.
"Known Issues
Camera, portrait mode does not work
Ambient Display is not working
System stability issues
Encryption will change in the next preview build
Some apps may not function as expected when running on this Developer preview release
Issue With MTP cannot copy rollback from PC to Phone."
Not with twrp.
The only issue with twrp at the moment is reading v3 synthetic keys to decrypt if you have pin/password set and running may security patch.
kluongo said:
And you are referring to using TWRP on Android Q beta correct??? Because when I tried using the latest stable TWRP for 6T but with Android Q... It would not flash
Click to expand...
Click to collapse
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
kluongo said:
Thank you twinn for clarifying that... So I stand corrected on twinns point... But not on fullofhells needless comment
Click to expand...
Click to collapse
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
fullofhell said:
Use Blu spark, secondly the resolution for mtp, is enable dev options and turn on USB file transfer. Then USB works. Use a prepatched twrp and pre rooted twrp Blu spark kernel. Flash in fastboot, twrp works fine. Fully. Not apparently not needless if u still have issues posting erroneous comments that serve no purpose. U should read. It serves so many purposes. U would see the fix for mtp on Q and how in the main twrp thread a week or more ago I discussed how twrp works fine if u do as I listed there.. I read everything, I assumed every other user does the same.
Click to expand...
Click to collapse
:highfive:
WOW.
Where to start here?
The TWRP you linked (https://androidfilehost.com/?fid=1395089523397961761) is for OPO 6, not 6T, but it does say fajita, and not enchilada
TWRP works fine for us, if you use the latest.
P and Q are different beasts, as of now, and there are posts on how to flash TWRP on Q.
This thread seems redundant an unnecessary.
But....that's just my $.02
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
kluongo said:
So first, i just searched all 9 pages of the 6t Guides thread section... not one single thread explaining, or detailing, any guide or tutorial, for individuals to play around with Q... On that point, not redundant.... Secondly the fajita image i posted is not for the 6... its from mauronofrio for the 6t, under the thread he started for twrp images for the 6t... so.. if it is in fact for the 6... maybe he should be notified?..... and if this thread is redudnant, why cant i find any guide detailing steps to mess around with Q?
Click to expand...
Click to collapse
Here's a thread about Q on the 6T: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174 (specifically post #62)
The TWRP link page you linked specifically says "Download test-twrp-3.3.0-Q-fajita.img for the OnePlus OnePlus 6" but I commented that it was correctly for the 6T. I would get ahold of Mauronofrio to inform him of the error.
It's only redundant because after reading the thread I posted above^, it seems we have some waiting to do until we even get a stable Q build.
Thanks!
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
No need to stay quiet, just learn to use the search function, and participate on the already created threads instead of creating new ones. (Just a suggestion...)
And the ad hominem attempts are unnecessary.
Love,
'full-of-myself'
No..
Love,
@fullofhellself
?
Damn wth did I do..lol... We are a system of checks and balances for all users. Full of myself... Yeah okay.. better be nice or mom's not gunna pay your internet bill.. and I hate trumpian politics. I just loathe redundant unusable posts. As do my constituents here..
kluongo said:
Yes, I did in fact see that thread and briefly read it over. On the contrary, it did not help me in the manner i needed. Alot of people don't have the time to dig through threads to find an answer to a problem, especially from a thread which was never intended to address said problem in the first place (according to its title, as well as the entire first page of posts). I have been following these forums, quietly, since the galaxy s4 was released and hence, when I look for a guide or missing piece of information I require, i know to read and look around a bit before starting a thread. As such, I have not needed to create a thread EVER... and then there was this problem with no clear cut guide, thread, solution... nada.... so alas, I decided to provide one for a change... I am now reminded why i choose to stay mostly quiet... because xda has become a honeypot full of negative trollers, and "full-of-themself" donald trumps, when it should contain more people offering constructive critisicm, positive environment, and turning the less knowledgeable into the more informed android enthusiast.
Just my $.01
Click to expand...
Click to collapse
Chill out, no need to bring politics into a phone modding forum, seems kinda silly doesn't it? But yes, you should have just gone to the existing 6T Android Q thread and just used the search function. Wouldn't have been that hard. I never even installed Android Q and I even remember reading through numerous posts of people wanting to return to stock. I don't blame you for posting or anything, I'm just letting you know that there definitely was a clear-cut easy way to find a way to go to stock from the Q beta.
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
juggz143 said:
LMAO xda is getting out of control... I agree with the OP as the other thread is not about this particular issue... Which was getting twrp and magisk going on the Q beta (NOT returning to stock - like where did that even come from if your following along lol)
I could easily see him getting flamed for hijacking the thread if he posted this tutorial in the other person's thread. You can't win for loosing any more.
This is also why I stay mostly silent on here smh!
Click to expand...
Click to collapse
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
fullofhell said:
omfg. Read post 1. Reread. Read again. Now read your sentences. Try not to feel dumb. Search function = no one wastes time. That's all.
Click to expand...
Click to collapse
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Sent from my SM-G975U1 using Tapatalk
juggz14301 said:
[emoji848]Maybe it's you who should re-read. The first post doesn't mention anything about returning to stock. He's trying to install magisk on a BETA, which is the polar opposite of returning to stock [emoji2375][emoji2363]...
If anything having a dedicated thread for a "specific reason" is much easier to find, and less time consuming, than searching for a possible answer in the comments of another thread on a somewhat related post. He's making the search more efficient since you mention "wasting time", you're the one wasting time *****ing on a usefull post lol.
You're assuming installing TWRP is for the purpose of returning to stock but there's a ton of other reasons someone could want to install TWRP and then magisk... Also there's other ways to return to stock besides TWRP soooo [emoji2375] i guess that's a waste of time too...
What are we doing SMH [emoji23][emoji24][emoji88]
Click to expand...
Click to collapse
Who is talking about returning to stock? He's talking about installing TWRP and magisk on Q beta.

Categories

Resources