Database Info

mt7-09 b331 firmware root?

Does anybody knows how to root my mate with b331 firmware? Where can i find a guide step by step to root my mate to put out the folder to increase the volume which is very low.

Unlock bootloader then flash twrp for lp and then flash supersu.zip
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka

chudy_85 said:
Unlock bootloader then flash twrp for lp and then flash supersu.zip
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
I unlocked the bootloader but i cant flash twrp.where can i find the files twrp and supersu? could you pls tell me step by step how to flash twrp?

depeche3 said:
I unlocked the bootloader but i cant flash twrp.where can i find the files twrp and supersu? could you pls tell me step by step how to flash twrp?
Click to expand...
Click to collapse
Her you have twrp
http://forum.xda-developers.com/showthread.php?p=64127308
And her you have supersu.zip for twrp
https://download.chainfire.eu/696/supersu/
Do It that.
Enable debugging USB in setting
Then use twrp to install
When it's install copy supersu.zip to sdcard
Go to twrp and find supersu.zip and flash
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka

Mi 4c bootlogo and fastboot changing

I discovered something interesting.
Bootlogos from oneplus one works for our mi4c.
You can use this tool to make your own:
http://forum.xda-developers.com/oneplus-one/themes-apps/mod-customize-ones-bootlogo-t2857153
To flash it :
splash logo:
Code:
fastboot flash bk2 logo.bin
fastboot logo :
Code:
fastboot flash logo logo.bin
For both displayed is opo splash logo, so you must make separate files for splash and fastboot logo.
Enjoy !
Also feel free to share your logos.
Mi4c original logos attached below

nice

So we can get rid of the Mi logo? Would be nice to have Android logo like most phones I.e. Samsung s6&7

Potentially yes, we only need PNG of it.
Wysłane z mojego Mi-4c przy użyciu Tapatalka

How safe is it to flash this?

I tested it, and it worked. Done in 4 seconds.

can I flash by phone only?
no pc available for right now...

Try dd via terminal or make for flashable zip
Wysłane z mojego Mi-4c przy użyciu Tapatalka

AndropaX said:
Try dd via terminal or make for flashable zip
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Click to expand...
Click to collapse
hi @AndropaX
me as a noob, i'm afraid it can bricked my phone...
as the OP http://forum.xda-developers.com/oneplus-one/themes-apps/mod-customize-ones-bootlogo-t2857153
said, don't used out of dated
and it confusing me
can you please explain in detail step by step how to change bootlogo
thank you
ps. i have flashed your google bootlogo in RR Rom, and it works :good:
but, i'm can't make my own :crying::crying:

This apply only for oneplus one, where this causes bricks on lollipop bootloader, we have mi4c, so don't worry...
Wysłane z mojego Mi-4c przy użyciu Tapatalka

@AndropaX
thanka you mate, its works like a charm
:good:

@AndropaX is there a way to flash the boot logo only and not fastboot logo? Because when using the tool, it seems it combines both into one .bin file?
I've attached the image I want to use

This tool is made for oneplus one, which has splash and fastboot logo in one partiton, mi4c has separate partitions for it. So simple ignore fastboot.png
#GETRESURRECTED

Just made this and added the powered by android to make it like other phones. Added a preview and the boot if anyone wants to try it

Nougat bootloader
Can I flash in on nougat bootloader

any idea why am I getting error something about max. storage when trying to flash logo and end up with no success? device is seen properly through fastboot devices, it used to work in past, not sure what is issue now
running official LOS 14.1 with newest firmware for it
EDIT: never mind, on the other try it worked fine, but still would prefer to know how to make flashable ZIP so I don't have to use PC next time

AndropaX said:
This tool is made for oneplus one, which has splash and fastboot logo in one partiton, mi4c has separate partitions for it. So simple ignore fastboot.png
#GETRESURRECTED
Click to expand...
Click to collapse
Does this tool work on nougat? And how do I create my own bootlogo?

There's an internal problem with your device

Hi Community!
Can someone help me to get rid of this message? It came up after I've upgraded to 5.1.9 with OTA update. Then I've re-rooted device according to second pinned thread and flashed latest Magisk. And after restart I've got this message.
I've tried to flash patched boot.img from forum thread called "Root OOS 5.1.9 patched boot. img" but the message is still there. Everything seems to work fine, except this annoying message. How to get rid of it?
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

TheFaithfulOne said:
Hi Community!
Can someone help me to get rid of this message? It came up after I've upgraded to 5.1.9 with OTA update. Then I've re-rooted device according to second pinned thread and flashed latest Magisk. And after restart I've got this message.
I've tried to flash patched boot.img from forum thread called "Root OOS 5.1.9 patched boot. img" but the message is still there. Everything seems to work fine, except this annoying message. How to get rid of it?
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
Click to expand...
Click to collapse
Try magisk 16.3 or higher.

mikex8593 said:
Try magisk 16.3 or higher.
Click to expand...
Click to collapse
Man, I already have latest 16.7.... any other idea?
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

16.6 and 16.7 are known to cause the issue.
You MUST use 16.0 to 16.4 from TWRP and only upgrade Magisk inside Magisk Manager.

Ramihyn said:
16.6 and 16.7 are known to cause the issue.
You MUST use 16.0 to 16.4 from TWRP and only upgrade Magisk inside Magisk Manager.
Click to expand...
Click to collapse
Should I uninstall current Magisk and install 16.4 now? I tried flashing 16.4 over 16.7 with no luck...
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

TheFaithfulOne said:
Should I uninstall current Magisk and install 16.4 now? I tried flashing 16.4 over 16.7 with no luck...
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
Click to expand...
Click to collapse
YES! I get that error message everytime I tried to flash something other than 16.4. Uninstall Magisk, reboot. Then go back to recovery and flash Magisk 16.4 and reboot. Just let the Magisk Manager handle updates to Magisk from there on out. It seems to be the only way to prevent that error message

In my experience this also happens, when you run Magisk with stock kernel.
Therefore you can also just use a custom kernel and the problem should be fixed too, if you actually want to use v16.7.

Kalleculated said:
In my experience this also happens, when you run Magisk with stock kernel.
Therefore you can also just use a custom kernel and the problem should be fixed too, if you actually want to use v16.7.
Click to expand...
Click to collapse
Which custom kernel do you prefer?
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

Kalleculated said:
In my experience this also happens, when you run Magisk with stock kernel.
Therefore you can also just use a custom kernel and the problem should be fixed too, if you actually want to use v16.7.
Click to expand...
Click to collapse
Stock kernel works just fine for me. Just flash Magisk 16.4 and let Magisk update on it's own

Have a look at the official Magisk Thread here.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
If you flash masgik with TRWP you don't have the "Preserve AVB 2.0/dm-verity" checkbox and this causes your issue most probably.
Try the above mentioned methode and it should be fine

Thank you all for helping me with this. Thread can now be closed
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka

Hey guys,
I'd like to add something
I had the same problem, only that my Wifi and Bluetooth still wouldnt work after replacing Magisk with an older Version or using a custom kernel ...I just flashed the newest OOS and the TWRP Installer, rebooted to TWRP and flashed Magisk v16.4 and wiped Cache/Dalvik.
Now, everythings working again

Oggy512 said:
Have a look at the official Magisk Thread here.
If you flash masgik with TRWP you don't have the "Preserve AVB 2.0/dm-verity" checkbox and this causes your issue most probably.
Try the above mentioned methode and it should be fine
Click to expand...
Click to collapse
this solved the issue on 5.1.11 OP6. thanks.

Going back to stock; Error 7

So as the title goes i'd like to go back to stock with root. I dont know what happened but i downloaded the OTA and install when boot. To. Recovery i encountered "error 7". Can anybody help me fix this. Am happy with stock rom and kernel with magisk.

Bump

You must install Old Twrp 3.0.1
Wysłane z mojego RNE-L21 przy użyciu Tapatalka

I agree, is a recovery problem!

Which version of twrp recovery are you using?

Restore backup from TWRP and "Your device is corrupt"

Hi guys,
I'm having issue with my OP6 9.0.4
I have restored the backup from TWRP and after restart system I have this screen:
https://imgur.com/a/5iZWA7V
All the memory is blocked I can not see my files they're encrypted and TWRP is not asking about my PIN
How to get it back to live without wiping everything?
I have access to TWRP...

No one can help with this ?
Wysłane z mojego X80 Pro(E3E7) przy użyciu Tapatalka

You backup is encrypted. Just with the same decrypt key you can access your files. Try to change slots and access them
If it doesn't work, probably you lost you data.
Enviado de meu ONEPLUS A6003 usando o Tapatalk

I can not access my files as TWRP is not even asking me about the password...

You can't even browse your files?
Enviado de meu ONEPLUS A6003 usando o Tapatalk

I have installed by twrp and ADB sideload again the system and it boots up, so I can access my files now!
Wysłane z mojego ONEPLUS A6000 przy użyciu Tapatalka

SkubiDoo said:
I have installed by twrp and ADB sideload again the system and it boots up, so I can access my files now!
Wysłane z mojego ONEPLUS A6000 przy użyciu Tapatalka
Click to expand...
Click to collapse
Use the official twrp. Bluspark has a few unsolved issues.

dgunn said:
Use the official twrp. Bluspark has a few unsolved issues.
Click to expand...
Click to collapse
Hi, I'm interested in this. If the official twrp works out of the box, what are the partitions to backup to be able to restore without any issue (I've been stuck in fastboot after having restored with bluespark, I've just restored boot, system and data) Now it's ok but I had to reflash a fastboot stock image to recover my bricked device
So if the offcial twrp works well, has anyone been brave enough to test if the restore part works well? (or if some troubles come as I read in some thread due to the crypted system?)
Since I have the oneplus6, I have the feeling that the things get more complicated than before with nandroid backups
Thanks for your enlightenments guys

There are plenty of sources on XDA that give step-by-step instructions and I for one have restored 9.0.2 with the official twrp. Just make sure to also read The Forum of the 255 error and delete all of the 999 folders BEFORE creating the backup