Related
I just bought my new Galaxy SII for a penny. Great deal, and spectacular phone. Happens to be my first android phone as well (been waiting for one for years). The only problem i am having is when I put the phone in USB debugging the computer won't pick it up in explorer. If I enable USB mode I can copy files, but I cannot root (Trying the Xperia X10 Easy Rooting Toolkit, spits out crap about "cannot find the path specified", no matter what I do). Kies also seems to not work with the phone... I have tried both my Self Built Windows 7 HP 64 Bit Desktop and Windows 7 HP 32 Bit netbook and both have the same problem. Windows Devices and Printers reads the device but says that the driver has not been installed, when in fact it has...
Any and all help to resolve this problem would be greatly appreciated.
Haha thanks, got it working. Rooted and everything, sorta excited-kid in a candy store .
OK. So if you couldn't tell, I'm a complete newb with android, wanted it for forever, but circumstances didn't allow me to until now, and now I feel a little over my head. Sooo:
1.) Could you (or someone) maybe post links to some threads or sites that would be good to ease me into the world of android?
2.) With my Samsung Galaxy SII, if I am installing ROM's and taking them off, and installing new ones, what are the chances of bricking my device?
3.) Since I rooted it, I went over to CyanogenMod and downloaded the ZIP to the latest stable ROM. I then dropped it into my SD card, and went into a app I downloaded called ROM Manager. When I went to install from SD card, and it rebooted, it gave me an error and popped back out, seemed like I did it wrong. So how do I install ROM's (CM7 in particular).
4.) How would I go about removing that ROM after its been installed and im tired of it ?
I hate feeling like a newb, and would be very thankful for any help people would be willing to give to get me started!
Ok, two more questions .
1.) Is there a good app to backup my current apps before doing a wipe(I have a ton of them...)?
2.) I read that ROM's cannot include google apps, so how would I get them on? Would I download the APK and then sideload them?
Thanks again!
The ROMs that I downloaded were all in ZIP folders and I couldn't figure out what I should link to odin as ZIP folders aren't compatable to flash . And then my phone wont reboot into recovery or download mode (can't remember which one I need to be in for Odin). I tried with debugging on and off and it just boots right back into android. This is very frustrating, as I know I must be doing something wrong...
Thanks for all your help
Sent from my SAMSUNG-SGH-I777 using XDA App
bencozzy said:
Download mode-power phone off hold to buttons vol up and vol down power is still off and connect usb cable from computer. Download mode menu will pop up.
CWM or recovery-vol up + vol down plus power from phone being off until you see forst boot animation samsung.
Odin uses .tar or .tar.md5 files do lots of reading i think zedomax has a youtube video for rooting the i777 and how to get cwm.
Click to expand...
Click to collapse
thats the method i used for rooting and it worked flawlessly and was quick and easy
Wow you need to slow before you do something stupid. Take the time to read and just as important, if not more important, take the time to search the internet for your questions.
Learning what steps needed to do something to your phone is not the goal. Learning what you are doing and why, should be the goal, and learning how to do each step is a sidepoint that you learn as a by-product.
Most important thing to learn why and how to check for is to make sure what you're flashing does not contain bootloaders. If you mess with bootloaders and the smallest thing goes wrong, you end up owning an extremely expensive paper weight, i.e. a brick.
In general flashing what the majority flash here on xda is safe. But that's not a guarantee as any garbage can be uploaded. So read the entire thread. Some are long. If you can't be bothered to read the longer ones, at the minimum use the search tool to look for particular words to your question. Search before you post. It will be evident by what you ask that you've spent the time researching, and will attract a higher level of help.
I'm not trying to be mean or come down on you. You're already starting to do what's right by asking when you're not sure.
A NOTE TO YOU AND EVERY NOOB ON XDA:
One of the biggest reasons people's questions receive no response for a day or more, is because their question could be easily solved by using the search tool in xda or one google search.
In the wise words of tom cruise, "Help me, help you. Help me, help you!"
And yeah, he can fly.
Sent from my páhhōniē
Yea. I goofed and I flashed an international ROM onto it. I was able to find a unrooted stack tar to flash. I plan to do a lot of reading before I do this again . If anyone has any ideas on where to start that would be great.
And no problem, I understand as I am a heavy user of tomshardware forums. It frustrates me when people ask for advice a two second search would pull up.
Again thanks everyone! XDA is awesome!
Sent from my SAMSUNG-SGH-I777 using XDA App
I know it's been a couple days since you asked, so hopefully you've already found what you're looking for, but I always recommend people read all of creepncrawly's write ups. They cover near every question and are up to date on everything.
Sent from my páhhōniē
First off,i would like to apologize for being such an amateur.This is my first post on this forum,so don't get angry on me for breaking some rules (forgive me im new ,idk if i should post this here or somewhere else,don't worry i will be polite ).Anyway as the title says,im having a bit of a problem,or to be more precise a huge one.
So lately i was trying to root my phone,Huawei U8500 which was so buggy,so i decided to root it,install cwm and flash a new ROM.But the problem is i can't get it rooted.I've tried many methods from XDA but none of them worked.Z4 root loads until it displayed acquiring root access,and then the app crashes (closes itself).I've tried Framaroot,but it didn't work either.It said 'try another exploit',but the thing is it displayed me only one.I also tried poot.apk,but it also failed.Telling me '(-) can't get a handle on it:-1 Permission denied'.
(note that all the time my USB Debugging was enabled ! ) All of the apps are at latest version!
So after so many failed attempts with pc-less methods i've decided to try a PC one.The first method i used was Superoneclick,which didn't work.I thought that was because the phones model was not supported.All until a friend of mine told me that he rooted his phone using the same program (he has as well huawei u8500).Every time i try to root with superoneclick it is stuck at the second step(as in screenshot).Then i started googleing and google-ing,until i found a thread with a program called SRSroot,thinking it will safe me from this nightmare that is haunting me for days.But it failed again.The program told me 'ADB Device not found',which made me think about checking the drivers.I've installed the google usb drivers and SDK Manager with all drivers.But still the same happens.So i decided to see if my computer(later many others) recognize my device.After i typed in ADB 'adb devices' it showed me blank.Later i tried to do the same with my other phone and it displayed the device.Another thing i've noticed lately is my computer sees my device as a cd device in windows device manager.It happened with all computers i tried. I've tried it also at my friends(plural,which means more computers).I've tried it on Win7,win XP,and WIN8 and it is still displayed as cd drive.(which is not the case with other phones i've tested!)
I hope someone will read this and help me.I would also like to add, this is not my first time rooting,so i knew what i was doing.
Im so confused,idk what to do,developers pls HELP ME!!!
I will also post screenshots from all the things mentioned above.Hope this helps you figure out the problem
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
tried
Guynan said:
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
Click to expand...
Click to collapse
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Beatit123456 said:
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Click to expand...
Click to collapse
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
I did factory reset,i also did hard reset,but still nothing works
Guynan said:
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
Click to expand...
Click to collapse
Already did it,still the problem persists.Anyone here have any idea?
Beatit123456 said:
Already did it,still the problem persists.Anyone here have any idea?
Click to expand...
Click to collapse
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
pls read my question thoroughly
Guynan said:
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
Click to expand...
Click to collapse
Since im unable to root my phone,i can't flash a custom ROM.I'm trying to root but no success,pls some1 help????
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon
I bricked my SGPT12 Xperia Tablet S. After attempting to install the "signed-txs03_201-ota-130705006.zip" everything seemed to go downhill. The problem is I can't get into recovery/download mode at all. I've tried every possible combination (Pow+VolUp, Pow+VolDown, Pow+Volup+Voldown) to get into recovery, but nothing has worked. The Sony logo appears, then the "blue streak" picture shows up and loops forever.
The only good news is that after awhile, ADB starts working on the tablet. I have already tried "adb reboot recovery" and "adb reboot-bootloader" but each time it just restarts the tablet and shows the Sony logo and proceeds to the "blue streak" animation.
I've tried using the S.onyXT.S [UNBRICKER] tool, but that one keeps on failing when attempting to write the files to the SDcard.
Please, can anyone help me out?
Edit: Also, I forgot to mention. When I try to "su" using ADB, it gives me two errors: "Stopped (signal)" and "Segmentation fault". Since I can't regain root through terminal, I can't use most of the tools of A.I.O.
steven.smith said:
I bricked my SGPT12.....
Click to expand...
Click to collapse
here is cure
http://forum.xda-developers.com/showpost.php?p=55865211&postcount=15
urgas said:
here is cure
http://forum.xda-developers.com/showpost.php?p=55865211&postcount=15
Click to expand...
Click to collapse
As ive said in the other posts you have been littering the other forms withs correct your english your steps are un clear and confusing
Sent from my SGPT12 using XDA Free mobile app
@dex9mm
now you are so clever
why didn't help me when I need last week???
at least I try to help from mine ideas how I did it
urgas said:
@dex9mm
now you are so clever
why didn't help me when I need last week???
at least I try to help from mine ideas how I did it
Click to expand...
Click to collapse
Because the answers you need are already in the relevent threads you just have to look, this is why no one replied because with a small bit of research you find the answers your looking for
Reading is your friend on this fourm the tablets are about 4yrs and 3yrs old now at this stage and any questions are all ready answered a couple of times over so yea pretty much sick of repeating myself if you check my posts out ive been fairly active on this fourm and these threads in particluar also what you did has been suggested about a page or two back in this thread or the unbricker you did nothing that hasn't been done already again reading is your friend
By the way ive no problem with the fact that you posted what you did im only asking you tidy it up so if someone does need to follow it that its clear and understandable
Sent from my SGPT12 using XDA Free mobile app
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?