Database Info

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?

Root Lenovo Phab 2 Pro

Hi to all, i see this guide ....
Does anyone test it?
http://lenovo-forums.ru/topic/22676-lenovo-phab-2-pro-poluchenie-root-prav/

nope; waiting for a wealthy member to brick his phone and then post the solution :laugh:

I unlocked bootloader but.. stuck on step#2 (disable secure boot) any1 have stock boot.img for PB690M_s2000100_170228 ?

Any other methods surface?

Sorry for late replay. I already rooted & xposed this device.
Wysłane z mojego Lenovo PB2-690M przy użyciu Tapatalka

gandalfini said:
Sorry for late replay. I already rooted & xposed this device.
Wysłane z mojego Lenovo PB2-690M przy użyciu Tapatalka
Click to expand...
Click to collapse
Did you use my post guide?
Sent from my Lenovo PB2-690M using Tapatalk

Yes, but for step#2 (Disable secure boot) i download FW PB2-690M_S200100_170228_ROW_QPST (same FW and extract boot.img from here)

gandalfini said:
Yes, but for step#2 (Disable secure boot) i download FW PB2-690M_S200100_170228_ROW_QPST (same FW and extract boot.img from here)
Click to expand...
Click to collapse
What do you think about the updates? Can we reflash the stock for update the phab (if lenovo helps)
Sent from my Lenovo PB2-690M using Tapatalk

can anyone give an update on the current ability to unlock the bootloader and install TWRP and root this phone? either with supersu or with magisk?
thanks

gandalfini said:
Yes, but for step#2 (Disable secure boot) i download FW PB2-690M_S200100_170228_ROW_QPST (same FW and extract boot.img from here)
Click to expand...
Click to collapse
I can't download bootloader unlock file... how did you download PB2-690M_unlock_7M.7z file?

Successfully Rooted!
Damn! Rooting this thing was a TASK. But after a struggle of few hours I was successful (Without any bootloops)

Tell us more

The rooting process is same as in the link that's there in the first post of this thread.
A) Unlock Bootloader
B) Disable Secure Boot by flashing patched boot.img (See details below)
C) Install Extended TWRP Recovery
D) Flash SuperSU
Here's what I did:
1. Unlocked Bootloader
1. Downloaded the FW PB2-690M_S200100_170228_ROW_QPST firmware and extracted boot.img from it
2. Unpacked the boot.img, made edits in the ramdisk\default.prop and ramdisk\fstab.qcom
3. Repacked boot.img with these edited files and flashed it
4. Flashed Extended TWRP Recovery
5. Flashed SuperSU and then install the app from play store.
6. Checked by any root checking app.
7. Voila! Result = Success!
Hope this helps
PS: Detailed guide is the first post in this thread. Do go through it for what or which lines/files to edit in boot.img and also for download links for the firmware

For unroot can be installed the firmware in the first post?
Sent from my Lenovo PB2-690M using Tapatalk

vespino75 said:
For unroot can be installed the firmware in the first post?
Sent from my Lenovo PB2-690M using Tapatalk
Click to expand...
Click to collapse
Yes, you may reflash stock. Although you'll need to reverse the entire process. Flash original boot.img and the firmware and lock bootloader.
Sent from my Lenovo PB2-690M using Tapatalk

This method doesn't work for the phab 2 pro PB2-690Y. I would pay to have root on this phone. It's very surprising there isn't more people developing for this phone. Basically non-existent.

strawsy said:
This method doesn't work for the phab 2 pro PB2-690Y. I would pay to have root on this phone. It's very surprising there isn't more people developing for this phone. Basically non-existent.
Click to expand...
Click to collapse
Pardon me, but I would want to understand why this method won't work with PB2-690Y when it works perfectly with PB2-690M? Yes you'll need the proper respective firmware to extract the boot image but that's it. Everything else should be same.

Well I don 't have the proper firmware and tried the firmware given. Not sure where I would get the firmware.

strawsy said:
Well I don 't have the proper firmware and tried the firmware given. Not sure where I would get the firmware.
Click to expand...
Click to collapse
That's bad. Because the Russian Lenovo forums (from where I downloaded my firmware) seems to only have the one for 690m at the moment.

Dominic.B said:
That's bad. Because the Russian Lenovo forums (from where I downloaded my firmware) seems to only have the one for 690m at the moment.
Click to expand...
Click to collapse
Correct. I definitely would have used the 690Y if it was available. I'm pretty sure the only difference is 690M is international and 690Y is US. I've tried every other method known of rooting but none work. This is my favorite phone I've owned but lack of development and accessories is killing the phone.

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.

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

Cant able to install TWRP on android Q beta 3

So i have installed android Q beta 3 but when i try to flash latest bluespark twrp via Fastboot its showing this everytime.
FAILED (remote: unknown command)
Though i am typing correct command
Fastboot boot twrp.img
Any help

Flash VIA fastboot mode.
Wysłane z mojego Redmi K20 Pro przy użyciu Tapatalka

jumis said:
Flash VIA fastboot mode.
Wysłane z mojego Redmi K20 Pro przy użyciu Tapatalka
Click to expand...
Click to collapse
Command i have mentioned is already Fastboot method

Do you have the latest version of the SDK Platform Tools on your computer?

makeyourself said:
Do you have the latest version of the SDK Platform Tools on your computer?
Click to expand...
Click to collapse
Give link. But previously there is no such problems

I am experiencing exactly the same problem.

pankspoo said:
Give link. But previously there is no such problems
Click to expand...
Click to collapse
Perhaps but you've installed a new version of the Android Bootloader which interfaces with fastboot. Possibly the Q upgrade also changes your partition layout, I don't know.
The link can be easily found on google but here it is anyway.

makeyourself said:
Perhaps but you've installed a new version of the Android Bootloader which interfaces with fastboot. Possibly the Q upgrade also changes your partition layout, I don't know.
The link can be easily found on google but here it is anyway.
Click to expand...
Click to collapse
Yes i think so, but how can be this problem person specific as u told its working for you?

Anybody who solved this problem? Having the same problems here

It's a known issue. For now, you could try flashing fastboot Pie ROMs. Next time you flash any ROM, flash TWRP afterwards.
If flashing fastboot ROMs also give you problems, then your only remaining chance is to use MSM download tool.

mideg said:
I am experiencing exactly the same problem.
Click to expand...
Click to collapse
Same but in 9.0.8

fastboot boot twrp.img just doesn't seem to work under Android Q anymore. I have the TEST version of TWRP and that doesn't flash with fastboot boot either :/

So I also experienced this problem last night. Had to forego sleeping just to get it to work. Thankfully it's a Sunday.
Anyway, after extensive searching, I have concluded that it is indeed caused by an updated bootloader that disables the "fastboot boot" commands. The OP7 Pro also has this problem.
Unfortunately, flashing stock Pie fastboot ROMs don't fix the problem. I tried flashing all the way back to OOS 9.0.5, but it seems like the bootloader didn't revert and is still unable to accept "fastboot boot" commands.
In my case, I needed TWRP to flash Magisk. Fortunately, we can install Magisk without flashing via TWRP. It's as simple as installing the Magisk Manager APK from topjohnwu's github, and patching the OOS 10 boot.img. I believe there's already a thread somewhere here that provided the patched boot.img. all we need to do is just fastboot flash boot magisk-boot.img, and we should be rooted. I can even install some mods.
For the fastboot issue though, I don't think we're gonna find a fix any time soon.

I have the same Issue.
Went back from Q Beta to 9.0.9 Stable and also flashed the original bootloader.
It's still not possible to fastboot boot TWRP. I'll hope this will be fixed soon...