[GUIDE] How to Change Boot Logo (Splash Screen) for Lenovo Yoga Tab 3 Plus YT-X703F - Lenovo Yoga Tab 3 Plus Guides, News, & Discussion

Here is a tool provided by @GokulNC and modified with instructions from here: https://forum.xda-developers.com/showpost.php?p=73942075&postcount=144
GokulNC said:
Please try the following steps for your Lenovo Tab 3 Plus YT-X703F and tell me if it works:
1. Download the tool for Mi 5: https://forum.xda-developers.com/mi-5/how-to/guide-how-to-create-custom-splash-t3425054
2. Open bin/logo_gen.py & change "SUPPORT_RLE24_COMPRESSIONT = 0" to "SUPPORT_RLE24_COMPRESSIONT = 1 " (in line 71) and save the script.
3. Now use a 1600x2560 picture to create a splash.img using the same tool and flash it.
If it works, please post the modified tool in your device's sub-forum so that it'll be useful for others
Click to expand...
Click to collapse
I found that the image needs to be in portrait, (Or rather create in landscape, then rotate 90 degrees to the right)
Here are instructions taken from here https://forum.xda-developers.com/mi-5/how-to/guide-how-to-create-custom-splash-t3425054 and edited for the modified tool for Yoga Tab 3 Plus:
Note:
This is not a bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when the device is switched ON)
This is for Yoga Tab 3 Plus YT-X703F Only
Requirements:
1. Rooted Yoga Tab 3 Plus YT-X703F
2. Optional: Terminal Emulator app or Custom Recovery or at least working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly on your computer (just in case something goes wrong)..
1. Download & Extract this: https://forum.xda-developers.com/attachment.php?attachmentid=4291531&stc=1&d=1507064918
2. Make sure you have a picture with resolution of 1600x2560 portrait (Make the image in landscape, then rotate 90° to the right)
Note:
In fact, you don't need a 1600x2560 picture, you can even have a picture with any resolution lower than device resolution, which will automatically be centred while booting.
3. Now rename your picture as logo.png or logo.jpg (according to the format) & replace it inside "pics" folder of the extracted folder.
(Or you can also directly edit the picture inside)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , 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
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or 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:
In case something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot. I've also attached a flashable zip of the original YT-X703F splash.img
Credits:
1. @GokulNC who wrote this script
2. Based on logo_gen.py script
Hit the Thanks :good: button if it worked for you

Reserved

Thank you for sharing this! I hadn't realized that these scripts come straight from Qualcomm, although when you think about it, it does make sense

Thanks for the wonderful article, the device which I am doing this is also in your list, but somehow its not working for me, am I missing anything ?
Code:
[email protected] Root % fastboot flash splash splash.img
Sending 'splash' (44 KB) OKAY [ 0.009s]
Writing 'splash' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

gtl-madhav said:
Thanks for the wonderful article, the device which I am doing this is also in your list, but somehow its not working for me, am I missing anything ?
Code:
[email protected] Root % fastboot flash splash splash.img
Sending 'splash' (44 KB) OKAY [ 0.009s]
Writing 'splash' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Click to expand...
Click to collapse
Which device do you have?

scoobyjenkins said:
Which device do you have?
Click to expand...
Click to collapse
Lenovo TB-8505X

@scoobyjenkins is it possible you can tell me where they have actually stored that -> splash.img file or logo.img or logo.bin file ?
I am trying this from 3 days, searching all round. not succeeded. sorry but I am not very good with all this stuff, Just learning from you all experienced XDA members.

Delete

gtl-madhav said:
Lenovo TB-8505X
Click to expand...
Click to collapse
gtl-madhav said:
@scoobyjenkins is it possible you can tell me where they have actually stored that -> splash.img file or logo.img or logo.bin file ?
I am trying this from 3 days, searching all round. not succeeded. sorry but I am not very good with all this stuff, Just learning from you all experienced XDA members.
Click to expand...
Click to collapse
Sorry, this is for Yoga Tab 3 Plus YT-X703F only. All I did was ask on the thread by GokulNC, linked in the OP, and he gave me instructions to modify a tool for another device. That worked so I created this thread with the modified tool for YT-X703F. If you go to GokulNC's thread, hopefully you can get some help there

scoobyjenkins said:
Delete
Click to expand...
Click to collapse
I am very new to XDA, can you tell me what you saying here.

gtl-madhav said:
I am very new to XDA, can you tell me what you saying here.
Click to expand...
Click to collapse
The tool in this thread is based on the work of GokulNC and his thread is here: https://forum.xda-developers.com/t/...en-for-snapdragon-devices-splash-img.3470473/
You will need to ask your question there as I can't help with your device. My thread is only for the Yoga Tab 3 Plus YT-X703F

Related

[ROM][X][O][8.1][WEEKLY]OmniROM

X/SUZU/F5121 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. No USB tethering
2. Wifi sometimes fails to turn on
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.1
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
[url]https://gerrit.omnirom.org/[/URL]
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image has been downloaded from HERE
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem odm_loire.simg
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Wifi sometimes disconnects (fixed by enabling/disabling wifi)
2. Fingerprint sensor sometimes fails to detect or add new fingerprints (workaround available HERE )
3. No USB tethering
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Click to expand...
Click to collapse
Hi, I'm happy for the new version.
I'm already trying.
P.S. I noticed an error in the fastboot command [fastboot flash oem odm_loire.simg]
Thank you so much for your work!
Im getting error message bluetooth has stopped and phone restarts is there any particular reason clean install as it mentioned
Looks promising. Is video recording supported? And if yes, will you add [email protected] video capturing in the future? Current kernel codecs supports that...
Seems that Microg does not work properly. UnifiedNLP cannot be registered.
Are you able to get the dark mode? I enabled it, but it stays light.
Pico-TTS works again.
Gray47Maxx said:
Looks promising. Is video recording supported? And if yes, will you add [email protected] video capturing in the future? Current kernel codecs supports that...
Click to expand...
Click to collapse
video recording works, 60fps mode is probably not feasible currently.
mase76 said:
Seems that Microg does not work properly. UnifiedNLP cannot be registered.
Are you able to get the dark mode? I enabled it, but it stays light.
Pico-TTS works again.
Click to expand...
Click to collapse
microg requires some patches right? That's probably why it doesn't work.
Dark mode works here, the background of quicktiles changes to black (note that what you're changing is systemui style)
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
1. The device has the latest stock ftf
3. The ODM image has been downloaded from...
Two things are unclear to me:
What and for what is the ODM_image?
Why is the latest stock ftf required?
Thanks for ROM and answers
Click to expand...
Click to collapse
MichaBit said:
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
1. The device has the latest stock ftf
3. The ODM image has been downloaded from...
Two things are unclear to me:
What and for what is the UDM_image?
Why is the latest stock ftf required?
Thanks for ROM and answers
Click to expand...
Click to collapse
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Olimpo83 said:
MichaBit said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Exactly at the same minute I improved it - ODM is in op. ;P
---------- Post added at 10:23 PM ---------- Previous post was at 10:16 PM ----------
Olimpo83 said:
MichaBit said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Ahh, maybe right now im getting it; u mean 'OEM' is equal to stock?
(so i dont have to use Emma) :angel:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Why the latest stock ftf is also unclear to me. I did a dirty flash from Omni 7.1.2, flashed that odm image and things work so far.
I did not know, that darkmode is for the quicktiles only. I thought, that would also make the system apps dark.
My powermenu is strange. Only a poweroff and a silent button. How can I get the reboot menu? I also checked the extended reboot, but I never got it to see.

			
				
MichaBit said:
Two things are unclear to me:
What and for what is the ODM_image?
Why is the latest stock ftf required?
Click to expand...
Click to collapse
1. The ODM image contains proprietary binaries that are required by the system
2. The latest stock ftf is required to guarantee having the latest bootloader. That way support for flashing ODM image using fastboot is guaranteed.
Olimpo83 said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
well, depends on how you define it:
1. if you define the image by its intended usage, it's an ODM image according to google.
2. if you define the image by the target partition on our devices, it's an OEM image.
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
Please check OP more thoroughly, especially the part about having the latest stock ftf flashed
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
i had the same problem you should not use by flash tool you have to do it on command prompt, place the file on a folder name it as flash then open the command prompt then paste fastboot flash oem odm_loire.simg thats it
---------- Post added at 06:33 AM ---------- Previous post was at 06:22 AM ----------
oshmoun said:
Please check OP more thoroughly, especially the part about having the latest stock ftf flashed
Click to expand...
Click to collapse
i manage to do as it mentioned but after few hours phone start to restart i cant make calls even i really wants to have this rom i tried
GCam5.1.018-Arnova8G2-V1.5.apk little buggy but portrait mode is awesome i cant imagine the pictures are so good on suzu
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
I had written it in the second post.
The OEM file must have the extension .img
Rename it in oem_loire.img Change the file extension, put it in the platforms-tools folder, click with the right mouse button and at the same time click the Ctrl key on the keyboard to display the option OPEN CONTROL WINDOW HERE.
Turn off the mobile phone and then reconnect it to the PC by holding the VOLUME UP button, until the blue LED (Adb mode) appears. After doing this in the terminal enter the command FASTBOOT FLASH OEM OEM_LOIRE.IMG (written in lower case).
No way for install for me, got newest ftf and flashed oem image. Flashing of omnirom always ends at
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR 7
Error installing zip file
Click to expand...
Click to collapse
EDIT: Figured it out. I had to change odm_loire.img into oem_loire.img
rheckr said:
No way for install for me, got newest ftf and flashed oem image. Flashing of omnirom always ends at
EDIT: Figured it out. I had to change odm_loire.img into oem_loire.img
Click to expand...
Click to collapse
Those two things are absolutely unrelated.
Flashing the odm image does not change anything concerning how the zip is flashed in recovery. Simply renaming the file name also obviously has no effect.
So it must be something else that allowed the zip to successfully flash.
Fingerprint scanner doesn't work. Unable to add any finger.
Face unlock (trusted face) is missing. This omnirom is lacking two of most important features...
Front camera autofocus is messed also. I'll wait for stable release. Anyway good job.
hey guys,
since the lat update is online for the xperia x, my phone shows me that i can download and patch it automaticly. phone downloaded the rom, try to falsh it in twrp, restarts, but then it stucks at the white screen with the sony logo. i runned this for 2 hours, nothing happens. restartet in recovery mode, installed back to 7.1.2, phone works fine again. downloading the 8.1 rom and install it with twrp also ends in the same result.
someone of u have the same problems? is there an solution?
greetz

[GUIDE][Redmi 5A] How to change Splash Screen (Boot Logo) for Redmi 5A

Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi 5A Only..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Redmi 5A (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.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Download & Extract this in computer: Redmi_5A_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.
(Similarly you can also change fastboot.png if you wish to change the picture of fastboot)
4. Finally, run the 'Create_Logo.bat' to create splash.img , which you can find inside the "output" folder.
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.)
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.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.
Credits:
Thanks to @franktom for the stock splash.img of Redmi 5A.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Thank you very much for build this tool.
---------- Post added at 05:13 AM ---------- Previous post was at 05:00 AM ----------
franktom said:
Thank you very much for build this tool.
Click to expand...
Click to collapse
I'm tested, it's worked as expect, thanks, love u.
Please friend help me its not working friend for me when i sets splash screen by flashing zip file using twrp latest them my spash screen what i created it comes for a little second like 0.0000001s and then mi stock splash screen appears and then it starts bootanimation and finaly i am back to my lockscreen please help me fast i am on redmi 5A custom rom cr droid how to do it please tell me
successfully changing my redmi 5a splash screen, thank you!
permission to try.thank's
Really helpfull
:good: Thanks Bro
Can anyone make splashscreen google for me
Ok
eelsymbianers said:
Can anyone make splashscreen google for me
Click to expand...
Click to collapse
I Just made Google bootlogo
Where to get pocophone splash screen.
...
It bricked my redmi 5a, when booting, xiaomi bunny appears and random characters then it boots into 900e diagnostics mode...
I flashed with fastboot flash splash splash.img... Now I'm trying to repair with MiFlash. :crying:
EDIT:
May be the problem that I flashedwith that default Google logo andnot a 720x1080 picture?
Any Telegram channel/group to download custom splashes?
kalmin06 said:
Any Telegram channel/group to download custom splashes?
Click to expand...
Click to collapse
Telegram links are not allowed to be shared here

[TWRP] self-booting 3.2.3-0

I extended the given TWRP from s3tupw1zard ported by Thinhx2.
You can now use the adb root access while the TWRP booted and access your phone with mtp when it is not encrypted.
It is a self booting image now, means, this boot file only boot direct to TWRP.
NEVER flash this image direct to flash with fastboot flash boot, you cannot start android then, only TWRP.
Boot it, while your smartphone is in fastboot mode, with the command:
fastboot boot self_bootingTWRP323.img
Then you can do everything like in the flashable version of TWRP, only with the advantage that you are not security patch dependent and you don't need to modify your original system.
You can install all ZIP files, like Magisk or open-Gapps.
After reboot the smartphone starts normal from the boot partition inside the smartphone and twrp is gone.
Tested in 00EEA platform only but i guess it will also run on 00WW!
Lol, what's the difference between each of these 4 parts. No statement about it. Lack of info may confuse users.
Its one rar image divided into 4 parts because upload size is limited!
page1875 said:
Its one rar image divided into 4 parts because upload size is limited!
Click to expand...
Click to collapse
How could I combine it all?
Download them all, put them to the same folder and extract the first image.
Then the rar extractor will take the following images automatically!
How to decrypt Nokia 3.2 using TWRP.
page1875 said:
Download them all, put them to the same folder and extract the first image.
Then the rar extractor will take the following images automatically!
Click to expand...
Click to collapse
Works perfectly. If you want to decrypt your Nokia 3.2 you will be needing to format your data partition using TWRP. But your device will be encrypted again (if you didn't do (perhaps) any backup or used commands like "adb push") once it booted up.
I tried it after unlocking bootloader but it just goes to black screen and nothing is happening, only solution is holding power button and it reboots normally. here's the command output:
[email protected]:~# fastboot boot /mnt/q/twrp/self_bootingTWRP.img
downloading 'boot.img'...
OKAY [ 0.962s]
booting...
FAILED (status read failed (No such device))
finished. total time: 6.614s
I'm on android 9 (no updates applied), phone is TA-1164. build number: 00WW_1_08D.

Pixel stuck on google loading screen after flashing patched boot image

I'm trying to root my Pixel 3 and my device is stuck on the white google loading screen after flashing the patched boot file.
Here is what I've done so far:
Downloaded the boot image -> Installed Magisk on my phone -> patched the boot image -> booted into Fastboot -> flashed the patched boot image -> then my phone restarted and has been stuck on the white google loading screen.
If I hold the volume down button and the power button, my screen goes to the Fastboot mode. Then if I try to power off and start the phone, I get back to the white google loading screen which doesn't change.
Heres the logs from terminal if that provides any info:
(base) [email protected] android % ./fastboot flash boot magisk_patched.img
Sending 'boot_b' (31860 KB) OKAY [ 0.310s]
Writing 'boot_b' OKAY [ 0.258s]
Finished. Total time: 0.837s
(base) [email protected] android % ./fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
Anyone have any ideas? everything was going smoothly until this point so not sure what I've done wrong. Any help is appreciated, thanks!
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk. Probably dm-verity was enabled when you flashed Magisk's boot.img.
My advice: Try to re-flash Stock ROM.
jwoegerbauer said:
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk.
Try to re-flash Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply but slight issue. I got impatient and tried another solution which was:
(base) [email protected] android % ./fastboot flash boot --slot all magisk_patched.img
Sending 'boot_a' (31860 KB) OKAY [ 0.310s]
Writing 'boot_a' OKAY [ 0.494s]
Sending 'boot_b' (31860 KB) OKAY [ 0.200s]
Writing 'boot_b' OKAY [ 0.192s]
Finished. Total time: 1.760s
Now my device is stuck in a loop on the Fastboot Mode screen with following info:
Device state: unlocked
Boot slot: a
Enter Reason is: "no valid slot to boot'.
Also my device is now NOT recognised by my laptop so I'm unable to re-flash stock ROM as you suggested or do anything. sigh... I shouldn't have rushed.
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
jwoegerbauer said:
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
Click to expand...
Click to collapse
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
MHuncho said:
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
Click to expand...
Click to collapse
Hold power and volume down buttons to get to fastboot.
Tulsadiver said:
Hold power and volume down buttons to get to fastboot.
Click to expand...
Click to collapse
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
MHuncho said:
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
Click to expand...
Click to collapse
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Tulsadiver said:
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Click to expand...
Click to collapse
Would this work if I'm on a Mac? as its a bat file
MHuncho said:
Would this work if I'm on a Mac? as its a bat file
Click to expand...
Click to collapse
You should use the .sh file.
Tulsadiver said:
You should use the .sh file.
Click to expand...
Click to collapse
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
MHuncho said:
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
Click to expand...
Click to collapse
I believe that he was inferring that you are rooting in order to run a custom ROM and that maybe you should have stayed stock.
I don't know where you got your boot image but if you will unzip the image zip that was inside your firmware where you found the flash-all zips you should find the correct boot image to use. First you should enable developer settings and enable USB debugging so you can use USB. What you did sounded correct.

How To Guide [TUTORIAL] ULTIMATE How to flash GSI Trebble AND ROM and root on Xiaomi device on Windows (files needed included)

Hi, first of all, I'm not a dev or else just user who had difficulties to flash GSI on my phone... Was 7 years with a samsung galaxy Note 3, with twrp....So easy to flash....
with the help of @gr0ndpa, thanks to him.....
FLASH GSI​
Now I will explain how to flash easily with files attached
1/ first of all you need a phone and drivers installed, use xiaomi pc suite, unzip and install it
2/ you need to activate USB debug in dev options.
3/ dl adb folder unzip it and put in C
4/ run command and type
Code:
cd /adb
5/ then
Code:
adb devices
to check if phone recognised
6/
Code:
adb reboot bootloader
once in fast boot
7/
Code:
fastboot flash vbmeta vbmeta.img
wait finished type to enter in fastbootD
8/
Code:
fastboot reboot fastboot
9/
Code:
fastboot flash system
LiR 313.XXX.img
you will have a system error, but wait the flash begin in few seconds
at the end wait ok then
10/
Code:
fastboot reboot recovery
on stock recover
11/ wipe data and reboot with +/- and PWR
and you're done...
In case you want to flash custom kernel or patched boot image to root with magisk, you have to
12/
Code:
adb reboot bootloader
Copy kernel boot image to C drive and rename kernel boot image to boot.img.
13/
Code:
fastboot flash boot c:\boot.img
14/
Code:
fastboot reboot
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
Downloads for : Xiaomi Mi 11 Lite 5G | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You can check what I ve done on tuto ss...
if you have some comments, don't hesitate...
I flashed LiR 18.1 rom and very happy with it.....
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==================================================================================================================================================================================================================++
Flash ROM​
This now how to flash ROM on your device, it's convenient for all roms like LOS, corvus, awaken...
First you need all the proper drivers installed and unlocked bootloader, USB debugging all of that stuff.
Now open up a cmd/terminal , and put the files i sent and the ROM file in the folder from where you're opening the cmd/terminal and connect the phone (you may need to put ./ as an suffix for all the commands if you're on linux)
Type
Code:
adb reboot bootloader
Then type
Code:
fastboot devices
to see if everything is ok
Then type
Code:
fastboot flash boot_ab boot.img
(you can drag and drop the file instead of typing it)
After that's done type
Code:
fastboot flash vendor_boot_ab vendor_boot.img
(you can drag and drop this too if you want)
Code:
fastboot flash dtbo dtbo.img
(you can drag and drop this too if you want)
After that's done type
Code:
fastboot reboot recovery
This will boot you into a recovery and now you need to go to wipe and format data
After that go to apply update then adb sideload then
In the cmd type
Code:
adb sideload rom.zip
for example (you put the ROM zip here you can drag and drop it)
Wait for that to finish it will go to 47% and on the phone it will show step 1/2 then step 2/2
and when it's done it's gonna show an error
adb: failed to read command: No error
Then you can reboot to system
Hello thank your for the short HowTo. Unfortunately im stuck on invalid sparse error. Could you pls post a fix to solve this? Would appreciate your help.
hardshell said:
Hello thank your for the short HowTo. Unfortunately im stuck on invalid sparse error. Could you pls post a fix to solve this? Would appreciate your help.
Click to expand...
Click to collapse
You have to wait at least 30 sec after the error appear...
Are you sure you are on fastbootD???
tuto modified and completed to also root device with magisk and patch boot.img
when i restart into fastboot, it is frozen.
dy2592 said:
when i restart into fastboot, it is frozen.
Click to expand...
Click to collapse
normal, nothing happens on fastboot....when you flash, only thing is on your computer, not on screen..
cant seem to get this installed =(
rayman95 said:
8/
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
After I enter this, it just stays on waiting for any device.
Update: I was able to figure it out. My device had no drivers so I went search through updates on windows and installed a LeMobile Android driver os it shows up properly in device manager.
How does one install gapps?
dy2592 said:
After I enter this, it just stays on waiting for any device.
View attachment 5419437
Update: I was able to figure it out. My device had no drivers so I went search through updates on windows and installed a LeMobile Android driver os it shows up properly in device manager.
Click to expand...
Click to collapse
because you don't have xiaomi drivers installed...install xiaomi pc suite and you will have drivers installed...
duplicate
rayman95 said:
In step 14, I encountered the error "fastboot: error: ANDROID_PRODUCT_OUT not set" after executing the fastboot flash system command. what do I need to do?
Click to expand...
Click to collapse
Did you insert the img at the end?
Fastboot flash system LIRxxxxxxxxxxxx.img
you have to put your rom to adb folder and dont forget to add .img at the end
rayman95 said:
you have to put your rom to adb folder and dont forget to add .img at the end
Click to expand...
Click to collapse
1.img is your rom Is there anything else missing?
dy2592 said:
Did you insert the img at the end?
Fastboot flash system LIRxxxxxxxxxxxx.img
Click to expand...
Click to collapse
yaha your right thank you so much
rayman95 said:
you have to put your rom to adb folder and dont forget to add .img at the end
Click to expand...
Click to collapse
thank I solved my problem. Now I have another problem, how to install GAPPs
Patrick Star_ said:
thank I solved my problem. Now I have another problem, how to install GAPPs
Click to expand...
Click to collapse
run twrp, it's explain in 1st post or maybe try with magisk...I can install minimicroG nogoolag with it..
rayman95 said:
run twrp, it's explain in 1st post or maybe try with magisk...I can install minimicroG nogoolag with it..
Click to expand...
Click to collapse
I tried to use twrp to brush into GAPP, but the error is 70. How can I solve it? I don't know if there is a problem with my twrp. Can you send a tutorial on xiaomi11 Lite 5g installing twrp? Thank you very much
Patrick Star_ said:
I tried to use twrp to brush into GAPP, but the error is 70. How can I solve it? I don't know if there is a problem with my twrp. Can you send a tutorial on xiaomi11 Lite 5g installing twrp? Thank you very much
Click to expand...
Click to collapse
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
And twrp link is in post 1..maybe you choose bad gapps variant

Categories

Resources