Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
phaino00 said:
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
Click to expand...
Click to collapse
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
draymond1987 said:
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
Click to expand...
Click to collapse
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
phaino00 said:
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
Click to expand...
Click to collapse
I’ll have to edit that part then
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Here you go this is from the December A1 Firmware image. enjoy
LeoD said:
Here you go this is from the December A1 Firmware image. enjoy
Click to expand...
Click to collapse
Is there a way I can make a zip, to flash via EX’s app?
You’re a live saver, so far!
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
vandyman said:
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
Click to expand...
Click to collapse
You make a really decent point. Guess I’m just antsy to have all the fixes and not be on a buggy firmware.
The tools in This thread may help.
Related
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Lord_Miraak said:
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Click to expand...
Click to collapse
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
riyan65 said:
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
Click to expand...
Click to collapse
Yes thanks! I did it yesterday, watching a Brazilian video. I had to download 3 different ROMs to be able to do such a process; so I did the process through Fastboot. Thank God I did not have to buy another device, hehe. And I'm already using another Custom Rom at the moment (RR, but I plan to change it as soon as I find another great new one that does not bug WhatsApp). Thank you again!
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Serpent.king said:
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Click to expand...
Click to collapse
I haven't installed or changed anything in a few months besides updates...
pbsavages said:
I haven't installed or changed anything in a few months besides updates...
Click to expand...
Click to collapse
If your device isn't crashing or anything else I wouldn't worry Abt the root. I'm guessing the updates have something to do with it. Most operating systems will have auto triggers that stop or disable certain things
pbsavages said:
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Click to expand...
Click to collapse
Not sure why you lost it but do you continue to lose it after flashing the patched image again? On the latest Magisk I take it?
Since your rank is senior member imma ask where do I start a thread I got a problem with this stupid tablet i need solved
Lughnasadh said:
Not sure why you lost it but do you continue to lose it after flashing the patched image again? On the latest Magisk I take it?
Click to expand...
Click to collapse
Yeah, latest Magisk is what I patched it with for the July update. I'm at work but I'll flash the patched boot image when I get home. This hasn't happened before, just wanted to see if it's happened to anyone else.
Serpent.king said:
Since your rank is senior member imma ask where do I start a thread I got a problem with this stupid tablet i need solved
Click to expand...
Click to collapse
Go to the device's forum, click on "Post Thread" at the top and choose the appropriate section (e.g. General, Question, etc...).
pbsavages said:
I've lost root on my Pixel 6. Been rooted since I got it, I update every month then root it. On July 22 update, rooted fine.. I think yesterday I just lost root out of nowhere. I've been sideloading OTAs and fastboot flashing Magisk patched boot image, no issues until suddenly losing it. Any ideas why?
Click to expand...
Click to collapse
I'm in exactly the same situation. I updated, patched boot.img with latest Magisk (25200) and flashed -> had root. Then I lost it I think after the first restart.
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
I just flashed a patched boot.img, tried to restart a few times and so far so good, root stays. Let's see if that works long term.
mic3r said:
I'm in exactly the same situation. I updated, patched boot.img with latest Magisk (25200) and flashed -> had root. Then I lost it I think after the first restart.
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
I just flashed a patched boot.img, tried to restart a few times and so far so good, root stays. Let's see if that works long term.
Click to expand...
Click to collapse
Nope, I've had it direct installed for almost a whole month
mic3r said:
I'm not sure but I'm suspicious that I forgot to open Magisk and do install -> direct install to have permanent root. Maybe that's your case as well?
Click to expand...
Click to collapse
You don't need to use direct install to have permanent root. That option is there for when you are already rooted and want to update Magisk itself via direct install instead of patching the boot image again, or if you fastboot boot rather than fastboot flash the patched image.
If you just fastboot booted the patched image rather than fastboot flashed it, then you will only have temporary root until you do a direct install or fastboot flash the patched image.
Serpent.king said:
Having root alone voids the warranty on most devices. I'd say somewhere in your venture of installing and changing things you messed something up, triggered an error of some kind.
Click to expand...
Click to collapse
No. Does not void warranty. Do not spread crap like this.
I've seen it get pissed off with the contents of the boot partition and "revert" it and/or somehow swap boot_b into boot_a. After this happened a few times, I just make sure to write the patched boot.img to BOTH boot_a and boot_b and haven't had it happen since.
Build number
DE2117_11_C.17
Hardware version
DE2117_11
I keep seeing T-Mobile version, INTL version, DE18 and all that. I'm so confused, I just need root.
I believe that's the international version since mine is DE2117. Not sure because of the "_11" at the end of yours. Maybe that signifies you updated it, in which case you will probably have to downgrade it.
Rooting this phone is a headache btw. I'm not even sure if I should be providing instructions because I bricked mine multiple times while attempting and had to keep restoring with MSMtools, and now I'm not even sure I can update it without losing root. I don't even think I did anything differently when it finally worked, it's just luck.
Anyway, first step is to download the international version of the MSMtools and payload dumper. look up how to dump the boot image with payload dumper from the MSMtools. And make sure you don't attempt to do anything to the device before unlocking your bootloader (and you'll have to unlock it again everytime you restore with MSMtool).
From there you should be able to follow guides.
@swee08315
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
jova33 said:
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
justauserthatusesaphone said:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
Click to expand...
Click to collapse
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
jova33 said:
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
Click to expand...
Click to collapse
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
jova33 said:
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
Click to expand...
Click to collapse
I'll get it when I'm on my PC
the c17 one, correct?
justauserthatusesaphone said:
I'll get it when I'm on my PC
the c17 one, correct?
Click to expand...
Click to collapse
Don't worry about it. I redid the MSM tool since the phone wasn't even setup yet, no big loss.
swee08315 said:
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
Click to expand...
Click to collapse
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img.
jova33 said:
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img
Click to expand...
Click to collapse
You could turn off automatic system updates so it doesn't reboot automatically and then you install the update and when it asks you to restart, go into magisk and click install and install to inactive slot then you go back to the system update page and click restart. I don't know whether Google's ota system makes it easier or not.
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
swee08315 said:
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
Click to expand...
Click to collapse
I never had that issue but if you do, press uninstall and restore images (DON'T REBOOT), then after installing the updates (DON'T REBOOT) press install and install to inactive slot. Press the reboot button and you're done.