Database Develop

Custom Boot Images here

I merged all the bootscreens from the original boot screen thread in development. Over taking "aron4588" as the thread creator of this one. His original post is in 12.
Sorry "aron4588" ​
This is updated with the latest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
(Driver for 1.5r2)
If you have the "new spl" you're going to need the new usb drivers
(http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565 You dont get a splash2 option with the "NEW SPL"
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Go to the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
OR get Boot Screen Flasher 3000 by dom2684 & Octoberriot

to build the file yourself go to the root android source directory (mine is linux, but it looks like this "/home/ryan/android_source"), your's might look something like "C:/Source Codes/android/" or whatever. Once you navigate to that directory (via the command prompt... just go to start > run > and type in 'cmd' and hit enter, then use the 'cd' command to get there... e.g., "cd C:/Source Codes/android/"), once there, simply type 'make' and hit enter and it will start building everything, it might take a few minutes to complete. Then just go into the 'out' directory, then it's under "host/windows-x86/bin" (i'm not sure about the windows-x86 part, it might just be windows or something like it, i'm just assuming based on mine), once in that folder you'll have the fastboot as well as all of the other binary files ready to go. Then you can just type fastboot w/e w/e and it'll work just fine.
Here's my updated bootloader logo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's kind of difficult to see, my camera sucks... it's my fraternity letters with the crest in the background. Here's the image i used for it:

Here's what I finally settled on.
Take 2...

I found this one on google, I think it suits me

Ok, before i go dual booting my system , as i have Vista x64 now. I want to know if i can use ubuntu x64 for this process or would it be best to use the 32 bit version.
Here is the boot image I put together that i want to use. Still futzing with it but this is the general idea.

Stock Boot Logos
For anyone that wants a copy of the stock images, for instances of RMA/repair.......Here they are.
The file contains both UK and US logos
Thanks to JesusFreke and Tobes, for the rip coding and the UK logo

Custom Boot Screen
Just sharing the boot screen I'm using. Made by me on PS. Enjoy.

Yes, you need to convert the picture.
Just in case here is the raw file.

Sure, I can provide the base image. On mine however, I customized it with some of my information, such as my name, etc. That way if it ever gets stolen, the thief will be reminded of it everyday
Stericson

infernix said:
“It won't work,” droned Marvin, “I have an exceptionally large mind.”
Click to expand...
Click to collapse
I really liked this idea, so I found the image at deviantart, and made a copy of your boot image, and for anyone else, I've attached the splash.raw565 file (zipped) to this post.
Cheers guys, and happy new year!
-- michael

Domo for android

[HOW TO] Install Custom Boot Images/Post images here
CAN I GET A STICKY I THINK THIS THREAD HAVE HELP ALOT OF PEOPLE AND I NEVER BEEN STICKY BEFORE LOL
This is updated with the lastest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Goto the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible

I was able to, here is mine:

It didnt work for me

brandenk said:
It didnt work for me
Click to expand...
Click to collapse
To the OP, you can grab that file from the SDK tools folder and include it in the zip.

Ok, so I downloaded this: http://graha.ms/androidproxy/AdbWin.zip
I put those 2 files in the fastboot folder and it worked! Thank you aron4588!!!
And here is a mirror to your file with those two files added: http://www.4shared.com/file/78814404/36e59544/Boot_images.html

Success
I was able to do it, but quick question.
How many splash images can I have?
I was able to flash 2 over and it boots the first one (splash1) and then the second one (splash2)
How far can I go with this?

MMTest97 said:
I was able to do it, but quick question.
How many splash images can I have?
I was able to flash 2 over and it boots the first one (splash1) and then the second one (splash2)
How far can I go with this?
Click to expand...
Click to collapse
You can only do 2 images.
Here's mine

How long does this take to send? It's been "sending" for over a minute now

Yanked the battery, restarted the whole process and it worked. Very nice tutorial!

cannot flash TWRP recovery...

I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BTW I have USB debugging on and the fast boot option under power settings checked off. I have tried clearing cache also via cmd prompt 'fastboot clear cache'
Sent from my HTC One using xda app-developers app

cloud628 said:
I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help! View attachment 2429761
Click to expand...
Click to collapse
First to clarify things:
you don't need to be s-off to flash a custom recovery just need unlocked bootloader
you need a custom recovery to root
you need root to s-off
so you need a custom recovery first in order to achieve s-off
The picture you attached tells me fastboot isn't finding the file ''twrp,img'' from your command line ''fastboot flash recovery twrp.img
in most cases because:
your recovery.img file is not in the ''platform-tools'' folder that contain adb.exe and fastboot.exe
the file name of your recovery is not twrp.img
Code:
fastboot flash recovery ''name_of_your_recovery_file.img''
fastboot erase cache
fastboot reboot-bootloader

i'll just leave this here: "cannot load" means the filename is WRONG!!! that's all
cya

okay I'll will give it a go with the suggestions tonight and update this thread with my results
Sent from my HTC One using xda app-developers app

So did I set this up correctly now? And I just open the CMD prompt window up from inside this domain and type "fastboot flash recovery "paste file name here" ? View attachment 2431242

So I just tried again....same error

I downloaded the newest SDK batch files and attempted again. Now I get a different error message.

cloud628 said:
I downloaded the newest SDK batch files and attempted again. Now I get a different error message. View attachment 2431302
Click to expand...
Click to collapse
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!

nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.

C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot devices
FA-----10153 fastboot
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery C:\Users\ds
hi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'C:\Users\dshi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshin---\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7
error: cannot open 'openrecovery-twrp-2.6.3.3-m7'

nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
OHHHHH!!!! It worked!. Now I get it! Jeeeze that was absolutely frustrating but now I know. Thank You SOOOOO Much!

cloud628 said:
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.
Click to expand...
Click to collapse
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk

thanks a ton!
nkk71 said:
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!

Hi Guys, just an FYI, i'm leaving here the link to download the current versions of TWRP IMG
SITE: https://twrp.me/
Regards!

asmallmammal said:
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!
Click to expand...
Click to collapse
please tell how you fix that i have the same problem

Just rename the file without typing in ".img" at it should be ok.
So in explorer, rename the file simply "twrp" and hit enter. There will be a ".img" extension on the file, but you won't see it. To make sure it's been corrected, run the dir command and it should show "twrp.img" even though the file doesn't have the ".img" when you look at it in explorer.
Does that make sense?

How to show/hide file extension
For Windows Vista, Windows 7, and Windows Server 2008
Start Windows Explorer, you can do this by opening up any folder.
Click Organize.
Click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
Note To hide file name extensions, check this line.
Click OK
For Windows 2000, Windows XP, and Windows Server 2003
Start Windows Explorer, you can do this by opening up any folder.
Click Tools, and then click Folder Options.
Scroll down and then click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
https://support.microsoft.com/en-us/kb/865219

what is it for htc at play?

[Q] [Help!] An Accident

I accidentally wiped my internal storage while flashing a new rom. Now I am in recovery and not having anything in. I can't even mount anything or flash anything :\ What can I do to fix it?

Hi!
If you have previously copied a backup to your computer (You should always do this) you can restore it by using the push command in ADB to your device and then restoring the file the normal way in Recovery. (Mind the file path, it should be exact. If you have no backup download any ROM to your phone and push this in the same way. I recommend Android Revolution, but any ROM will do.
It might be easier to first install a ROM, then do a backup of it to find the exact path if you want to restore a previous backup.
I have only used it a few times, but a quick Google search should give you enough information to get you started with the push commands.

MySlimey said:
I accidentally wiped my internal storage while flashing a new rom. Now I am in recovery and not having anything in. I can't even mount anything or flash anything :\ What can I do to fix it?
Click to expand...
Click to collapse
follow this guide to transfer your rom again to your phone, while booted in recovery:
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery (2.6.3.3 for all 4.4+ roms or 2.7.1.1 for newer CM roms) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse

alray said:
follow this guide to transfer your rom again to your phone, while booted in recovery:
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
​
Click to expand...
Click to collapse
Yeah, I have a problem though. I can't open a fastboot Terminal or and ADB terminal, it always closes really fast. I don't even know how it happens and what causes it :\

MySlimey said:
Yeah, I have a problem though. I can't open a fastboot Terminal or and ADB terminal, it always closes really fast. I don't even know how it happens and what causes it :\
Click to expand...
Click to collapse
I guess you are trying to execute adb or fastboot by double clicking the icon which is not possible. Open the folder where adb.exe and fastboot.exe are and hold left shift then right click a blank space in that folder. in the contextual menu, select "open a cmd window here" and then you'll be able to type fasboot/adb commands. Its all explained in the guide (2nd prerequisite, 3rd method):
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
Click to expand...
Click to collapse

It worked! Thanks man!

*deleted*

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!

Question Hardbrick no recovery or fastboot

Forgot how it got to this point, i think i flashed wrong boot.img or something, but my device just reboots constantly on the redmi sign. Tried following the guides on here but i got lost at some point. I've installed the driver filter and done the mtk bypass thing, but I'm confused on where i should go from here?

first of all, install MTK preloader/brom vcom drivers for your PC be able to detect your phone in BROM mode (attached below)
install MiFlashPro, you will need it to fill the Download-Agent in sp tool so you can write the boot images to recover your phone.
then, use the miui ROM that you used before bricking it, or download it from any website (my favorite is mifirm.net, it downloads faster)
now open sp tool from MiFlashPro.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
after it bypasses, go to sp tool and click download immediately, then your device should come to life.
if it didnt work, i recommend selecting every mapping excluding your data, or do a full reflash if you wish or as last resort

1lopes said:
first of all, install MTK preloader/brom vcom drivers for your PC be able to detect your phone in BROM mode (attached below)
install MiFlashPro, you will need it to fill the Download-Agent in sp tool so you can write the boot images to recover your phone.
then, use the miui ROM that you used before bricking it, or download it from any website (my favorite is mifirm.net, it downloads faster)
now open sp tool from MiFlashPro.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
after it bypasses, go to sp tool and click download immediately, then your device should come to life.
if it didnt work, i recommend selecting every mapping excluding your data, or do a full reflash if you wish or as last resort
View attachment 5860063
Click to expand...
Click to collapse
I was having errors with 'verified boot', managed to reflash everything with mtkclient, how do i get back to stock rom from here? Phone boots to fastboot mode but 'fastboot reboot fastboot' or 'fastboot reboot bootloader' just reboots device

HollyMarijuanna said:
I was having errors with 'verified boot', managed to reflash everything with mtkclient, how do i get back to stock rom from here? Phone boots to fastboot mode but 'fastboot reboot fastboot' or 'fastboot reboot bootloader' just reboots device
Click to expand...
Click to collapse
use mi flash pro, open mi flash, download miui rom and flash it thru there while on fastboot. you dont need dynamic fastboot for it, dont worry

1lopes said:
use mi flash pro, open mi flash, download miui rom and flash it thru there while on fastboot. you dont need dynamic fastboot for it, dont worry
Click to expand...
Click to collapse
Thank you! I was trying to fix this phone in December and gave up.. I appreciate your help

HollyMarijuanna said:
Thank you! I was trying to fix this phone in December and gave up.. I appreciate your help
Click to expand...
Click to collapse
glad to help