Develop Bugs

[GUIDE] How to Change Boot Logo (Splash Screen) of NextBit Robin

Note:
This is not bootanimation, this is to change the splash screen (the 'Robin' boot logo which is displayed when device is switched ON)
This is for Nextbit Robin Only..
(For other devices, please send me your splash.img so that I can create a tool for you too.)
Requirements:
1. Rooted Nextbit Robin (any ROM) or just unlocked bootloader
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Nextbit_Robin_Splash_Maker.zip
2. Make sure you have a picture in PNG format with resolution 1080x1920px.
3. Now rename your picture as logo.png & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though..)
You may get it from the stock firmware itself.
I have also attached the stock splash.img from 10/6/16 - 00WW_1_450.
Now, choose any one easy method to flash:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Also, changing the splash screen doesn't mean you can get rid of the 5 seconds timeout in bootloder unlocked warning, that's actually present in the bootloader (aboot partition).. (To get rid of that, you either need to patch it up to set the timeout to 0, or you may have to unset the unlock & tamper bit similar to this.. And, I'm not doing this, since I don't own a Robin as of now)
Hit the Thanks :good: button if it worked for you
You are welcome to post the splash images that you created (along with the picture)..

Awesome. Thanks for this.

Made these from a few images i found on google so all credit goes to the original owners and the OP of course.
[Flashable zip]

BTW @GokulNC the battery image does not change when building the logo. This could be because of newer firmware maybe and updated image? Whatever it is I'd love to help test whatever fix that could be implemented

Now if only we could figure out how to remove the annoying pestering startup warning about unlocking the device

AnierinB said:
BTW @GokulNC the battery image does not change when building the logo. This could be because of newer firmware maybe and updated image? Whatever it is I'd love to help test whatever fix that could be implemented
Click to expand...
Click to collapse
I'm not sure.. I just found a battery pic in it and put it as it is..
Maybe it's loaded from the boot.img (unpack it and check it out)
Jacobwitt said:
Now if only we could figure out how to remove the annoying pestering startup warning about unlocking the device
Click to expand...
Click to collapse
Try locking the bootloader and see if still that warning persists..
Code:
fastboot oem lock
If that didn't help, send the aboot partition of your device (Both stock locked aboot and unlocked one)..
I'll check that out..

AnierinB said:
Made these from a few images i found on google so all credit goes to the original owners and the OP of course.
[Flashable zip]
Click to expand...
Click to collapse
made that my new wall paper lol.

souphail said:
made that my new wall paper lol.
Click to expand...
Click to collapse
Here is the updated Logo and wallpaper. Added a basic ether compound (Device Code-name is ether) and rearranged some things,

So I noticed another bug that is pretty interesting.. when you don't use a battery logo and just the logo.png the battery logo shows stock boot logo (when battery dies and then plug in) even though its not in my pics folder.. must be another instance of it in the splash.img

I just watched this and thought I was on my thread for a second xD Nice video man!
But for future reference it's pronounced A-NY-RIN, but don't worry everyone gets it wrong haha.

[SPLASH Backup] Stock Boot Logo of Zenfone 5 (Both white splash & black splash)

Note:
This is not bootanimation, this is the splash screen (the 'Asus' boot logo which is displayed when device is switched ON)
This is for Asus Zenfone 5 Only..
(Click here for other devices)
Requirements:
1. Rooted Asus Zenfone 5 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to flash stock splash.bin:
Optional: To backup your original splash.bin:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.bin
(Not necessary though.. You may get it from the stock firmware itself.)
Download the stock_splash.bin zip file.
(Check this out for the black Asus splash screen.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Extract 'splash.bin' from zip file & transfer the splash.bin to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.bin of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.bin
or
fastboot flash splashscreen splash.bin
Credits:
1. @juyel92 who provided the stock splash.bin of Zenfone 5 T00F model..
Hit the Thanks :good: button if it helped you
Why I'm unable to find solution to change splash screen:
Unlike the other devices for which I have created splash tools, it seems the Zenfone 5's splash image is actually signed & verified while booting with checksums in bootloader.
I don't know how the file is actually signed (even If I knew what algo, I don't have the signing keys).
And also, I'm unable to recognize the format of splash.bin completely..
So, I guess custom splash screens are not possible until there's some insight into this..
BTW, just in-case if you were wondering how, to extract the logo picture, use the command:
Code:
ffmpeg.exe -hide_banner -f rawvideo -vcodec rawvideo -pix_fmt bgr24 -skip_initial_bytes 1083 -s 720x1280 -i splash.bin -vf "vflip" -vframes 1 -y output_logo.png
To extract charger battery picture:
Code:
ffmpeg.exe -hide_banner -f rawvideo -vcodec rawvideo -pix_fmt bgr24 -skip_initial_bytes 2765937 -s 720x1280 -i splash.bin -vf "vflip" -vframes 1 -y output_battery.png
And also, I have also left the splash changer tool as it is in the attachments which I created thinking it would work..
It seems it's not working

GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Asus' boot logo which is displayed when device is switched ON)
This is for Asus Zenfone 5 Only..
(For other devices, please send me your splash.img so that I may create a tool for you too.)
Requirements:
1. Rooted Asus Zenfone 5 (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.bin:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Download & Extract this in computer: Zenfone_5_Splash_Maker.zip
2. Make sure you have a 720x1280 resolution picture.
3. Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'Create_Logo.bat' to create splash.bin , which you can find inside the "output" folder.
STEPS to flash splash.bin:
Optional: To backup your original splash.bin:
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.bin to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.bin from fastboot or custom recovery.
(This was tested only on T00F variant only, but I guess it should work in all devices. If it doesn't, please send me your device's stock splash.bin
I just saw another variant of splash.bin. I'm beginning to wonder why it's named splash_signed. Are the pictures signed and verified while booting? Or does it have to match bootloader checksums or something? IDK; let's see)
Credits:
1. @juyel92 who provided the stock splash.bin of Zenfone 5 T00F model and tested it..
2. @GokulNC (myself ) who wrote this script
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
Finally, we got our tool for changing our ASUS boot logo? in Zenfone 5.
Thanks to @GokuINC for making this tool.
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

@GokulNC Bro after creating my own splash.bin and then flashing it vai adb...it's shows successful. But the boot logo changed to a rectangular red block. It doesn't changed to my custom pic what i have choosed. Just showing red rectangular block. I tried 4-5 times, and the result is same "red rectangular block".
What's the problem here ? Can you please tell me why it's showing only red rectangular block ?
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

juyel92 said:
@GokuINC Bro after creating my own splash.bin and then flashing it vai adb...it's shows successful. But the boot logo changed to a rectangular red block. It doesn't changed to my custom pic what i have choosed. Just showing red rectangular block. I tried 4-5 times, and the result is same "red rectangular block".
What's the problem here ? Can you please tell me why it's showing only red rectangular block ?
Click to expand...
Click to collapse
It's the same tool with which I created the iron man splash.bin which you tested and said it's working. I'm wondering what might be the issue now..
Send the splash.bin that you created, I'll check it out tomorrow..
Meanwhile, to others reading this post: pls check if working and do reply

GokulNC said:
It's the same tool with which I created the iron man splash.bin which you tested and said it's working. I'm wondering what might be the issue now..
Send the splash.bin that you created, I'll check it out tomorrow..
Meanwhile, to others reading this post: pls check if working and do reply
Click to expand...
Click to collapse
Yesterday also the same red rectangular block appeared. I thought you have created this red rectangular block just to test it whether it's working or not. Thats why i said its working.But now after creating my own splash.bin, i found that only after flashing custom splash.bin these red rectangular block appears. But when i flashed the stock splash.bin it shows me the original asus boot logo. I'm confused why this is happening.? ?
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

juyel92 said:
Yesterday also the same red rectangular block appeared. I thought you have created this red rectangular block just to test it whether it's working or not. Thats why i said its working
Click to expand...
Click to collapse
Lol bro, why would I send a rectangle
No problem, that was my mistake, I should have told you
juyel92 said:
But when i flashed the stock splash.bin it shows me the original asus boot logo. I'm confused why this is happening.
Click to expand...
Click to collapse
I will check what the issue is

GokulNC said:
Lol bro, why would I send a rectangle
No problem, that was my mistake, I should have told you
I will check what the issue is
Click to expand...
Click to collapse
Haha .. It was my mistake also.. I should ask you before what image you used?
Anyway please find the solution for this.. Everything is fine but why every time it shows only red rectangular block.
Please find the solution ASAP!
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

@GokulNC Did you find the solution?
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

Ah god, changing splash screen was the one I used to desperately find a way to when I used Zf5. A good sign for the current ZF5 users tho

BlackDragonz said:
Ah god, changing splash screen was the one I used to desperately find a way. A good sign for the current ZF5 users tho
Click to expand...
Click to collapse
Still we can't change the splash screen (boot logo) with our custom one. ?
Sent from my Asus ZenFone 5 (A500CG) using XDA Labs

juyel92 said:
@GokulNC Did you find the solution?
Click to expand...
Click to collapse
Nope, I couldn't.. I have explained the reason in the OP at the bottom..
(BTW, this thread featured in the XDA Portal.. Lol..
Gotta ask them to remove it.. Uff..)

Still no solution for this yet?
I really wanna wipe out everything of stock even this splashscreen.

What matter if i lost my splash image ? Does my phone can boot?

[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.

Removing "Bloatware"
Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.
Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.
Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.
You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.
Installing Debloater
Launch Magisk Manager and select "Download" from the menu
Use the search function to locate the package "Busybox for Android NDK"
Install the package, and chose to skip the reboot at the end of the procedure.
Use the search function to locate the package "Debloater Terminal Emulator"
Install the package and this time proceed with the reboot
When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
Open the terminal and issue:
Code:
su
(confirm the request for superuser access) and then
Code:
debloat
Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.
Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.

One Question
Can i know this work for Redmi Note 9 global non NFC?

The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!

dfahren said:
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
Click to expand...
Click to collapse
Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E

[email protected] said:
Can i know this work for Redmi Note 9 global non NFC?
Click to expand...
Click to collapse
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.

N3OMOD said:
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
Click to expand...
Click to collapse
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!

dfahren said:
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
Click to expand...
Click to collapse
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
dfahren said:
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
Click to expand...
Click to collapse
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
dfahren said:
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
Click to expand...
Click to collapse
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
dfahren said:
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
Click to expand...
Click to collapse
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)

Followed the steps, worked flawlessly on my Redmi Note 9 (Merlin) 3gb ram 64gb storage purchased in Europe, running Global 11.0.5.
Thank you so very much!
I had successfully done this in the past but messed something up with xposed later, I won't xposed it this time and just enjoy my root-ness.

N3OMOD said:
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
...
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
...
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
The original explanation from user "neko-kun" seemed to me an automatic translation hence the rather weird language.
I can testify to the statement that you can reflash the original boot.img file should you enter a bootloop (which I got).
AdAway is also working for me as does AFWall+ (I needed to leave logging of blocked packets as it is -> off)

N3OMOD said:
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
i'm having an infinite bootloop and keep pressing power + vol down didn't help , what should i do ?

@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi

dfahren said:
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
Click to expand...
Click to collapse
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?

What about entering recovery?
noodlelicious said:
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
Click to expand...
Click to collapse
Try to enter stock recovery, if you can, select mi assitant. After that connect trough adb and run "adb reboot bootloader", that should do the trick.
If phone isnt booting none of main enviroments (system, recovery or fastboot/bootloader) battery drainage may restablish normal boot order. Just remember that if in any case it boots to recovery, use adb command to reboot to bootloader.

Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global
Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.
- Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.
- vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.

Hi .. Is there a way to write to system / app. I need to be able to pass an application to system. Thank you.

Does netflix still work in HD after having the BL unlocked and further rooted?

How to patch vbmeta
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
N3OMOD said:
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Click to expand...
Click to collapse
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?

can this be used to root the EU model: MZB9410EU ?

farvehar09 said:
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
Click to expand...
Click to collapse
Yes u can, i use the original vbmeta from miui_MERLINIDGlobal_V12.0.1.0.QJOIDXM_709d727d58_10.0.zip (ID variant)

Red Magic 5G BackUP Request

Hello XDA Forum
I have a little problem with my Red Magic 5G
I accidentally deleted the parameter files and also other important files out of stupidity and wanted to ask whether someone has a red magic 5g and can make a backup via twrp and send it to me? < I really don't know what to do anymore >
I have flashed new software with edl on it and installed all 3 rom versions but I still have the same problem non of them worked i can't even install custom rom anymore.
Best Regards
Akizuma

Has really no one a backup for me left for the red magic 5g ?

Hello, what parameters are missing in your red magic5g, can I help you? I use red magic5s

(I think everthing)
I need a twrp backup from a red magic 5g where everthing still works i destroyed to much,
Not even touch working anymore in twrp.
Edit ( I think not that 5s works on 5g or ? )

you don't need anything from someone else's device.
if you ****ed something up. then you need to use the unbrick tools. and set them up correctly and follow the directions to unbrick.
they will erase all your data. but form what I've read, you lost all that already.
there are unbrick tools for both devices. 5S or 5G on either forum for those devices make sure you're using the correct unbrick tool. 5g does not work correctly with 5S devices, and vice versa.
the unbrick tools will format and restore every single parition on the phone. restoring it to factory settings.
its very possible though if you were messing with partitions that you erased your IMEI.
if thats gone, its beyond the scope of the unbrick tools. you'll have to contact warranty services.
the unnofficial unbrick tools by Johnny in my opinion better.
just make sure your drivers are correctly installed, and up to date. .. this includes windows updates.
(recently there has been a google ADB driver that needs updating thats available through winodws update)
so make sure thats installed too.
set your phone to EDL mode and follow the direction on Johnny's thread.
it will restore your phone as long as you can get to Fastboot mode. (vol down and power)
PM me if you need more help. but that should be enough to get your back to stock.

Problem Fixed ! #closed

@Akizuma it would be kind to post what you did to fix the issue, so others in the future who are faced with the same issue can use your solution.
We are a community here to help others.
If we mention that our problems are sorted, without posting how, it only helps the direct user and other searching for solutions to fix their issues will continue.
Please post what it was you did to fix your issue. It would be very appreciated.

If you're having any of these issues, this option may be able to fix it.
Problem: black screen after boot up, touch not working (TWRP) or automatic booting in EDL mode
First download the Unbrick EDL Tool
(I chose EU)
Download here:
[Tool] Nubia Red Magic 5G Unbirck Tool
So.......It's finally here, the unbrick tool for RedMagic 5G. This tool can help you to unbrick the phone. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm...
forum.xda-developers.com
Then follow the instructions in the folder and install an operating system on it through edl mode
Then you start the installation again but this time you don't run it because I noticed that the tool doesn't flash important image files but skips them (you can even find it in the log)
First go to \ AppData \ Local \ Temp \ is-K4OSH.tmp \ NubiaEmergencyDownload \ software
(name can be different)
And copy
persist.img
boot.img
odm.img
recovery.img
system.img
vendor.img
And put it in a new folder
After that go to the bootloader again and unlock the oem via
(fastboot oem nubia_unlock NUBIA_NX659J)
Then execute following commands for the files like
(Command (Fastboot flash persist [file.img])
(Command (Fastboot flash boot [file.img])
(Command (Fastboot flash odm [file.img])
(Command (Fastboot flash recovery [file.img])
(Command (Fastboot flash system [file.img])
(Command (Fastboot flash vendor [file.img])
It can be that most of them give out an error, execute them anyway in case the folder still exists
Then the cell phone should start again normally.
P.s ( Sorry for my poor english ^^ )

System, Vendor, and odm, are all partitions flashed during the "super" partition.
this is why you didn't see them exactly written in the log they all go under "super" and get assigned a dynamic partition when flashed.
you cna see here how they changed the partitions and how they're written now.
Implementing Dynamic Partitions | Android Open Source Project
either way. thank you for your effort to your solution.

Looking for assistance, UNLOCKED dev test point

AT THE END OF THE DAY (week actually) this won't work for U.S. based phones as far as I could find. Huawei partitions etc. are all ****y and I can't update firmware beyond EMUI 8 because the sites are all down/gone so RIP me and my week of working on this dumb ****. Save yourselves, don't attempt if within the U.S.
I tried a billion things, but eventually I ended up taking my phone apart and getting access through the dev test point and potatoNV. Once fully unlocked I attempted to flash various images, but end up in boot loops until I reinstall EMUI. I'm presuming my problem is with finding a proper image? Let me know if you know otherwise, but I'm looking for latest Android version with GAPPS that will work on the Honor 7x please!
If you're reading this, just ditch the phone or deal with what you have. Leaving the following info in case anyone is stubborn enough to give it a shot, but I highly do not recommend it.

Taking notes for myself if no one comes out of the woodwork
I managed to reach the 313 logo (ducks), but froze there with https://github.com/phhusson/treble_experimentations/releases/tag/v313 (aonly GAPPS)

Still would love assistance/input. I've tried a bunch of different images including 'a only' and android 10, but still hitting issues. Not sure if SparseConverter is helping or hurting either

Tried
system-squeak-arm64-ab-gapps.img.xz
system-roar-arm64-aonly-GAPPS (chunked and not)
system-arm64-aonly-gapps-su.img
dotOS-R-v5.2-arm64-ab-GAPPS-OFFICIAL
system-quack-arm64-aonly-gapps = new android logo boot screen loading forever
Havoc-OS-v3.12-20201230-Official-a64-aonly - spooky, never got out of bootloader
For anyone else doing this, items I've read say that factory reset should be done before AND after flashing system.
I feel like there is a RAM limitation on some of these later android OS, but here's some more info
honor7x is KIRIN 659 arm64 a-only partition
POST FLASH INSTRUCTIONS
After entering the reboot command, your 7x will reboot and you will see the warning screen where it tells you that your device is unlocked. On that screen "PRESS AND HOLD THE VOLUME UP KEY" to boot into erecovery to perform a Factory Reset. If you do not, the phone will boot loop until it forces you too.
per https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X#post-flash-instructions

I have been scrubbing the asshole of the internet to find this information.
honor7x is KIRIN 659 arm64 a-only partition
adb shell getprop ro.treble.enabled = true
HOWEVER
the device isn't fully VNDK-compliant (https://source.android.com/devices/architecture/vndk), and the device can use only the GSI for the same on-device OS version. For example, an Android 9 (API version 28) device that isn't VNDK-compliant can load only an Android 9 GSI image.
per https://developer.android.com/topic/generic-system-image
so we're (allegedly although I've seen otherwise) stuck with android 8 Oreo (in my case U.S.)
no TWRP download for 7x specifically...using 7 = 3.1.10 then
installed magisk https://forum.xda-developers.com/t/...10-mate-10-pro-huawei-treble-devices.3749280/ is a useful guide
Installation
The Magic Mask for Android
topjohnwu.github.io
https://androidfilehost.com/?fid=673956719939832043 = boot.img
adb push -p BOOT.img /sdcard/
(on the pull they ****ed up the _ and -)
device does not have a separate vbmeta partition, JUST KIDDING found one at /dev/block/platform/hi_mci.0/by_name when checking for boot
adb reboot fastboot
trying with recov because boot gave me partition length get error...
(img1)
idk at this point because a lot of people have TWRP that I'm unable to get because of this^ and I don't think this garbage phone even has a boot partiton? (img2) but has two recovery partitions per https://forum.xda-developers.com/t/honor-7x-bricked.3973247/

aw this: https://forum.xda-developers.com/t/oreo-twrp-complete-backup.3764500/
but also saw:
https://www.reddit.com/r/honor7x/comments/ao2qkd
(large comment about spending 36 hours from currently named user PMmeYourFlipFlops)
Android Booting Shenanigans
The Magic Mask for Android
topjohnwu.github.io
probably a type III device for magisk...
adb pull recovery_ramdisk
adb pull ramdisk
didn't work
grab path for twrp
/storage/sdcard0/Download/twrp-3.1.1-0-plank.img
flashing recovery gives same partition length get error
fastboot flash recovery_ramdisk twrp.img
STOP HERE pretty sure this is the step where I screw myself and at least my phone still uses safe mode, but I don't have a recovery.img
imagine drowning phone by holding vol +, vol -, and pow. get spooky err screen (no recovery img failed)
got emui screen
hold pwr vol + to get normal (not ereco) recovery. Still ****ing boned so trust pmMeYourFlipFlops at this point.

I'm currently on emui 8 vendor
TWRP For Emui 8: https://forum.xda-developers.com/t/...e-unofficial-twrp-3-2-1-0-28-04-2018.3783447/
ROMS I have tried:
Havoc OS Arm64-aonly: https://forum.xda-developers.com/t/...ab-arm-arm32binder64-updt-2019-09-14.3930030/
AOSP 9.0 v123 -- system-arm64-aonly-vanilla-nosu.img.xz: https://github.com/phhusson/treble_experimentations/releases/tag/v123

Descendant OS 4.0.1: https://forum.xda-developers.com/t/sp-aug-r47-descendant-4-0-1-for-treble-enabled-devices.3840578/

You can also try this roms: https://github.com/erfanoabdi/ErfanGSIs
Remember to download arm64-aonly for emui 8 and arm64-ab for emui 9