Problem with SuperSU install with recovery. - LG G5 Questions & Answers

Welcome.
What can I say.. My phone: LG G5 H850 International, Android 8.0 Oreo. I'm doing everything like it's written in tutorial. Bootloader is unlocked, I have no problems with flash recovery via fastboot. **** happens when I try to root my device with SuperSU. Process of install is going like it supposed but after reboot I don't see supersu app and when I verify root status - it says it's not rooted. I tried again and again and again for about sixteen times and after last try I saw one failure command line: patching sepolicy failure aborting. I rooted and mod couple of devices and never had something like this. I hope someone will help me because without root - phone is trash with many sick problems like afterimages on screen, no manual video mode and not good quality of photos etc. Greetings from Poland.
EDIT: Maybe I should try Magisk in this case?

Thread should be closed because yesterday I rooted my LG with Magisk without any problems. Recovery is working, root too.
Yeah!

majhau said:
Thread should be closed because yesterday I rooted my LG with Magisk without any problems. Recovery is working, root too.
Yeah!
Click to expand...
Click to collapse
Okay, what was your solution?

Related

Rooting Astro TAB

Trying to root an Astrotab but I'm not able to connect the device with usb debugging because I don't have the correct USB drivers on my windows 10 machine. After scouring the web I've been unable to find any in existence and hopefully someone here has been able to do so or knows of some workaround. I'm new to rooting and I am using an application called oneclickroot , I don't know if this is the best method but the software isn't recognizing the device due to lack of drivers. Here are my device specifications below
Model A935
Android version 5.1.1
Firmware Version v3.3rc5
Kernel Version 3.4.39 [email protected] #9
Build Number A33_U92C_U992HB2C_1510077.20151228
root apk
try to get some rooting apk on tablet, and try to root with that
Which do you recommend? I heard that kingroot leaves behind alot of bloatware that is hard to get rid of
UPDATE
Still not able to locate any ADB drivers for windows 10 on this device. Tried non pc apk's Kingroot , Towelroot/Iroot. Still no success , any help would be appreciated.
Working...
After 4-5 grueling hours finally got it working! How do i know if this is temporary or permanent root? I used root checker and it says it is properly installed on this device. Only thing there seems to be alot of bloatware on my device now. How do I tell what is safe to remove? Some crap called one click , app cool , etc was removed and I lost root access. Re-did process and got root again but still have the same chinese applications present on my device. App Cool , King root , superUser.. My question is do I have to deal with having them on my device , or is there a safe way to remove them without losing root?
app
Remove all except Superuser because it is main root aplication
malivrag11 said:
Remove all except Superuser because it is main root aplication
Click to expand...
Click to collapse
Well that wasn't it , getting something about root not properly installed after checking in root checker when deleting all besides superuser...
now it no longer wants to root anymore , thanks for bringing me back to square one
PremiereENTITY said:
now it no longer wants to root anymore , thanks for bringing me back to square one
Click to expand...
Click to collapse
Anyone on this forum helps? I got it back working but I need a recovery for this device. It;s not present when booting into recovery mode. I am looking to flash or backup the ROM. Where can I get this for this device?
PremiereENTITY said:
Anyone on this forum helps? I got it back working but I need a recovery for this device. It;s not present when booting into recovery mode. I am looking to flash or backup the ROM. Where can I get this for this device?
Click to expand...
Click to collapse
I need this too. If anyone has a backup of the original rom it would be great.
PremiereENTITY said:
After 4-5 grueling hours finally got it working! How do i know if this is temporary or permanent root? I used root checker and it says it is properly installed on this device. Only thing there seems to be alot of bloatware on my device now. How do I tell what is safe to remove? Some crap called one click , app cool , etc was removed and I lost root access. Re-did process and got root again but still have the same chinese applications present on my device. App Cool , King root , superUser.. My question is do I have to deal with having them on my device , or is there a safe way to remove them without losing root?
Click to expand...
Click to collapse
Can you explain how you got it to root properly? I tried king root application on windows 10 but I couldn't get it to root. It's all in Chinese, as well.
I easily rooted this tablet with KingRoot then used the KingRoot to SuperSU script to get KingRoot replaced. But mainly I'm commenting because I just wanted any tablet owners to know that I have the stock firmware and flashing tools (windows) that u can use to get the tablet back to stock or save yourself from a bootloop ( I can confirm this because I bricked mine using substratum lol) Also I can confirm that marshmallow will b an option sometime during Q1 of 2017 as quoted from insipira.
Sort of....
The Marshmallow update will only work on A10 tablets manufactured after October 1, 2016 (according to the folks at Inspira) Unfortunately, it will give you a white screen and nothing more on older versions of the hardware - I know. I have one. I tried. It doesn't work. Save yourself the frustration. The biggest pain with the A10 is that the bootloader is locked and attempts to unlock it are a waste of your time. If you brute force KingoRoot on it, it will not survive a reboot because of the unlockable bootloader. The vendor is unable (or more likely unwilling) to provide an unlocking code which tells me future tablet business for self and clients will have to go elsewhere. PITY - it is a really nice little unit but not worth calling in the NSA to try to root it. Oh well, lots of other inexpensive Android Tablet vendors out there.
PremiereENTITY said:
After 4-5 grueling hours finally got it working! How do i know if this is temporary or permanent root? I used root checker and it says it is properly installed on this device. Only thing there seems to be alot of bloatware on my device now. How do I tell what is safe to remove? Some crap called one click , app cool , etc was removed and I lost root access. Re-did process and got root again but still have the same chinese applications present on my device. App Cool , King root , superUser.. My question is do I have to deal with having them on my device , or is there a safe way to remove them without losing root?
Click to expand...
Click to collapse
Can you explain how you were able to unlock the bootloader?
I have the same device and I've been unable to unlock the bootloader. I can get ADB working, boot into recovery just fine, but I can't figure out how to boot into the bootloader, whenever I try to (either using the adb command to reboot into bootloader or using recovery itself) it just shows the "Astro Tab" logo and gets stuck like that forever. I made sure to enable the option about allowing OEM bootloader unlock in the "Developer Settings" window.
Aurey24 said:
I easily rooted this tablet with KingRoot then used the KingRoot to SuperSU script to get KingRoot replaced. But mainly I'm commenting because I just wanted any tablet owners to know that I have the stock firmware and flashing tools (windows) that u can use to get the tablet back to stock or save yourself from a bootloop ( I can confirm this because I bricked mine using substratum lol) Also I can confirm that marshmallow will b an option sometime during Q1 of 2017 as quoted from insipira.
Click to expand...
Click to collapse
Can you explain how you were able to use KingRoot to root this? I downloaded the apk from http://kingroot.net, installed it, and clicked the "Try Root" option, but it got stuck on the "Acquiring Root" step after a few minutes and completely crashed.
Here is a picture of where it got stuck: https://i.imgur.com/L4Pxtjn.jpg I couldn't even screenshot since system was frozen, and even connecting via ADB didn't work at this point. The reason I noticed that the device froze was because the clock did not update (it was around 8:30 when I took the picture, not 8:16 as shown).
I'm also having an issue unlocking the bootloader -- I can't even get to the bootloader (see my earlier post for details) but that's a whole different issue.
--------------------
Edit: For reference, I added some info from the "About Tablet" section in the Settings if that helps.
Android version:
6.0.1
Kernel version:
3.4.39
Firmware version:
v6.0rc4_20160910
Kernel version:
3.4.39
[email protected] #18
Tue Feb 21 13:27:23 UTC 2017
Build number:
A83T_N10

Help me please! LG GX2 (F430L / D631 / VS880) update wrong ROM!

I have my LG GX2 F430L working perfectly with Sphinx ROM (it's from lgviet forum, sorry can not post link, I'm new). However then I found a guy posted a Lollipop ROM for it, so I tried it. Unfortunately it's a ROM built from Verizon VS880, and after finish updating there is no signal, also Knock On / Off is no longer working. Then I tried many ways to restore the Sphinx ROM but failed for 4 days already. Below is what I have tried so far:
- Root with Drake - Failed
- Root with LG Root Script - Failed
- Root with KingRoot - It said rooted, also rootchecker said OK but can not install SuperSu. Tried SuMe - Failed
- Tried to install CWM in many ways: apk file, flashing by adb - Failed - All the time after I tried Flashify or LG GX2 Recovery app and reboot - it says Boot secure error. As far as I know, bootloader locked and there is no way I can unlock it - There is no OEM unlock in developer option (tried the way with Nova - not worked), and when I tried fastboot oem unlock / fastboot flashing unlock - it said unknown command. Yes I did put my phone to fastboot mode.
So now please help - what could I do to give the Sphinx ROM back to my phone? Appreciate all suggestion as I tried many but still no hope.
Restore the original firmware then reinstall Sphinx.
Thanks es0tericcha0s, I for got to mention that I also tried to flash KDZ by LG Flashing Tool 2014, but always fail at 4%
Ah, yea, sorry, that makes sense since the build.prop has been changed, the flashing tool probably won't work right. Hmm. Weird that the posted this rom without root in the first place... How did you flash it? Via dd commands?
Thank you. When it was in Sphinx, I can use CWM properly and flashed the Verizon ROM that way. So now I guess need to get back to CWM to flash the Sphinx back :crying:
Does root work with Kingroot? If so, you might use a root explorer to change the build.prop to f430l and try the LG Update tool again. There's a new kdz flashing tool called LG Up as well.
Yes, it's rooted with Kingroot. So I'm gonna look for a F430L build.prop file to replace mine? Thank you very much, I will try this way!!!
You wouldn't need to replace the whole thing, just edit the appropriate lines. You could use the Sphinx rom zip one to compare. Make sure the permissions are set correctly or it'll soft brick.

Root LG MS210?!

I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .

Root/Unroot frustrations

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!

Question Lost root out of the blue

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.

Categories

Resources