Multiple layers of oxygen os - OnePlus 6T Questions & Answers

Ive recently purchased one plus 6t and I unlocked bootloader and install twrp in it. After following all instructions of xda developers, i tried to wiped oxygen os beta 4 ( i was using beta 4 then) and after wiping everything ( including oxygen os ) from the device, i booted into the system. According to me, if no os is installed on one plus device, it should not show anything if we boot into the system. But surprisingly, I found that oxygen os beta 3 was running. Now, how did it happen I can't figure out... maybe there are multiple layers of oxygen os... I don't know
Sent from my ONEPLUS A6010 using Tapatalk

Check out these links. Also, one other item you should search for and research if you haven't is how to recover your phone and the limitations of the methods available to any device you're using. XDA has a lot of helpful posts to guide you, use it's search features.
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

yaksh26 said:
Ive recently purchased one plus 6t and I unlocked bootloader and install twrp in it. After following all instructions of xda developers, i tried to wiped oxygen os beta 4 ( i was using beta 4 then) and after wiping everything ( including oxygen os ) from the device, i booted into the system. According to me, if no os is installed on one plus device, it should not show anything if we boot into the system. But surprisingly, I found that oxygen os beta 3 was running. Now, how did it happen I can't figure out... maybe there are multiple layers of oxygen os... I don't know
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
The OP6T is an A/B device. The phone has two partitions of which one is active. If you install an OTA Update it'll be installed to the inactive Partition WHILE you're using your phone. There is no Need to let the phone boot in recovery mode to install the update. After the update is finished it'll boot the other Partition where the update was installed.
I think this is what you're experiencing here

RLM703 said:
Check out these links. Also, one other item you should search for and research if you haven't is how to recover your phone and the limitations of the methods available to any device you're using. XDA has a lot of helpful posts to guide you, use it's search features.
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Click to expand...
Click to collapse
Thanks for very helpful links

Related

TWRP Sources

Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
user7743 said:
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
Click to expand...
Click to collapse
Use whichever you like, both work
Just be careful about the version, versions lower than 3.1.0 are dangerous and backing up stuff can wreck your phone
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
user7743 said:
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
Click to expand...
Click to collapse
Maybe it is a mirror... can't test but you could compare md5
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
user7743 said:
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
Click to expand...
Click to collapse
well there are more than one TWRP versions out there it seems. For example when you flash the universal bootloader TWRP displays 3.1.0-N while on stock 7.1 it shows 3 1.0-0
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
fastjohnson said:
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
Click to expand...
Click to collapse
The problem I think is data partition.
Every time I swich rom to oficial I have to format data, wipe dont work. Maybe before restore format data in f2fs or ext4 for oficial rom
Enviado desde mi ZTE A2017G mediante Tapatalk
May sound strange but it was because I flashed the ROM and gapps from my USB c style flash drive so I just decided to do the phone over fresh. It's working 100% all fresh install. Thanks for your help but no matter what I did it wasn't going to install those restores.

Unofficial Lineage, Magisk

Will putting Magisk on My ZTE A2017G with unofficial Lineage 14.1 get passed Safety net and allow me to use apps like Android Pay?
Sent from my ZTE A2017U using Tapatalk
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
P650SE said:
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
Click to expand...
Click to collapse
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Supersilver-Haze said:
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Click to expand...
Click to collapse
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGApps, followed by Magisk 14.0 and anything else you'd like to install before rebooting.
P650SE said:
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGapps, followed by Magisk.
Click to expand...
Click to collapse
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Supersilver-Haze said:
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Click to expand...
Click to collapse
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
P650SE said:
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
Click to expand...
Click to collapse
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Supersilver-Haze said:
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Click to expand...
Click to collapse
Haha, that's quite alright. Feel free to let me know should you have any further problems with the Axon 7. I'm a new owner but have a lot of experience with previous Android devices such as the LG G4 and OnePlus One.
P650SE said:
Haha, that's quite alright. Feel free to let me know should you have any further problems.
Click to expand...
Click to collapse
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Edit: disregard the I figured it out I had it permanently on LTE so I wasn't able to make or receive calls on LTE it seems
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Hmm, i'm not sure about that one because I didn't use the phone for making calls when I was running LineageOS on my Axon 7. If you installed the Android N modem before flashing the ROM it should work fine in theory. Maybe you can find someone else in the LineageOS thread who's having the same issue.
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
FuzzyDunlop9 said:
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
Click to expand...
Click to collapse
I also had problems getting Viper4Android to work on this device. For me it would install fine, but the audio effects made no difference in apps like Spotify and YouTube, despite having the deep-buffer fix enabled. Try using this version by ahrion instead, it works for me! (Just make sure you remove anything relating to previous installations of V4A beforehand!)
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I don't know how much difference it would make, but installing the Official build of LineageOS is probably slightly better. The method of switching from Unofficial to Official is basically the same as what I posted previously in your other discussion thread:
1. Make sure your apps and files from Unofficial LOS are backed-up.
2. Download the Official LOS ROM and copy it to either the internal or expandable SD card storage on the Axon 7.
3. Download the latest GApps arm64 ZIP for Android 7.1 from OpenGapps and copy it to either the internal or expandable SD card storage on the Axon 7.
4. Reboot the phone into TWRP custom recovery.
5. Enter the 'Wipe' menu and wipe the partitions /data, /system, /dalvik and /cache. (It might not be 100% necessary to wipe /data since you're just switching to an official build of the same ROM, but it is still advisable. You could try installing the ROM without wiping /data, but you may encounter some issues!)
6. Switch the the 'Install' menu and flash Official LOS, followed by the OpenGApps ZIP.
7. Reboot the device.

[GUIDE][addison] SETUP Moto z play XT1635-02 : from stock 6.0 to custom ROM.

I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194

TWRP for Honor 8 pro encrypted mode

Can anyone help on how to modify current TWRP to support encryption?
Nothing as of now. The support is dead.
Yesterday I tried rooting my phone by using almost every instance of magisk available on the web, but I either end up with a bootloop or Error 255.
There is no point installing twrp, you will only break your phone.
Only solution is never trust honor again in terms of development support.
SAME Issues.
shailendra1993 said:
Nothing as of now. The support is dead.
Yesterday I tried rooting my phone by using almost every instance of magisk available on the web, but I either end up with a bootloop or Error 255.
There is no point installing twrp, you will only break your phone.
Only solution is never trust honor again in terms of development support.
Click to expand...
Click to collapse
Unfortunately, i'm regretting getting the H8P instead of the OP5. Kinda had a feeling this would happen but took a shot anyway.
Tried many versions of Magisk but all ends up in bootloop. Spent over 30 hours on the device, tinkering.
Best bet would be to flash Stock, lock bootloader and forget about SU . The only choice given how expensive the phone was to a common man when it released.
No more Honor or Huawei every again. For me or anyone who askes for suggestions.
I'm not that into android that i can jump in to help devs aswell. But i will try to stay active and support those who brick their device.
@anirudh & @shailendra1993
Sorry, but you seem both out of topic.
It seems to me latest official magisk is working on your device by flashing a patched ramdisk via fastboot.
Coming back to OP, the latest public TWRP available for your device seem to be there https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223But they may not support encryption...
Anirudh A said:
Unfortunately, i'm regretting getting the H8P instead of the OP5. Kinda had a feeling this would happen but took a shot anyway.
Tried many versions of Magisk but all ends up in bootloop. Spent over 30 hours on the device, tinkering.
Best bet would be to flash Stock, lock bootloader and forget about SU . The only choice given how expensive the phone was to a common man when it released.
No more Honor or Huawei every again. For me or anyone who askes for suggestions.
I'm not that into android that i can jump in to help devs aswell. But i will try to stay active and support those who brick their device.
Click to expand...
Click to collapse
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
psbhullar said:
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
Click to expand...
Click to collapse
Thanks ! I get constant bootloops when I flash almost all versions of magisk on stock Oreo 8.0.0.323 . I'm now using AOSP from open krin . 8.1 . Not the most stable rom, but I love stock Android. Definably miss a few stock rom features though. It would help if you tell us the version of magisk flashed and also stock rom version.
And the installation method you followed for magisk was patching boot using magisk manager and flashing the image via fastboot right?
Anirudh A said:
Thanks ! I get constant bootloops when I flash almost all versions of magisk on stock Oreo 8.0.0.323 . I'm now using AOSP from open krin . 8.1 . Not the most stable rom, but I love stock Android. Definably miss a few stock rom features though. It would help if you tell us the version of magisk flashed and also stock rom version.
And the installation method you followed for magisk was patching boot using magisk manager and flashing the image via fastboot right?
Click to expand...
Click to collapse
Follow each step as mentioned and and it works perfect.
https://www.google.co.in/amp/s/foru...de-magisk-root-honor-8-pro-oreo-t3743587/amp/
I am using this past few weeks on Oreo 8 with no bootloops. Yes with Xposed i too had boot loop issues.
Thanks! Works.
psbhullar said:
Follow each step as mentioned and and it works perfect.
https://www.google.co.in/amp/s/foru...de-magisk-root-honor-8-pro-oreo-t3743587/amp/
I am using this past few weeks on Oreo 8 with no bootloops. Yes with Xposed i too had boot loop issues.
Click to expand...
Click to collapse
Hey,
I followed those same instructions before.
From v 15.4, we can directly extract our boot.img , patch it using magisk manager and flash it using fastboot.
And it works like a charm. With data encrypted.
Thanks for your inputs
psbhullar said:
Are you looking to have Magisk with Safety net pass ? Let me know i can help. I am on latest Oreo with Magisk and all seems ok.
Click to expand...
Click to collapse
wait wait... so you have root and adblock /titanium backup working on latest oreo? please let me know.. I want to get to oreo update but I can't lose titanium and adblock (and keep decrypted my sdcard?!?)
Sent from my DUK-L09 using Tapatalk
I come from an Honor 8 completely turned inside out (root,twrp,xposed,gravity,substratum,v4a,titanium backup,kali linux and so so so on).
Can I hope to get almost half of them on my new Honor 8 Pro? I would stay on latest stock B189, but If I well understand there are problems with TWRP and TB because of encryption. What is the state of the art we can get on Nougat? Thanks a lot.
gianmaxfactor said:
I come from an Honor 8 completely turned inside out (root,twrp,xposed,gravity,substratum,v4a,titanium backup,kali linux and so so so on).
Can I hope to get almost half of them on my new Honor 8 Pro? I would stay on latest stock B189, but If I well understand there are problems with TWRP and TB because of encryption. What is the state of the art we can get on Nougat? Thanks a lot.
Click to expand...
Click to collapse
https://consumer-tkb.huawei.com/tkbapp/downloadWebsiteService?websiteId=768024

Considering unlocking and all that. Recommendations?

So, I've had this phone since shortly after launch. I came from a pixel 2 XL after one of my middle school students broke it. I pretty regularly ran custom roms or just a couple modules and root apps here and there. I know you lose fingerprint sensor by installing custom roms, just curious as to what everyone else did? I assume the procedures are all still the same as the pixel 2.
Sent from my [device_name] using XDA-Developers Legacy app
I unlocked yesterday, root and installed a kernel and run OOS Stock Rom. You should do that, if you don't want to loose the FP. Probably I would be trying some ROMs, but not now. I come from a OP3 with Custom ROM.
kickenwing13 said:
So, I've had this phone since shortly after launch. I came from a pixel 2 XL after one of my middle school students broke it. I pretty regularly ran custom roms or just a couple modules and root apps here and there. I know you lose fingerprint sensor by installing custom roms, just curious as to what everyone else did? I assume the procedures are all still the same as the pixel 2.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
There's 2 roms we have here that have the fingerprint sensor working, because they're actually Magisk modules that run on top of OOS. Revovation Ice (Only works with stable OOS) and XXX No Limits (works with stable and beta, you can find this one in the OnePlus 6 forum). I'm using Renovation Ice right now, I love it!
H4X0R46 said:
There's 2 roms we have here that have the fingerprint sensor working, because they're actually Magisk modules that run on top of OOS. Revovation Ice (Only works with stable OOS) and XXX No Limits (works with stable and beta, you can find this one in the OnePlus 6 forum). I'm using Renovation Ice right now, I love it!
Click to expand...
Click to collapse
Sweet. I actually tried Friday 2 and still have it and it did not go well. Could not figure out what gapps to download, seems like everyone I picked was the wrong one. Had to learn how to put this phone back to stock and was freaking out. Nandroid backup didn't work. Every time I hit reboot system it would put me right back to the same spot, except it was TWRP encrypted, wouldn't reboot. Ended up having to figure out how to get it back to stock and haven't tried it again yet.
Sent from my [device_name] using XDA-Developers Legacy app
kickenwing13 said:
Sweet. I actually tried Friday 2 and still have it and it did not go well. Could not figure out what gapps to download, seems like everyone I picked was the wrong one. Had to learn how to put this phone back to stock and was freaking out. Nandroid backup didn't work. Every time I hit reboot system it would put me right back to the same spot, except it was TWRP encrypted, wouldn't reboot. Ended up having to figure out how to get it back to stock and haven't tried it again yet.
Click to expand...
Click to collapse
Why are you trying to install Gapps? The stock OOS already has them. Renovate Ice runs on top of the stock ROM. Back to Stock is as simple as flashing the latest ROM even with a factory reset(complete wipe). Set up as normal after flashing, then flash Twrp. Install Magisk if you want Root then Renovate Ice. There are guides on how to do all of this.
Havoc rom required then according to the directions. That's the too I tried Friday night. It was a rough night.
Sent from my [device_name] using XDA-Developers Legacy app
kickenwing13 said:
Havoc rom required then according to the directions. That's the too I tried Friday night. It was a rough night.
Click to expand...
Click to collapse
Oh ok if you are installing non-OOS ROMs yes.
schmeggy929 said:
Oh ok if you are installing non-OOS ROMs yes.
Click to expand...
Click to collapse
You guys have me all about the stock ROM though. Glad that is a thing. Hopefully the installation process goes more smoothly
Sent from my [device_name] using XDA-Developers Legacy app
kickenwing13 said:
You guys have me all about the stock ROM though. Glad that is a thing. Hopefully the installation process goes more smoothly
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Phone corrupt? Simple fix actually. Download the MSM Download Tool, it's here on XDA in the Guides section for some reason. There's the T-Mobile version of the tool if you bought your device from T-Mobile, and the global version of the tool (two separate threads on here) that will reflash the device if you bought from OnePlus directly. Shoot me a message if you need some help, I don't mind at all! [emoji1]
EDIT: Note that this tool formats your device COMPLETELY. You'll lose all your pics and files, but it cleanly installs OOS for you and relocks your bootloader as well.
H4X0R46 said:
Phone corrupt? Simple fix actually. Download the MSM Download Tool, it's here on XDA in the Guides section for some reason. There's the T-Mobile version of the tool if you bought your device from T-Mobile, and the global version of the tool (two separate threads on here) that will reflash the device if you bought from OnePlus directly. Shoot me a message if you need some help, I don't mind at all! [emoji1]
EDIT: Note that this tool formats your device COMPLETELY. You'll lose all your pics and files, but it cleanly installs OOS for you and relocks your bootloader as well.
Click to expand...
Click to collapse
I downloaded the tool, and have some experience using them but ended up doing the fastboot method . Are they the same thing except one is just via toolkit ?
Sent from my [device_name] using XDA-Developers Legacy app
kickenwing13 said:
I downloaded the tool, and have some experience using them but ended up doing the fastboot method . Are they the same thing except one is just via toolkit ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well, basically the MSM tool doesn't go through your bootloader. This device has a Qualcomm download mode built in that's an even lower level mode than the bootloader. The MSM tool can restore your device even if it's TOAST (for example, corrupted bootloader or just can't boot to it.). It's easier that fastboot as well! It's a perk of having a OnePlus for sure! [emoji106]

Resources