Related
#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
this is mosty a copy and past cuz i didnt find this part of the forums when i had to remake my acc. if u watch the video u'll see what i did and what i should cuz the how-to for install magisk is broken to say the least
i have a sony xperia z3v and before u ask yes i did follow when was on the xda but NOTHING works as u see in this video here - https://www.youtube.com/watch?v=Jaga6MUcTdc&feature=youtu.be.
so first thing i need is a Custom Recovery. so i follow what that page here - https://www.xda-developers.com/how-to-flash-install-custom-recovery/ says...
first thing it is say i need Android SDK but never once talks about needing it ONE TIME.
2nd, both links given on that page for the custom recoverys 404! - https://imgur.com/bV9egdH
so what do i do next? i follow whats given and BOTH SITE R DEAD! also that page doesnt ONCE going into how to set up a custom recovery at all.
how is that u guys can help me out when it comes to flashing my sony xperia z3v back to stock after i F-ed up on a root and yet not have a set by set for geting Magisk to work install and work on your phone?
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Didgeridoohan said:
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
yes u do need a custom recovery as said on this page here - https://www.xda-developers.com/how-to-install-magisk/
"What You’ll Need:
A device running Android 4.2+
Custom Recovery (how to install)
We’ll be using TWRP in this guide"
i have the magisk manager already install as is my phone it rooted as u can see in this SS from the phone here - https://imgur.com/a/Kq1EChq but as u see magisk has a red X since its not installed so i go to install it but it give a .zip so i use that and it errors out EVERY ****ING TIME as see here - https://imgur.com/a/VyAslvt
if u toke a few mins of your day to watching the video instead of being a ass and commenting that knowning full well u could have watched the video to see i did everthing that the pages sad u wouldnt be most the comment u just did. u just make yours look like a ass. i want ppl the help me not say "u dont need a custom recovery" when the page on the how to install SAYS U ****ING NEED ONE.
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Didgeridoohan said:
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Click to expand...
Click to collapse
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
let me make it as simple to understand what im looking for. i want to use my Sony Xperia Z3v to game assets dumps for Uta-Macross so i can have pull the 3D models and cards (very nice photos) from the game. to do this i need to have my sony phone rooted and i need to have Magisk so i can hide the root from Uta-Macross so i launch into the game to download the assests to do a dumb. everthing up to this point i have YET to understand what do at all. that link u give - https://topjohnwu.github.io/Magisk/install.html says to this then go here then go here and do this over and over again never saying just do this, this, and this, and your done.
tankball said:
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
Click to expand...
Click to collapse
The instructions by @topjohnwu are pretty complete... They do assume that you are somewhat familiar with things like fastboot, but that is information that can easily be found by searching the big ol' interwebz.
Using a custom recovery is one of the ways of installing Magisk. If this is the route you really want to go I suggest you take a look in your device's forum here on XDA:
https://forum.xda-developers.com/z3
That's usually a good first step since you'll likely find others discussing the same device specific topics.
But if you take a look again in the linked docs, you'll find that you can also use something called boot image patching (which doesn't require a custom recovery at all):
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Rooting and tinkering with your device does require a certain level of knowledge about what you're doing. If you can't follow/understand the instructions available there's a good chance you might mess up your device. If you have your data backed up somewhere off the phone (which you should always have when playing with this stuff) you should be good since a complete and catastrophic failure is very unlikely. It's really annoying to have to set everything up from scratch though...
But if you take a look again in the linked docs said:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching[/url]
Click to expand...
Click to collapse
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
tankball said:
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
Click to expand...
Click to collapse
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Didgeridoohan said:
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Click to expand...
Click to collapse
i should also root the phone again also?
tankball said:
i should also root the phone again also?
Click to expand...
Click to collapse
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Didgeridoohan said:
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Click to expand...
Click to collapse
ok now im lost again. to do date dumps for Uta-Macross i need a rooted phone so i can pull the files without windows again tard and saying "unknow error" when i go to copy the files from my phone. but to play this game i need to hide the root from Uta-Macross so i need to use Magisk. is Masgisk a root itself? im really lost again
Magisk provides a way to do systemless modifications to your device, it is a root solution in itself, and it has the ability to hide itself and it's components from most apps and services that look for a rooted or modded device.
This is kind of the basics, so I reallly suggest you do more research before continuing. The best source for information is the Magisk GitHub page:
https://github.com/topjohnwu/Magisk
Start there, take a look at the readme and the documentation available and continue searching for whatever other information you might need.
I'm not going to be available for further assistance for the next 8 to 9 hours (I hope, but that's entierly up to my little one). G'night.
nothing i did worked. the .zip fail or the D6708_23.4.B.0.319_1288-1477_R30C.ftf file in the .zip witch in the rom from the phone, it will ALWAYS say failed, unsupported/unknow image format.
Morning. Like I posted previously, old (and new) Sony devices have been known to have issues installing Magisk. Search your device's forum for Magisk related posts and you'll likely find the info you need.
Good luck.
Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.
plan3tgreen said:
Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.
Click to expand...
Click to collapse
I've done so many factory resets and wipes(somewhere in the 20s.) I have finally given up on this. Because now i've ended up stuck, impossible to get past ODIN. I get this wonderful little message: "Only official released binaries are allowed to be flashed."
plan3tgreen said:
I've done so many factory resets and wipes(somewhere in the 20s.) I have finally given up on this. Because now i've ended up stuck, impossible to get past ODIN. I get this wonderful little message: "Only official released binaries are allowed to be flashed."
Click to expand...
Click to collapse
I'm downloading a stock and will attempt it later in odin.
plan3tgreen said:
I'm downloading a stock and will attempt it later in odin.
Click to expand...
Click to collapse
Still getting "Only official released binaries are allowed to be flashed(RECOVERY)."
By the way thanks for helping, i'll be sure to voice my opinion about how helpful this place is.
plan3tgreen said:
Still getting "Only official released binaries are allowed to be flashed(RECOVERY)."
By the way thanks for helping, i'll be sure to voice my opinion about how helpful this place is.
Click to expand...
Click to collapse
Give it time for someone to be able to help.
Not everyone has a note 9 and should be posted on note 9 forums.
The reasons why you are getting official binary error is OEM is locked and/or you have KG and/or Rmm state being in prenornal state.
plan3tgreen said:
Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.
Click to expand...
Click to collapse
With those phones I'm pretty sure you have to power the phone on by pressing vol up and power, then release the two when you see the bootloader warning screen. This boots the phone into root mode. Just pressing power normally boots them into normal mode.
GeeAyeZee said:
With those phones I'm pretty sure you have to power the phone on by pressing vol up and power, then release the two when you see the bootloader warning screen. This boots the phone into root mode. Just pressing power normally boots them into normal mode.
Click to expand...
Click to collapse
this was just my issue.
after following {awebsite}topjohnwu.github.io/Magisk/install.html, to the letter and going round in circles, it was this simple bit that i was missing.
once magisk has gone through the process once, it seems that the root is applied automatically going on.
as a hint, if you install titanium backup *root required* from the play store, then you can check very quickly if you presently have root or not.
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
Thank you. I have followed the guide to the letter. My screen (in dl mode) is showing OEM bootloader thingy lock is OFF... but I am still getting the 'only official...' error message when trying to flash the boot tar file made in the guide
3mel said:
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
Click to expand...
Click to collapse
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
tonyboy_23 said:
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
Click to expand...
Click to collapse
The switch in developer mode MUST be like this (picture), otherwise you cannot flash or root custom roms, custom kernels, etc.
I've read that sometimes you have to wait a few days for it to show up as unlocked finally. also you can't lock a brand new phone instantly, you've got use it a few days too.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
leokratos17 said:
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
Click to expand...
Click to collapse
rooting is pretty universal at the moment barring a couple OEM specifics. pretty much all Samsung phones root the same way.
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I have the same version, sm g 780g without the 5g (Brazilian version) can you help me to root?
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I also have this s20fe G780G 4g model I'm from Brazil, make a Tutorial help and...
The "OEM unlock" option I missed first but suddenly, after updates of the pre-installed apps and reboots, I got it.
I haven't tried to root as far and directly on front of my vacation.
Hit a wall trying to unlock BL, enabled in dev options and adb into DL mode but LONG PRESS VOL UP is not working! So there is no way to actually unlock BL!??!!?
WTF?
Hi all,
I'm hoping someone here can give me advice on how (or if!) I can recover from a bootloop after a failed Magisk update attempt, without losing the data on my tablet...
My Tab S8 was boot-looping constantly after I tried a Magisk update; trying the plugged-in-volume-up+volume-down trick from this thread gives me the screen with options for Continue, Device Unlock Mode, or Cancel. Before I go any further, I really want to make sure I don't do something that will accidentally wipe all my data!
I'm a long-time Android user and generally just competent enough to follow instructions (like the incredibly helpful howto guide in this forum!) and root my various phones and tablets, but tbh I don't have a full understanding of the various modes and what does / doesn't wipe the data on the device. I have a handful of documents on it that I would really like not to lose, so I don't want to screw this up by choosing options I don't fully understand... Any suggestions will be greatly appreciated!
(Or if someone with actual clue is willing to jump on a web meeting and help me recover it without losing data, I'll gladly compensate you for your time...)
Thank you in advance,
Lisa
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
roirraW edor ehT said:
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
Click to expand...
Click to collapse
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
lorenzin said:
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
Click to expand...
Click to collapse
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
roirraW edor ehT said:
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
Click to expand...
Click to collapse
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
lorenzin said:
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
Click to expand...
Click to collapse
You're welcome, glad that helped! I know I was nervous the first time I updated Magisk, but I did it at the same time I updated the firmware. That is, I would've had to update the Magisk app first, so that I could apply that updated Magisk to the new AP file.