[Andrewski]

Hi guys,
I'm just about to root my armor 9 due to very dodgy camera software, I want to install gCam.
Sorry if my question is silly, but after rooting my phone with this method, will I lost all the data and I will need to setup the phone like new one from the box?

[X3non]

Hi guys,
I'm just about to root my armor 9 due to very dodgy camera software, I want to install gCam.
Sorry if my question is silly, but after rooting my phone with this method, will I lost all the data and I will need to setup the phone like new one from the box?

the process of unlocking bootloader will erase data from the phone, so yes you will loose all data and go through initial setup
also unless you have the exact same build number as the OP, you should follow the guide @ https://www.hovatek.com/forum/thread-21427.html

[wZjRiDFi2B3NQlMqrLbD]

Hi!

I've been following this guide, but after re-locking the bootloader my phone ends up in red-state.

Device: UleFone Armor 9E (Android 10)

My steps so far:

0.0 Get boot.img, scatter file, checksum generator (from ulefone), magisk.akp (from github), vbmeta.img, drivers, SP Tool (from here)
0.1 Install magisk on my phone and patch boot.img.
0.2 Enable developer options on my phone
0.3 Enable OEM unlocking and USB debugging on my phone.
0.4 Install drivers on my PC
0.5 Copy scatterfile, boot.img, vbmeta.img into checksum generator's folder and get checksum.ini.

1.0 Connect phone
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem unlock
> fastboot reboot

Phone boots in orange state.

2.0 Re-enable dev opts, (phone shows as already unlocked), USB debugging and turn off the phone.
2.1 Start SP Flashtool
2.2 Select scatter file
2.3 Check only vbmeta.img
2.4 Start download
2.5 Connect phone
2.6 Download completes successfully.
2.7
> fastboot devices
> fastboot reboot

Orange state.

2.8 Factory reset from phone

3. Repeat 2., except at 2.3 check only the patched boot.img

Still orange state.
Magisk app is installed.

4.0 Turn the phone on, enable dev opts and USB debugging, connect to PC
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem lock
> fastboot reboot

Red state - boot loop.

5.0 Hold power button until it turns off abruptly
5.1 Hold volume up until load some sort of boot selector menu.
5.2 Select fastboot mode with vol up button.
5.3 Vol down to boot selected mode
5.4
> fastboot devices
> fastboot oem unlock
> fastboot reboot

Orange state - everything else is working.

What am I doing wrong? How can I relock the bootloader?

Thanks in advance for your help!

[X3non]

...
What am I doing wrong? How can I relock the bootloader?

Thanks in advance for your help!

locking bootloader while having custom images on the device will only get you red state, if you must relock bootloader then you must return all partitions back to stock

[wZjRiDFi2B3NQlMqrLbD]

locking bootloader while having custom images on the device will only get you red state, if you must relock bootloader then you must return all partitions back to stock

Thank you X3non!

In case I'd do that should I proceed like this:

- Download original boot.img with SP Tool
> fastboot erase cache
> fastboot reboot
- Download original vbmeta.img with SP Tool
- Clear cache and reboot agian
- Then reboot into fastboot mode
> fastboot flashing lock
> fastboot reboot

Or can I restore both images at the same time? Also I did not clear the cache from fastboot last time but I feel like I should have?

Thanks again!

[X3non]

...
Or can I restore both images at the same time? Also I did not clear the cache from fastboot last time but I feel like I should have?

Thanks again!

you can restore both at the same time in fastboot, it should be something like this

Code:

fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flashing lock

if you wish to use sp fflash tool then tick both boot and vbmeta then flash

[wZjRiDFi2B3NQlMqrLbD]

Hi!

• Is it safe to update my phone while it's rooted this way? (I'd assume so, but better safe than sorry) Or should I unroot first, then apply OTA update and then reroot again?
• How can I edit my hosts file? It appears to be read only, no matter what.

Thanks!

[X3non]

• Is it safe to update my phone while it's rooted this way? (I'd assume so, but better safe than sorry) Or should I unroot first, then apply OTA update and then reroot again?

No, you can't
unroot then update

• How can I edit my hosts file? It appears to be read only, no matter what.

super partition on android 10 is -ro
use some other alternative such as magisk manager systemless host

[ssorgatem]

I have an OTA-updated Magisk-patched boot.img if anyone's interested.

[nonhocapito]

Hello, I am stuck. Please help!

I had previously successfully rooted my armor 9 following Hovatek instructions.

Phone got bricked after installing the wrong magisk module.

Decided to install an updated firmware from Ulefone (20210519).

Used the SP tool from Ulefone, all went well.

Then I moved on to root it, using the actual SP flash tool 5.2, but red state happened.

Here's what I did:

1. extracted vbmeta.img and boot.img from new firmware
   
2. patched boot.img with magisk 24.2 (ticked 'patch vbmeta' also, although not sure what that means)
   
3. flashed the old vbmeta.img from hovatek I had used with the previous rooting (figured it's just an empty file)
   
4. rebooted - red state - stuck in a loop
   
5. reinstalled vbmeta from firmware, all works okay
   
6. try flashing only patched boot.img
   
7. rebooted - red state - stuck in a loop!!
   
8. repeat step 5, try flashing both vbmeta and boot.img at the same time
   
9. rebooted - red state - stuck in a loop...
   

So, what is it? The new firmware cannot be rooted this way?
Am I doing anything wrong?