I did not have it in the same directory, but I specified the path relatively.
I will try another flash.
I did not have it in the same directory, but I specified the path relatively.
I will try another flash.
I just tried to reflash, TWICE, using MinimalADB etc. It LOOKED successful, but then my desktop was still there after reboot. It did not perform a factory reset, and more importantly, Magisk still canât be installed for root.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
201909T1000735 fastbootC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot teracube_patched_boot_sw1.img
target reported max download size of 134217728 bytes
sending âbootâ (9469 KB)âŚ
OKAY [ 0.437s]
writing âbootââŚ
OKAY [ 0.139s]
finished. total time: 0.581sC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebootingâŚfinished. total time: 0.007s
C :\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
201909T1000735 fastbootC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot teracube_patched_boot_sw1.img
target reported max download size of 134217728 bytes
sending âbootâ (9469 KB)âŚ
OKAY [ 0.438s]
writing âbootââŚ
OKAY [ 0.136s]
finished. total time: 0.579sC:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebootingâŚfinished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
If you know it flashed correctly (see my cmd window above),
Did you click MagiskManager on GitHub?
that is where I got it, but I donât think I got that message upon install.
uninstall, reinstall, nothing about special access
funny, the first TWO times that I reflashed did a reset, but not now
Sorry, thatâs about all I can think of. I did 4 and they all went real smoothly. Hopefully someone more knowledgeable will come along and help. Later today or tomorrow I will try to get TeraCubeâs unto XDAâs forums. They have a lot of very talented folks who could probably help.
that will be great!
I am doing another factory reset and seeing if I can root it.
apparently a fresh start, and SKIP everything, and flash and install Magisk Manager (which then installed Magisk) was the trick!!!
I note also that after this flash, the Magisk Manager safety check says âctcProfile trueâ instead of false
seems to be rooted!! Now to install everything else again
See if you can get your guide linked to by XDA dev mods: https://www.xda-developers.com/root/#others
Great idea. I donât see a way to report a new device there. Anyone know how to get Teracube on that page?
Update : Iâve sent a PM to the user mentioned in that article.
I seem to have lost root with the beta update.
Would I normally need to re-root the phone after updates?
Is re-flashing the bootloader necessary?
Bootloader stays unlocked if you had unlocked earlier.
We will provide a new patched boot image that will need to be flashed with the above sequence.
yes I still get the boot warning as if the bootloader is unlocked.
Looking forward to the new patched boot!
Hopefully the boot img wonât need to be changed very often in updates.
Can we extract boot.img from the update zip, and patch the img file with Magisk via Magisk Manager (Install Magisk>Install>âSelect and Patch a Fileâ), and flash that img to regain root?
Sure - that should work.
I have now tried using Magisk Manager to patch, and it boots, and Magisk Manager report both as installed.
However Titanium Backup now closes upon open every time.
not sure what is happening
I think it would be a good idea for someone to make a video on how to root the device.
I seem to have root, but it causes an immediate crash of Titanium Backup, without it asking for permission to use SU even
Another root check program ask for access to SU and reported phone as rooted though.
I have a few questions regarding boot images, unlocked boot loader, and patched boot files:
The unlocked boot loader lets us flash a new patched boot img, right?
One is (I am) able to patch their own boot.img extracted from the recent update
the update IS ALSO ABLE to flash everyoneâs phone with Teracube updated boot.img, including still boot-locked phones
Q: Is unlocking the bootloader only needed because the patched img files are not SIGNED by Teracube?
Q: Could signed patched img files be used to make it harder for programs to detect an unlocked/rooted system? (and remove the need for an unlocked bootloader?)
See my respons inline: