Database Info

Flashing through adb/fastboot

Quick question all,
I was previously on B145 then upgraded to B148. I didn't like and tried to go back B145 and failed. (Before researching through the forum), I took it to flash B300 firmware and was successful but stuck for more than a week trying to figure how to get out of it. Flashing KK never worked (or so I thought), so I decided to try B324...turns out, it flashed and I was on 5.1.1 C900B324. Then I tried B327 and worked for that as well. Now I'm back to B324 and want to go back to B145.
I've been reading around to start at B127 and work up from there, but no KK firmware seems to work at all...some firmwares process, but fail at 19% and some at 90%, others fail at the very start.
Now, was my mistake done when I flashed B300 while still on KK B148? Or, after flashing so many firmwares with adb/fastboot? fyi, whenever I flashed a firmware...I did (Boot.img, Recovery.img, Cache.img, Cust.img, System.img and Userdata.img)...should I have not flashed some of these images when trying to downgrade? Still looking to downgrade back to B145 presently, although there is many cool features of LP.
All the help is appreiciated.
Thanks!
jfer671

Flash b324 then flash b300 from Italy then flash 137sp03 and then flash b145
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka

I think I've tried this and all other avenues, but I'll give it a go once more.
Okay, so is this B300 the (Rollback 5.1 to 4.4)? Or (Downgrade C900B308)? Also, after the correct transition to 300, which img(s) of 137SP03 do I flash and also for B145?
I've been accustomed to flashing Boot/Recovery/Cust/System/Cache & Userdata images...should there be specific images to flash in each for 137 and 145?
Thanks for the feedback!!

Flash using 3 bottom and must work
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka

chudy_85 said:
Flash using 3 bottom and must work
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
I'll try this out and hopefully all goes as planned

chudy_85 said:
Flash using 3 bottom and must work
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka
Click to expand...
Click to collapse
Ok, just as I mentioned before.
I can transition down to B300 from B324. Extract Update.app from B137SP03 and force by 3 buttons; it loads up to 19% and then fails after. I've repeated like 5x already with same results.
I also put the unextracted B137SP03 file into dload and tried 3 button but same Failed results.
Any other ideas? fyi, my bootloader is unlocked as well.

Read this topic and try repair you phone.
Here it's the link
http://forum.xda-developers.com/showthread.php?t=3192839
Wysłane z mojego HUAWEI MT7-L09 przy użyciu Tapatalka

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

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.

'Internal problem with device' warning on boot.

Hi, help please! so I'm getting an 'internal problem with device- please contact your manufacturer' on boot before lockscreen.
This is after the usual bootloader warning.
What have I corrupted exactly?? I went to LOS and back to 5.1.9...

Magisk?
Wysłane z mojego ONEPLUS A6000 przy użyciu Tapatalka

add_pl said:
Magisk?
Wysłane z mojego ONEPLUS A6000 przy użyciu Tapatalka
Click to expand...
Click to collapse
What about it?

Custom recovery. You don't have to worry about that message.

the.Great.Skua said:
Hi, help please! so I'm getting an 'internal problem with device- please contact your manufacturer' on boot before lockscreen.
This is after the usual bootloader warning.
What have I corrupted exactly?? I went to LOS and back to 5.1.9...
Click to expand...
Click to collapse
This screen is being caused by the flashing of the wrong version of Magisk. Uninstall Magisk, then flash Magisk 16.4

I had that as well and to fix it I did the following (running magisk 16.7 without twrp).
1) uninstall -> restore images
2) selected Preserve AVB 2.0/dm-verity
3) install -> direct install
4) reboot
No more message and also after doing this the backups started working again under my google account.

I solved the problem bij using Oxygen updater from the playstore. Reinstalling the last update solved the case.

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