Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?
Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.
sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.
Related
Ok guys,
I found this a while ago:
https://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166
I wanted to do the same on the urbane 2, to give us the full potential of this watch.
There are a few things to be changed.
After getting the boot.img, for us it is the 'fstab.nemo' that has to be edited first.
I really want to finish this for us too, but always short on time. Will try to go further tonight and get the partitions online on gparted. anybody wanna join and help, just let me know.
:highfive:
Ok, late update. while i repaired my watch, i was back on this thread.
seems we can't flash it as intended while secure boot is breaking on this point. whenever i want to start with ext4, the watch will not boot to system, but hang on lg bootlogo
sebj84 said:
Ok, late update. while i repaired my watch, i was back on this thread.
seems we can't flash it as intended while secure boot is breaking on this point. whenever i want to start with ext4, the watch will not boot to system, but hang on lg bootlogo
Click to expand...
Click to collapse
Nice to see you again for inspiring us the reason why I was stuck in staring at the bootlogo. Good job guy. Hope there could be idea to deal with that in someways.
we would need a way to turn of Secure Boot.
I have the ABOOT image, but don't know how to modify it
sebj84 said:
we would need a way to turn of Secure Boot.
I have the ABOOT image, but don't know how to modify it
Click to expand...
Click to collapse
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.
wendster said:
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.
Click to expand...
Click to collapse
i will try the new version today.
anyhow, I'm still interested to get /system modifiable and the only way will be to get rid of secure boot.
Was the old wear 1.5 already squash FS?
maybe flashing back would be an option?
wendster said:
It seems that aboot will be checked by SBL when booting so turning off Secure Boot can truly be a difficult job for me due to knowing little about it. But on the other hand, I've tested Magisk V21.4, finding it working amazingly well. I wonder if it's able to function what we need systemlessly by the powerful tool - Magisk.
Click to expand...
Click to collapse
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
I'm not sure whether earlier WearOS has already begun using suashfs or not as I'm a new user of WearOS because my watch is secondhand.
EdXposed doesn't support Android 7 and below, how did you install it? You would like to try original Xposed Framework in Magisk by rovo89 and install the modified Xposed Installer provided by the author to properly detect Systemless Xposed. However, it may lead to high CPU rate and cause an unpleasant using experience. Good luck, hope we can find the way to make this watch totally in control.
sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
Futhermore, I'm working on trying emulating Mifare cards on my watch by using NFC but only to find it so difficult to archieve my goal. Is there any way to emulate cards with all sectors?
sebj84 said:
did you try riru and sandhook with 21.4?
i bootlooped earlier when installing sandhook.
Click to expand...
Click to collapse
Solved!
I found it from here when I was finding some posts in Coolapk but came across the great surprise what we need.
Just download it and flash it by fastboot.
Enjoy!
wendster said:
Solved!
I found it from here when I was finding some posts in Coolapk but came across the great surprise what we need.
Just download it and flash it by fastboot.
Enjoy!
Click to expand...
Click to collapse
did you try that already. its too good tonbe true.
will be downloading in a minute
with the ext4 image i will hang on 'searching for updates' while setting up the watch
ok, clean install fixed that for me, but still get a prob setting up the watch with wear app
finally connection isnt possible
In actual fact it's unnecessary to wipe data. Just wipe cache and davlik cache in recovery and then you will get your watch with nothing changed but system unlocked. I've succeeded in this way.
wendster said:
In actual fact it's unnecessary to wipe data. Just wipe cache and davlik cache in recovery and then you will get your watch with nothing changed but system unlocked. I've succeeded in this way.
Click to expand...
Click to collapse
I went a harder route....
Finally had to flash stock and update again.
Flashed then after the fresh Wear 2.0 update and it worked flawlessly.
But i still encountered the problem with connection to Phone.
Could only resolve by adb reconnect to phone.
But anyhow, works now and is all fine.
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.
Flash through fastboot
Put img in platform tools
Run the following command
Fastboot flash boot magisk_patched.img
And enjoy
https://drive.google.com/file/d/10KezX3FzffZviGimQP7gkR66UVVj4DgT/view?usp=drivesdk
Which image is that, though. There are 3 different builds.
ZeroKool76 said:
Which image is that, though. There are 3 different builds.
Click to expand...
Click to collapse
As the OP says it's for the build-number ending on 007 .
Sent from my HTC U12+ using XDA Labs
Ahh, i didnt see the whole title in portrait mode
ZeroKool76 said:
Which image is that, though. There are 3 different builds.
Click to expand...
Click to collapse
007. I am thinking on updating to 011.c4, but, might not happen
Kevtrejo37 said:
007. I am thinking on updating to 011.c4, but, might not happen
Click to expand...
Click to collapse
Does anyone know what the two 011 build are??
CyberpodS2 said:
Does anyone know what the two 011 build are??
Click to expand...
Click to collapse
Google hasnt released anything on them
I'm on 0 11.C4 and used the same process to patch its boot image, rooted just fine.
Only hiccup is sometimes I get stuck on Google logo after a reboot. Have to force power of and power back on again.
matlear said:
I'm on 0 11.C4 and used the same process to patch its boot image, rooted just fine.
Only hiccup is sometimes I get stuck on Google logo after a reboot. Have to force power of and power back on again.
Click to expand...
Click to collapse
Might have to do with that one being on a newer google play system image, an app you installed, or magisk module
Narrowed the reboot issue down to systemless hosts, does the same on 007.
**Update - when i try flashing in TWRP (sideload) it fails to mount cache or data, this could be causing the problem? Anyone know the fix?**
Hey everyone.
Long story short I updated to 11.0.4.1 (Global/US) and didn't retain root/magisk.
I'm attempting to re-root/Magisk with a patched boot img however after flashing everything Magisk installed says "N/A" and I'm fairly lost on how to fix this problem since I've attempted multiple times.
What's weird is that I fail Safety Net & my corporate apps recognize me as rooted.
I tried using the Magisk uninstall zip this most recent attempt as a "restart" however same result.
Has anyone else run into this issue / know how to fix? Is it some boot slot situation? I'm lost.
Cheers
ktimque said:
Hey everyone.
Long story short I updated to 11.0.4.1 (Global/US) and didn't retain root/magisk.
I'm attempting to re-root/Magisk with a patched boot img however after flashing everything Magisk installed says "N/A" and I'm fairly lost on how to fix this problem since I've attempted multiple times.
What's weird is that I fail Safety Net & my corporate apps recognize me as rooted.
I tried using the Magisk uninstall zip this most recent attempt as a "restart" however same result.
Has anyone else run into this issue / know how to fix? Is it some boot slot situation? I'm lost.
Cheers
Click to expand...
Click to collapse
Is it a know good boot image? Maybe install magisk via twrp side load or via micro sd,
hammered58 said:
Is it a know good boot image? Maybe install magisk via twrp side load or via micro sd,
Click to expand...
Click to collapse
Do you have a patched 11.04.1 global US one I can use? I tried side loading too
ktimque said:
Do you have a patched 11.04.1 global US one I can use? I tried side loading too
Click to expand...
Click to collapse
I do but not right now , I just used it a hour ago so I know it's good,, I can pm you in a hour and send you a link
hammered58 said:
I do but not right now , I just used it a hour ago so I know it's good,, I can pm you in a hour and send you a link
Click to expand...
Click to collapse
Appreciate it friend
ktimque said:
Appreciate it friend
Click to expand...
Click to collapse
Sent, check your pm
hammered58 said:
Sent, check your pm
Click to expand...
Click to collapse
Thank you sir
OP updated
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone