I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Trippyy Doee said:
I just got my bootloader unlocked this morning and I am ready to get it started however all I see are Verizon and Google store bought methods
Click to expand...
Click to collapse
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Badger50 said:
Interesting wording. If you mean that you can now toggle OEM unlocking on, then unlocking the bootloader with fastboot is the same no matter what device you have.
Click to expand...
Click to collapse
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
Magisk is the only way and there is no twrp
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Is there a working Magisk Canary build that can patch my boot.img?
Trippyy Doee said:
Sorry for that lol But what I meant was just any root method using magisk because I used the latest 20.2 and it failed for me. And TWRP if any . Just a point in the right direction basically ?
Click to expand...
Click to collapse
p70shooter said:
Magisk is the only way and there is no twrp
Click to expand...
Click to collapse
Like @p70shooter said. There is no other way to root besides magisk, and there is no TWRP as of yet. If rooting with 20.2 didn't work, then try 20.1. You can find it here :good: https://github.com/topjohnwu/Magisk/releases
Trippyy Doee said:
Is there a working Magisk Canary build that can patch my boot.img?
Click to expand...
Click to collapse
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
p70shooter said:
Don't know. I just use stable, like they recommend. I know people do use Canary just fine but can't help you there
Click to expand...
Click to collapse
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Trippyy Doee said:
This what I'm getting when I keep trying to patch it. And it is the correct stock image with my build number.
Edit : I'm just going to have to do this after work . I thought I had time but I'm just rushing probably just missing everything.
Thanks for the help guys
Click to expand...
Click to collapse
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Badger50 said:
Just a little FYI for you my friend. Have you downloaded the factory image coinciding with your current build? If not, then do so, then extract the factory image, then extract the image.zip, then pull the boot.img from there, place it on your phones internal storage, then try to patch it with magisk. I just did it myself with the 20.2 stable version and it worked fine :good:
Click to expand...
Click to collapse
Yea I was certainly rushing . I used the wrong boot file. Thanks alot. Finally off work so now I get to enjoy rooting my first Pixel phone. ?
Related
If I have formatted and installed with encryption disabled, what is the right way to get encryption back?
Can I just go into Settings>Security & Fingerprint>Encrypt Phone and enable it there?
Yup, that should do the trick. Didn't try on T3, but used same method on one of my prev phones.
Did that work?
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
AndreiVolk said:
I did it on OOS 4.1.1 with twrp and franco kernel installed. It worked for me :good:
Click to expand...
Click to collapse
I wonder if it works with a non oos rom though
stonew5082 said:
I wonder if it works with a non oos rom though
Click to expand...
Click to collapse
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
AndreiVolk said:
Well all custom roms work fine with encrypted devices so i don't see why it shouldn't be possible to encrypt your device on a custom rom. If you want to be 100% sure ask in the thread of your rom
Click to expand...
Click to collapse
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
stonew5082 said:
It worked. I disabled root to be on the safe side and encrypted. I get errors in twrp now, but they don't seem to effect anything.
Click to expand...
Click to collapse
nicknacknuke said:
May i know what error TWRP gives after you encrypt your phone ?
I plan to do so as well...
Click to expand...
Click to collapse
Root is not a problem neither. i did it with root enabled.
That twrp error is normal. When you boot in twrp it shows the error that it can't mount data because you're encrypted and you need to type in your password first.
I also suggest you to use blu_spark's twrp because it's always updated. The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
AndreiVolk said:
The official twrp for the op3t hasn't a maintainer anymore and it seems abbandoned..
Click to expand...
Click to collapse
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Didgeridoohan said:
How do you figure that?
https://eu.dl.twrp.me/oneplus3t/
Click to expand...
Click to collapse
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
AndreiVolk said:
I mean here on xda. The last build on xda is the 3.0.4.1 which it never came out. There was the 3.1.0.0 which had the wipe bug for the 3t. I don't know who is making those builds and i don't neither know if they test it.
Click to expand...
Click to collapse
You were talking about the official builds... That's the official downloads from the official TWRP website (https://twrp.me). There's a world outside XDA as well...
A bit bummed out after loosing root after updated to the latest version of Oxygen OS
How can I solve this, is it necessary to re-flash anything ?
Thanks in advance !
Charlied43 said:
A bit bummed out after loosing root after updated to the latest version of Oxygen OS
How can I solve this, is it necessary to re-flash anything ?
Thanks in advance !
Click to expand...
Click to collapse
It's expected to happen that way. Just re-flash root in TWRP. If you updated to Oreo, forget supersu, not working anymmore, use magisk. 14.6.
sansanc said:
It's expected to happen that way. Just re-flash root in TWRP. If you updated to Oreo, forget supersu, not working anymmore, use magisk. 14.6.
Click to expand...
Click to collapse
Thanks ok, so I reboot back into TWRP and flash Magisk ?
Please be specific my rooting' skills are way out of practice ..
sansanc said:
It's expected to happen that way. Just re-flash root in TWRP. If you updated to Oreo, forget supersu, not working anymmore, use magisk. 14.6.
Click to expand...
Click to collapse
I think I've lost TWRP recovery! Is this possible ? Seems like I can only boot into stock recovery ; (
Charlied43 said:
I think I've lost TWRP recovery! Is this possible ? Seems like I can only boot into stock recovery ; (
Click to expand...
Click to collapse
You need to install twrp again as well
Root and twrp
Charlied43 said:
A bit bummed out after loosing root after updated to the latest version of Oxygen OS
How can I solve this, is it necessary to re-flash anything ?
Thanks in advance !
Click to expand...
Click to collapse
Follow this link and you will solve your issue:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
aakashverma0007 said:
You need to install twrp again as well
Click to expand...
Click to collapse
Thanks dude, all good I have restored TWRP and #root however Magisk is now telling me that I fail the safety net check ; ( what now ?
Charlied43 said:
Thanks dude, all good I have restored TWRP and #root however Magisk is now telling me that I fail the safety net check ; ( what now ?
Click to expand...
Click to collapse
what version of magisk did you flash? also did you only flash magisk or something else too?
B0unze said:
what version of magisk did you flash? also did you only flash magisk or something else too?
Click to expand...
Click to collapse
I now am updated to 15.2 and yes, only Magisk so far..
Cheers!
Flash blu spark TWRP via fastboot. Search the forum. Then install magisk 14.6. you should be good that way.
Hi folks,
What we used as beta ROM is now published as official stable release known as version RMX1991_11.C.12 for Chinese model of Realme X2.
Probably anyone can upgrade the phone now in any possible way.
The bad news is FP stops working as soon as you patch vbmeta for disabling AVB...
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
yakovpol said:
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
Click to expand...
Click to collapse
Then, you will not loose fingerprint?
AlAneed said:
Then, you will not loose fingerprint?
Click to expand...
Click to collapse
Exactly
yakovpol said:
Exactly
Click to expand...
Click to collapse
Magisk can be installed and we still have the fingerprint working?
AlAneed said:
Magisk can be installed and we still have the fingerprint working?
Click to expand...
Click to collapse
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
yakovpol said:
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
Click to expand...
Click to collapse
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
I will try to search for it. Is it just a normal app to install from Play store? or requires other method?
One more thing, TWRP working with it or no?
Thanks
---------- Post added 10th April 2020 at 12:36 AM ---------- Previous post was 9th April 2020 at 11:38 PM ----------
I guess I am not able to understand how to do root? I searched for system base root in the web with no luck
Would you mind explaining how to do root without Magisk?
osamanazim said:
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
Click to expand...
Click to collapse
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
yakovpol said:
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
Click to expand...
Click to collapse
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Mikelsteven said:
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Click to expand...
Click to collapse
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
yakovpol said:
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
Click to expand...
Click to collapse
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Put some labour on searching through Internet please. So you will be sure if to update or not
To me it works just fine.
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Black Screen problems while playing COD Mobile. Iit is a common problem on sobre Android 10 upgraded devices.
But all the rest of software running and working smoothly.
can someone please confirm if the feature of Waze returning to top during voice call is working? i have the globalized version by mettis and it doesn't work there (have CN device)
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.
Hello there, i have a honor 9 lite (lld-l31) i'm searching a recovery.img to patch with magisk.
thank you for your help. I search for hours on web, but i've found nothing
Catoplepas said:
Hello there, i have a honor 9 lite (lld-l31) i'm searching a recovery.img to patch with magisk.
thank you for your help. I search for hours on web, but i've found nothing
Click to expand...
Click to collapse
Here you go (EMUI 9.1only):
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Here you can download patched recovery_ramdisk (v23.0), TWRP and Magisk manager 23.0 apk.
If you want, you can update Magisk version via Manager after installation.
Ok, nice. I make a try. Really, really thank you!
Catoplepas said:
Ok, nice. I make a try. Really, really thank you!
Click to expand...
Click to collapse
No problem.
OK, i rooted the devices, but i have a problem: google play service isnt compatible with this device. I tried to use microG but nothing happened.
Do you know how can i fix it?
Catoplepas said:
google play service isnt compatible with this device
Click to expand...
Click to collapse
what device? Nobody here is a telepath...(afaik )
Yes, you've right. Even the same: Honor 9 lite lld-l31. I'm trying to reinstall magisk and seeing what happeninp
Catoplepas said:
google play service isnt compatible with this device.
Click to expand...
Click to collapse
Under stock EMUI?
Can you post a screenshot?
What version of Magisk do you have installed?
Hey man, sorry for my late. Yes, it was the official stock EMUI, using the recovery.img that you linked me.
I just wiped all and did it all again and now it works. I don't know what happened ahhaha.
BTW at this point i can do a guide of this device
Catoplepas said:
Hey man, sorry for my late. Yes, it was the official stock EMUI, using the recovery.img that you linked me.
I just wiped all and did it all again and now it works. I don't know what happened ahhaha.
BTW at this point i can do a guide of this device
Click to expand...
Click to collapse
it would probably be better to use stock recovery_ramdisk for LLD-L31 and patch it via magisk manager. It is true that Recovery and eRecovery are the same for ANE, LLD, BND devices, but there may be nuances...
So download the full stock LLD-L31 9.1.0.xxx from androidhost.ru and use the "Huawei update extractor" to extract the original Recovery_ramdisk.img (if you want to make a guide).