Related
Updated 14-Dec-2011: I'm posting an updated recovery, "20111213" (I compiled it yesterday) below. I'm not going to bother cleaning up this entire post with updated information, as I'm just too tired right now. Please read the post, then read the "Changes" section towards the bottom... then download the update (if you want.) Probably this weekend some time, I'm going to be consolidating the posts for all 3 models of this device into a single post with three download links. (I'm trying to get them all in sync with each other.)
**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your T869 (tmobile galaxy tab 7 plus) tablet.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung/TMobile SGH-T869. If you have a different model, don't waste your time downloading it. It won't work. I do NOT have this tablet to test with, and a special thanks to shadejinx for doing the testing. That being said, he tells me that the backup and restore both work okay. However, there is an issue with rebooting back into recovery (see Post Installation notes and Issues.) If you want to try this, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
So, once it knows that it's working on the proper type of tablet, this package will make a backup copy of your existing recovery image, and place it in your internal storage with the name starting with "recovery_backup" and ending with the version of the recovery package you installed. For example, recovery_backup_20111206.img.
Next, a new version of the clockwork mod recovery is installed.
Then, the script will look for and delete any existing clockworkMod recovery backups that you have sitting around. Why? Because I'm re-using the script I wrote for the GT-P6210 tab... read that thread if it matters. Once my CWM-based recovery is installed, overwriting it with the same or newer versions won't delete the backups anymore.
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "t869_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.)
3. Select the file you placed on your storage card (starts with "t869_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/showpost.php?p=20074586&postcount=14
Update: According to shadejinx, this doesn't work for the SGH-T869. However, there's an alternative way, but you must have adb installed: Connect your tablet to the PC you have adb installed on, and power down the tablet. (A full power off - not just standby.) You'll notice that your tablet really isn't fully powered down, as there's a battery icon smack in the middle of the screen. It's in a "low power mode", and "adb" can still talk to it. Use adb to send the following command: "adb reboot recovery". You'll end up in recovery.
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "t689_factory_recovery.img"
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20111213:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
Here's the link for the recovery/root .zip (for the tmobile SGH-689)
version 20111213: http://www.mediafire.com/download.php?oro674o2881kw54
old versions:
version 20111206: http://www.mediafire.com/download.php?07ucaimq8qs6q05
Take care
Gary
uploaded and available. (message is to mark the thread as unread and as a place-holder for future notes.)
Your donation note is cool, man.
Just flashed update. It works fine I have root everything works the same installed superuser from market. Great work now all we need is a nice ICS ROM and voodoo
Sent from my SGH-T869 using XDA App
I wonder if tmobile would let me borrow one of these for a couple days so I can test some updates to the recovery.
"Hello, welcome to T-Mobile. Can I help you?"
"Yes, I'd like to quietly sit over there and attach my notebook computer to one of your demo tablets for about an hour to test voiding the warranty by flashing in low-level tools that, among other things, will allow anyone to bypass all the silly locks you people put on these devices. Oh, and I'm not a tmobile customer (and probably never will be.) Okay?"
heh
CSR: sure, go right ahead. Could you root it and install a custom ROM while your at it.. we've been getting tired of looking at this same old spoon fed sammy touchwiz and samsung apps nobody uses. Overclock the snot out of it.
just kidding, back on topic..
@garyd9 I'll get the updated recovery stuff tested tonight.
Updated and a new link posted in the OP.
Thanks to shadejinx for testing.
Changes for 20111213:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
garyd9 did this work blind and it worked perfectly the first time... I am very impressed. Anyone who reads this needs hit the thanks button on the OP.
garyd9 said:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
Click to expand...
Click to collapse
Where have you seen this?
rxxt said:
Where have you seen this?
Click to expand...
Click to collapse
I used the magic "search" function in XDA. It's a really cool feature of the site that lets you press a button, type a few letters, and find things.
Even if you aren't capable of using that function (and quite a few people are search-impaired for some reason), or if you might be searching for the incorrect term (I've done that myself a few times) you can always search manually. That involves opening threads and reading through them (not just the first post!)
I know that if I were looking for a firmware image, the DEV subforum thread marked with "Official FIRMWARES" would catch my attention, and I'm sure I'd find something useful if I spent a minute scanning through the thread that's less than 30 posts long. (That's a hint, by the way. I absolutely refuse to provide a direct link.)
Good hunting!
Gary
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
(first the original reply)
rxxt said:
Wow, is it really true .. You have really savedmy day, damn well you tell me about the search option, otherwise I never havefound it, I can not thank you enough, what would we do without people likeyou..
Click to expand...
Click to collapse
Alas, 'tis true that some folk could never get along without those of us who point out the obvious.
(and now the current edited version)
rxxt said:
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
Click to expand...
Click to collapse
Thank you for making my point.
edit: Please don't take my sarcasm personally. It's how I keep sane.
Take care
Gary
With the release of ICS, and seeing that others have taken over carrying the torch for updated and more modern versions of CWM Recovery, I'm no longer going to be supporting this release.
I'll leave the thread intact, but request that it be locked.
Oh, and I am still around, but I'm giving my Galaxy Tab 7.0 Plus to my wife. The stock firmware is actually very good for her, and she doesn't demand the amount of control over a tablet that I want.
Take care
Gary
Okay, have found a lot of threads similar to this, but with key differences that are making the answers not-terribly-helpful in my particular circumstances. Not a comment on the answers, but enough that I feel the need to ask my question specifically.
I am trying to gain more control over my MyTouch 4g Slide (aka Doubleshot), obviously on T-Mobile.
It is running Android 2.3.4, and has hboot 1.45.0013. I have wiped it a few times in the process of fuxing with it, so right now I'm not worried about losing anything other than basic function (i.e., bricking it is still bad).
I have tried the zergrush exploit (it's been closed),
have managed to unlock the bootloader using the HTC unlock tool,
and have managed to flash the appropriate Clockworkmod recovery and get the blue menu to come up.
My overall goal isn't to do any major overhauls- I want to be able to allow some apps to turn my GPS on and off, clean out some bloatware, and put some new ringtones into the same folder as the stock ones. My understanding is that temporary root access is enough to do these things- go in and clean up, change some permissions on apps, then go back to being a normal user, just like with a well-managed Linux computer.
I just can't seem to get the next step to work.
My understanding is that I now somehow use Clockworkmod to install Superuser from the .zip archive. The options I get in the recovery screen are:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
My impression is that I should be using "install zip from sdcard" to install Superuser, but when I select that, the menu just disappears, and I am left looking at the logo, with no further options. I have seen it implied that there should be choices about which zip to install- those never come up.
What am I missing? My google-fu is failing me in trying to find instructions or guides for this particular combination of limitations and progress.
EDIT TO ADD: Ah- found part of my problem... the recovery menu uses the camera button, not the power button. Still somewhat at a loss to see what's next. Installing from the SD card fails. Info in a second post.
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
I am seeing in other places that HBOOT 1.45.0013 can't be rooted. I've been trying for about 9 hours to do this. . .no luck, even with a variety of methods.
bummer.
I'm in the same boat as the both of you. Spent the last two hours and enough tabs in my browser that my music player was skipping when switching between them, and my machine is nothing to be scoffed at!
There just doesn't seem to be enough clear information about how to root this device, and with only 7 pages of development threads, it's gonna be hard to be told to search!
In recovery you use the trackpad to navigate, and select....also, why not just flash a pre rooted stock rom? Follow the directions in this thread, it will work with any rom, not just ICS roms. I used the instructions in this thread to install Bulletproof on my Bf's phone which was an insurance replacement, so it had the same hboot that you guys have, and S-on. It worked flawlessly, I am not sure why so many people are having such a hard time, because it worked the first time perfectly for me.
http://forum.xda-developers.com/showthread.php?t=1508556
Edit: Which recovery are you using?
Woot! Oops...
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
If anyone has a Nandroid backup or copy of the dead-standard out-of-the-box ROM for this phone, please let me know. All I am finding is modified versions. Can't find the base that they were made from, and even the most basic version says it requires S-OFF to install. :headdesk:
Do you specifically need a nandroid backup, or would a flashable ZIP do? Pointers to the latter are available.
Flashable zip would actually be preferable, and pointers would be very much appreciated. I know they have to be out there somewhere, I'm just not finding the right search terms to locate them among all the modified versions.
Look at this post in the developer reference thread: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7
(There's lots of stuff listed there, but look for the 400 MB+ images.)
NOTE: Some ZIP tools get confused by these signed ZIPs, so they might seem corrupt. Check the MD5s to see that you got a good download. 7Zip seems to deal with them OK if you want to look inside.
I have personally flashed the 1.28 and 1.55 ZIPs without incident, but I did check the MD5s.
Well, I was not able to restore the ROMS from the links wjcarpenter linked- everything worked fine, as far as I can tell, but the phone said the "updates" were older than what was originally installed, so the installation was aborted. Not sure how to fix/handle that.
For the moment, I have one of the cleaned-up ROMs that is very similar to stock, but I would really rather it not be obvious that I rooted the phone the second you start it up (the one I found has changed the startup animations), so I will keep looking.
If it's going to be obvious that I changed the ROM, I guess I might as well start looking for the best custom ROM... any suggestions as to which is the most stable?
Firefairy said:
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
Click to expand...
Click to collapse
Just think of it as a big learning experience! The first time I rooted a phone, I messed it up so much I had to keep flashing back to stock and rerooting at least 3 or 4 times. Thankfully I had a phone that was virtually unbrickable. It was a good learning experience though, and I now feel comfortable rooting and flashing on several different devices.
Firefairy said:
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
Click to expand...
Click to collapse
download from androidsu and either save it directly to the ROOT of your sdcard, or copy and paste to the root of your sd card. i always get that same error when i install superuser from a folder in my sd card.
Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?
Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly
Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...
Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!
I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.
Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?
Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one
pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.
exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome
Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding​ it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
I downloaded the very latest Magisk from git ( https://github.com/kantjer/MagiskFiles ) version 13.3-170812-zip & then removed the Magisk App-booted into recovery-flashed the Remove-Magisk zip-cleared cache-rebooted into recovery-flashed the new version & NOW I have Magisk working properly.
I thought I'd offer a newbie perspective on the big brother BLOX2 (Life One X2 4 gigs /64 gigs).
I was planning to use BLOX2 AutoRoot, but I couldn't make it work. It got as far as unlocking the bootloader, then just sat there doing nothing. Same thing for BLOX2 ToolKit. (I think both problems were caused by my computer, not the software.) So then I decided to do the unlock via ADB, then Flash TWRP f=and BLOX2 Core from an SD Card.
My laptop (Lenovo ideapad FLEX4 running Win 10 Home 64 bit) does not like to recognize my phone. When I open a command prompt window and type in 'ADB devices' (ENTER) the computer pops up a notice telling me "the last USB device you connected to this computer malfunctioned and Windows does not recognize it." ADB returns an ambiguous statement that "a list of devices is attached" (to what, I have no idea). NONETHELESS, when I got frustrated and ran "fastboot oem unlock" it unlocked my boot loader in less than 2 seconds. Go figure.
I had to install TWRP a couple-three times as well before it "took" and stayed even after a reboot to system. I remember reading in a guide to rooting the Blu R1HD (if memory serves) that one ought to reboot into recovery after each step in order to make sure that the original image does not overwrite the new one. Don't know if this is related, but I followed that dicta from that point on. Lucky for me, TWRP installed right-side-up.
As for installing BLOX2 Core, the hardest part of this was putting the file onto an SD card in such a way that TWRP would recognize it. After that I popped it into the phone, booted up, opened TWRP. I found the BLOX2 Core file, flashed it and sat back to watch the magic happen. Line upon line upon line of pretty little code bits rolling by -- and all of it in black! No angry red lines to be found anywhere! As someone who is so far much better at bricking phones than modding them, this was truly a lovely site.
After this, there was really nothing left for me to do but BACKUP EVERYTHING! First I did a TWRP backup. (I have not been able to convince Nandroid itself to function on demand. It works fine on a scheduled basis, but when I try to run it directly it runs for three seconds, announces it is finished, and presents me with a non-file.) Then I installed one of my favorite apps: Titanium Backup. I setup TB to backup all system data and user apps on a schedule, and then ran the first one directly.
In all the excitement, I had forgotten all about Magisk, but a few hours later I noticed an icon labeled "Magisk." I clicked on it just to see if it was actually installed or just sitting there to install if I wanted to. When I saw that it was indeed the installer I just shut it down and left it alone. I strongly suspect that it was SU-Magisk failing to play nice that led to my bricking my first BLOX2, so I wanted to research how to get rid of it safely. Well, before I could get anywhere on that, the system on my BLOX2 started acting weird in familiar ways. Apps that I had not opened started 'closing' suddenly -- each one flashing a popup at the bottom of the screen that immobilized the touch screen until it was dismissed. When my first BLOX2 started doing this I thought I must have gone overboard with one of the longer-battery-life (Xposed) modules. So I frantically started zeroing them out to stock. This didn't help and the slippery slope had been crossed.
With my second BLOX2 I was a bit better prepared. I immediately uninstalled MAGISK and frantically ran every utility I could think of to be sure that there were no bits and pieces left to irritate SU into killing my phone. Just to be on the safe side I reflashed the entire BLOX2 Core zip, then backed up the result with both Nandroid and TB. This was a couple days ago, and my phone seems content.
I know that the BLOX2 Core I am running is not technically a "custom" ROM, but it still runs noticeably more smoothly than the original. Right now Settings shows 3.6GB total Ram, with 2.1GB free, which means that it is using about 1.5GB with screen on but only background stuff running.
As to my laptop's refusal to see my phone, I think the problem is in my PC. I have had nothing but problems with SP Flash, ADB, and all the various Qualcom-related tools. I have tried QFIL, SN-Write, WRTool, and the like. Even MTK DroidTools gives a message that there is nothing connected to the computer, then freezes. Go figure.
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
debianmain1 said:
One thing I've learned is that an OTG cable is a real nice thing to have & TWRP will recognize it with a simple click in storage. Put your downloads on a Stick--connect it to an OTG cable, plug it into the phone & you are set.
Click to expand...
Click to collapse
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Augieboo said:
DOH!!!!!!
This little thing is so cool. Right now I am doing a Nandroid backup (via TWRP) and storing the backup on my USB drive.
I wondered what that funny little cable was.... It came with my BLU VIVO 5R, which I probably could have saved from the brick-yard if I had known what that little cable could let me do.
Thanks!
Click to expand...
Click to collapse
No prob...glad the info helps.
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
debianmain1 said:
So, I think that it's a good time to start another thread about the One X2. I own an X2 Mini & am really liking it.
The first thing I can say is to BACKUP your install several times until you get root. MAKE SURE to include your boot.img as part of the backup.
1. Going thru unlocking the bootloader (easy), Installing TWRP (moderate) & Rooting (very frustrating) was an interesting experience. Unlocking the bootloader was by far the easiest I have ever done on any phone. Just enable developer options & tic the switch....That being said---the rest of the process was a PITA.
2. Installing TWRP was easy/moderate--having to do it twice & finding that the tool I used installed an early version that put everything upside-down was "interesting" but not really too difficult (I'm a linux guy, so a trip to the terminal & ADB fixed that without too much trouble).
3. Then came the Magisk install--that took a couple of days & quite a bit of help from forum members to get "sort-of" ironed out. There is protection on the boot/kernel that takes a bit of work to get in the right order to get root. With the Stock ROM you need to either run the AutoRoot script from BLOX2.com ( http://blox2.com/how-to-root-the-blu-life-one-x2/ ) or if you are terminal-savvy there are manual instructions also. I'm NOT a Windows guy, but tried the auto route first......That in retrospect was not the best way for the X2 Mini---the version of TWRP that it installs is early & upside-down so controls do not work. I got past that & found thru trial & error I needed to install Magisk 12.0 (via TWRP zip install) & MagiskManager 4.33 (with a APK Manager after reboot) FIRST. (as Ieatgravity pointed out...)
4. After you get to root this way you can just stay there (depends if you need SafetyNet or not) or get the more modern version of Magisk. As AlienTeck points out, you MUST install zips inside of TWRP due to the way the boot/kernel protection works. Installing inside of TWRP works outside of the booted system & gets the install done. You can't at present install inside of a running system without a reboot as soon as the kernel detects a system-wide change. This would prevent several "on-the-fly" root modifiers from working. I would hope someone will see the need to create a new boot.img & Kernel to side-step these issues.
5. There is only one custom ROM available right now---DRAX, & with my current experience, it seems to work MUCH better than the Stock ROM. It changes the spacing on-screen (for the better) & is debloated....definitely is faster/smoother than Stock.
Well---I'm not the FINAL authority on the X2/X2/Mini...there are several great people on the forum...I did this just to give a brief info list for people to look at without TOO much searching. You will find all the answers in the main thread----it just takes a bit of digging to get to them.
My hope is that this thread starts a "how-to" thread for people to refer to...And if I've miss-stated any info I've posted above, please feel free to correct me.
Click to expand...
Click to collapse
vampirefo said:
Does the mini use the same twrp as full phone?
I ordered a BLU Life ONE X2 Mini - 5.0" Unlocked Smartphone -4G LTE - 64GB + 4GB RAM -Grey.
So just googling for root and so far, won't have phone til next week, so no rush.
Thanks for any information.
Click to expand...
Click to collapse
Update
I see they use different twrps,.
vampirefo said:
Update
I see they use different twrps,.
Click to expand...
Click to collapse
You can get the Mini one on BLOX2.com
Just for anyone that can't find the TWRP for the Mini: https://drive.google.com/open?id=0B6h1RP64aWh0a1UyaUc2ZlNzQ1E
You guys are using very old roms join Yureka Black and tinno p7210 common group for new roms and discussions - http://t.me/yuyurekablack
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
ewingr said:
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
Click to expand...
Click to collapse
Rooting is 'full', just that technology (Android 9/10) is changing.
For AdAway app you must enable Systemless hosts (option/module in Magisk Manager), for modules Magisc automatically handles symlinking to the read-only System
So, even from root explorer (sugested MiXPlorer), you see as if AdAway wrote directly to the file system/etc/hosts, or that BusyBox tools are applied directly to system/xbin
Since EMUI 8, Huawei replaced Boot with Ramdisk, and since EMUI 9.1 Ramdisk is also read-only, hence Magisk must patch to Recovery instead
Because of that, you cannot have TWRP if you go for root (don't consider an alternative solution to flash TWRP over erecovery). But formally speaking, TWRP is not part of root (on the old systems, you could have TWRP without root, vice versa, or both). Even with TWRP, TWRP could not change read-only System, and it cannot see dynamical linking active only when system is running (Magisk running). Plus, because of new encryption since EMUI 8, TWRP cannot handle Internal storage (don't consider alternative solution to completely wipe Internal storage and format it without encryption)
All together, from system, systemless works fully seemlessly (as 'full' root). Just you don't use TWRP
To root:
- Install Huawei UpdateExtractor (PC), download update.zip for your 9.1.0.252 c432 from FirmwareFinder, unzip and extract Recovery_Ramdisk.img
- Copy Recovery_Ramdisk.img to the phone, install Magisk Manager, choose Install and then Patch a file, check all three options Preserve AVB, Preserve encryption, Recovery file
- Copy patched_boot.img (rename to patched_recovery.img or so) to PC and flash from Fastboot to Recovery (similar like flashing TWRP) - of course, Bootloader must be unlocked (you have code) and OEM/FRP must be unlocked
- You must boot to system through recovery (because Magisk was patched to recovery), if Magisk Manager shows rooted, you are done
To unroot:
- In case of bootloop or anything: just flash stock Recovery_Ramdisk.img back to Recovery, and you are back to stock
- Regular unrooting: take Uninstall from Magisk (and later, optionally, flash stock recovery_ramdisk.img)
- In case of OTA: unroot (regularly, as above), accept OTA, root again
Btw, you could update your sig now (no more EMUI 5)
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
ewingr said:
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
Click to expand...
Click to collapse
Font size can be changed in Settings /Display
I never changed system fonts but there are Magisk modules to do so, search by Google, eg:
https://forum.xda-developers.com/apps/magisk/avfonts-march-6-t3760827
https://forum.xda-developers.com/apps/magisk/module-midnightcore-one-midnight-modules-t3762758
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
ewingr said:
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
Click to expand...
Click to collapse
Look for MHA-LGRP2-OVS - see screenshots.
You can also find through Web:
https://pro-teammt.ru/firmware-database/?firmware_model=MHA-LGRP2-OVS
Btw, there are several b252 packages there, all the same size (and probably all ok) but I was told that package number #279403
is the one that is distributed by OTA
Thanks.
I saw the MHA-LGRP2-OVS ones, but I thought I needed to find one with identical name to the one I'm on.
This stuff doesn't make much sense...at least not logical. Only experience and/or help makes it possible to get it done.
Appreciate y our help.
Well, I don't know what's going on. I downloaded the FW from the link you provided, as well as from FF on the phone.
The one from the phone, once I transferred it to the PC, wouldn't extract anything from the zip.
The one from the link extracted, but when I loaded the Update.app into Update EXtractor, I got this error:
So, I then downloaded a different version from the web site (282444), and got this in Update Extracter:
Maybe it's warning me to not root:silly:
I am going through the thread about the extracter tool now to see if I find anything helpful. First blush looks like I'd need to make a profile file that is outside the limits of my knowledge. We'll see.
I found a post saying:
Try with crc check off (in settings) for extracting
Click to expand...
Click to collapse
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
ewingr said:
I found a post saying:
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
Click to expand...
Click to collapse
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
zgfg said:
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
Click to expand...
Click to collapse
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
WARNING:
If your phone runs Android 8 or later with latest security patch - then this service won't work!
Click to expand...
Click to collapse
I'm on Android 9 with security patch 3.
ewingr said:
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
I'm on Android 9 with security patch 3.
Click to expand...
Click to collapse
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
zgfg said:
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
Click to expand...
Click to collapse
OMG, yes, you have. BUT the site that provided the method to do it says it won't, per the quote I put in my post. I'm inclined to believe you, you have been a very good source and patient. But, I was wondering why would they say it won't work? That is their exact words, about their tool.
That being said, I guess as that I had the code before upgrading to 9, then just following the fastboot commands with that code will work, and in fact doesn't even use their tool. . So, I'll continue with that then. The information out here can sure be confusing.
Thanks...
[EDIT]
I figured that likely it would be the ramdisk.img file, and through Google search I found a thread that verified that. So, I'm continuing on.
Thanks...
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
56_kruiser said:
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
Click to expand...
Click to collapse
So, are you the same as previously, @ewingr?
If so, have you successfully unlocked Bootloader with that old code
OpenKirin instruct to patch Ramdisk and that was correct for EMUI 8.
(If) yu are on EMUI 9.1, hence you need to patch and flash Recovery Ramdisk
When patching from Magisk Manager (MM), you have to check all three options: Preserve AVB 2.0 DM-Verity, Preserve Force Encryption and Recovery Mode.
Does MM report any error while flashing or success/ok?
You can rename patched_boot.img to like patched_recovery.img, doesn't matter, but you must flash it to Recovery (like flashing TWRP to Recovery).
Right after flashing, boot by key combo to that patched Recovery (like booting to TWRP by key combo, after flashing TWRP).
Of course, you will not flash/use TWRP here
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
fastboot flash ramdisk Patched_RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
I got this response:
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.721s]
writing 'ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.757s
Click to expand...
Click to collapse
56_kruiser said:
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
I got this response:
Click to expand...
Click to collapse
Again, if you are on EMUI 9.1, forget Open Kirin instructions (for EMUI 8).
You must patch Recovery Ramdisk and flash to Recovery Ramdisk, so:
fastboot flash recovery_ramdisk Patched_RECOVERY_RAMDIS.img
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
56_kruiser said:
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
Click to expand...
Click to collapse
Magisk by default means you have root. You can install and disable modules in Magisk Manager, but you cannot disable root - for that you must Unistall Magisk (an option in Magisk Manager).
In MM you have a tab/menu showing all apps that were granted root - you can suspend or even revoke to some
Check in Settings/About, does it show you have b252 or b252 Patch03. I think that it thinks you are on b252 without Patch03, and it wants to install that patch.
But I don't know would you loose Magisk if you accept (or even get bootloop), so better disable authomatic OTA updates for now.
Believe me, similar 'Important' patches were receiving users (starting at the same time) with various Huawei phones running EMUI 9.1, discussing on XDA what it was, but there was never an answer, nobody detected any change for something better or worse.
So you don't loose anything if About showing b252 without Patch03
To boot to Magisk you must boot with Vol+ pressed - with USB discinnected.
If connected by USB to charger or PC, booting with Vol+ pressed will boot to eRecovery.
Normal booting (without Vol+ pressed) boots to the system (Android), but with Magisk disabled (MM will say that Magisk is not installed), so no root.
Reboot again with Vol+ and you are again rooted
If it ever comes an OTA for higher than b252, you will have to Uninstall Magisk from Magisk Manager and then accept OTA (and root by yhe same procedure one more time, with recovery_ramdisk.img from the new firmware).
Anomoly with root...
Root is working, albeit with anomalies.
If I boot w/o going through the recovery/Magisk, the phone boots up w/o root, and all works fine. When I go through recovery/Magisk, it comes up rooted, but with the following untenable anomalies: Dialer/Phone does not load; Contacts are not available; As result calls I receive do not show who is calling, and I cannot make calls out.
Given that changing fonts do not give me the fix I was chasing (see this thread), I may, unroot. But given that I can boot up w/o root and it works fine, I'll hold off un-rooting for a bit.