Related
YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND BE CAREFULL WITH THE COMMAND LINES
PROCEED ON YOUR OWN RISK
READ, READ, READ BEFORE PROCEEDING....
Hi A7 Users
--------------
Here we are with a new / excited finding ( thanks @Unjustified Dev )for ALL of us A2017U and A2017G (IS GETTING OFFICIAL UNLOCK AND THIS METHOD NOT TESTED YET,ANY VOLUNTEER?)
and is about UNLOCKING the Bootloader for those who are stock B20 or B27 + Lock Booloader.
Only IMPORTANT requirement is you need to have TWRP install, so if you don't have TWRP install here is the link
and you just NEED TO INSTALL TWRP and if you haven't back-up your STOCK boot.img is the right time to do so
Click Here on How to Flash TWRP with Lock Bootloader, Thank You @tennear
NOTE : THIS PROCEDURE WILL ERASE , I REPEAT WILL ERASE YOUR DATA + INTERNAL STORAGE.
SDCARD IS SAFE.
Steps :
---------
1- Download this File TWRP_UnlockBootloaderPackage_by_DrakenFX.zip and move to your SDCard.
2- Enable "OEM UNLOCKING" under Developer Options
3- Reboot to TWRP
Code:
adb reboot recovery
4- Lets make sure your device is detected
Code:
adb devices
Great let keep going.
5- Open Command and navigate to your adb location.
6- Type the following
* BACK-UP AND PULL CURRENT FASTBOOT IMAGE
Code:
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb pull /sdcard/fbop_lock.img
* FLASH TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
Awesome you have backup and flash the bootloader unlock package file but wait we're done yet
7- Type the Following
Code:
adb reboot bootloader
8- Lets make sure device is present
Code:
fastboot devices
9- Now let's Unlock the Bootloader (THIS WILL WIPE DATA+INTERNAL STORAGE)
Code:
fastboot oem unlock
10- You'll boot in TWRP once there do the following :
Code:
* tap [B]CANCEL[/B]
* tap [B]WIPE [/B]
* tap [B]FORMAT DATA[/B] and Follow the Instructions
11- Once done REBOOT
12- WHEN FULL BOOT GO BACK TO TWRP AND CREATE A BACK-UP AND KEEP IT SAFE
13- Have Fun you're now Bootloader Unlock With Stock B20 or B27 Software.
---------------------------------------------------------------------------------------
NOTE : A2017U.B27 Users Everytime you BOOT to System , Recovery, etc, etc you'll be getting a splash screen, JUST WAIT 5 SEC. and your device will boot to where you want to go.
---------------------------------------------------------------------------------------
If You Have the A2017G version and you are already on B03 you can follow step by @Starvirus
A2017G_B03 Unlock Bootloader Steps
---------------------------------------------------------------------------------------
CREDIT / Contributor
- @Unjustified Dev for testing in his Brand New just less than 3 hrs old A2017U and popping up in me the idea about this finding
- Thank you @regenwurm16 for Confirm New method working for A2017G
- Thank you @Starvirus for provide B03 steps
---------------------------------------------------------------------------------------
reserve 1
reserve 2
reserve 3
Mine
So.. this means unlocked bootloader for full flexibility but also OTA updates because it's still running stock?
So jelly. Stuck on B20_boot over here.
jpde said:
So.. this means unlocked bootloader for full flexibility but also OTA updates because it's still running stock?
Click to expand...
Click to collapse
about right, as long you have an Untouch/UnModded System + boot, so yeah
runderekrun said:
So jelly. Stuck on B20_boot over here.
Click to expand...
Click to collapse
@Unjustified Dev is uploading something that will help us go back to B20, I'll be testing this as soon is done and create a Thread for it, is just matter of time
DrakenFX said:
about right, as long you have an Untouch/UnModded System yeah
Click to expand...
Click to collapse
Holy crap, that sounds awesome. Huge thanks for all of your work! Hoping someone will be able to confirm that it works on the A2017G
Just wow!
Thats what I have talked about.
I hope it works on the A2017G version.
Is this reversible? Would ZTE somehow be able to tell if the bootloader was unlocked before when returning the device for a warranty?
legendarygizmo said:
Is this reversible? Would ZTE somehow be able to tell if the bootloader was unlocked before when returning the device for a warranty?
Click to expand...
Click to collapse
yes it is, just keep your fastboot img in a safe place backup is in OP part of the guide.
to revert back is very simple same step but instead using fastboot_unlock.img you use your fastboot backup and do the rest of the steps (wipe and so on)
DrakenFX said:
yes it is, just keep your fastboot img in a safe place backup is in OP part of the guide.
to revert back is very simple same step but instead using fastboot_unlock.img you use your fastboot backup and do the rest of the steps (wipe and so on)
Click to expand...
Click to collapse
Don't forget fastboot oem lock
Sent from my ZTE A2017U using Tapatalk
Unjustified Dev said:
Don't forget fastboot oem lock
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
annnddd that too
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
SinisterXReaper said:
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
Unfortunately it's necessary.
Sent from my ZTE A2017U using Tapatalk
SinisterXReaper said:
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
been honest in Marshmallow, i remember in Lollipop you could unlock bootloader and keep everything but in Marshmallow everything change, any device i had that need bootloader unlock it wipes.
We essentially just forced ZTE's legal department's hand. They now have no way of voiding warranty with unlocked bootloader. Nice job guys!
Can I do this procedure with Axon Zte 7 A2017? (China Model)
Moderator Edit: @blessingme - it is not necessary or desirable to quote the entire OP. It can cause page loading issues with those on limited bandwidth or when mobile.
Thanks
blessingme said:
Can I do this procedure with Axon Zte 7 A2017? (China Model)
Click to expand...
Click to collapse
If you have twrp installed, let us know and don't forget to backup your fastboot.img
Sent from my ZTE A2017U using Tapatalk
I flashed Xiaomis Official Global ROM with gapps (maybe that's where I went wrong?) and I went to reboot after a successful flash and it refuses to power on, go to recovery and it's not recognized in windows. Says there was an error or something.
Please give me ideas asap!
Can you get to fastboot mode?
[Tools, Tips & Tutorials] [DEVICE TEAM] Flash (Unbrick) Redmi Note 3(SD) with Locked Bootloader - All ROMS
If you can not get to fastboot mode then: -
How to Unbrick Redmi Note 3 Snapdragon (Best Solution)
corkiejp said:
Can you get to fastboot mode?
[Tools, Tips & Tutorials] [DEVICE TEAM] Flash (Unbrick) Redmi Note 3(SD) with Locked Bootloader - All ROMS
If you can not get to fastboot mode then: -
How to Unbrick Redmi Note 3 Snapdragon (Best Solution)
Click to expand...
Click to collapse
No fastboot.
That seconds method also has a broken download link.
CarterDavison said:
No fastboot.
That seconds method also has a broken download link.
Click to expand...
Click to collapse
Is it the emmc file? get it from here.
corkiejp said:
Is it the emmc file? get it from here.
Click to expand...
Click to collapse
Okay, that method fixed it. Thanks so much, now the next problem I have is that no matter how many times I flash TWRP or what version of it that it won't actually work. The flash goes through fine but when I reboot to recovery, it's just the stock one and not TWRP
CarterDavison said:
Okay, that method fixed it. Thanks so much, now the next problem I have is that no matter how many times I flash TWRP or what version of it that it won't actually work. The flash goes through fine but when I reboot to recovery, it's just the stock one and not TWRP
Click to expand...
Click to collapse
Any time you boot up MIUI it replaces stock recovery, so you need boot straight into TWRP.
You need to use a TWRP that patches the boot image or flash Universal Boot Img Patcher (UBP).
See this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
corkiejp said:
Any time you boot up MIUI it replaces stock recovery, so you need boot straight into it.
You need to use a TWRP that patches the boot image or flash Universal Boot Img Patcher (UBP).
See this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Click to expand...
Click to collapse
Which one do I use? i tried cofface and it worked but it's in Chinese!
CarterDavison said:
Which one do I use? i tried cofface and it worked but it's in Chinese!
Click to expand...
Click to collapse
Goto settings third option down on the right!
Select the Globe Icon
Choose your language
And click the option button bottom right.
I'm on xiaomi.eu rom, so use official twrp, but temporarily boot Alka for making backups.
Code:
fastboot boot <nameofTWRP.img>
corkiejp said:
Goto settings third option down on the right!
Select the Globe Icon
Choose your language
And click the option button bottom right.
I'm on xiaomi.eu rom, so use official twrp, but temporarily boot Alka for making backups.
Code:
fastboot boot <nameofTWRP.img>
Click to expand...
Click to collapse
You've been a huge help, thank you so very much!
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
Hi guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
Sagit Logo Generator for Xiaomi Mi Pad 4 (clover)
Download: here
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 4 image files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 4 image files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM.
Source: https://github.com/moonheart/sagit-logo-gen/tree/MIPAD4_clover
Thanks @huhu2207 for advice (binwalker).
Thumb up.
Which image should I change if I want to change only the splash screen?
I am still confuse with this mod. Why do I have to change 4 images?
This mod is for splash screen right? Or maybe I am wrong?
I want to know someone successfully using TWRP flash? Because it supports IMG files!
addro said:
I want to know someone successfully using TWRP flash? Because it supports IMG files!
Click to expand...
Click to collapse
Do you know which image to change? There are 4 images.
I want to change only the splash screen. So I only need to change 1 picture, but which one? Is it picture number 3?
dyingbread said:
Do you know which image to change? There are 4 images.
I want to change only the splash screen. So I only need to change 1 picture, but which one? Is it picture number 3?
Click to expand...
Click to collapse
Please be careful that I have failed! I have lost the splash screen.:crying:
addro said:
Please be careful that I have failed! I have lost the splash screen.:crying:
Click to expand...
Click to collapse
What? How did that happen?
Btw you could easly fix that by flashing default logo.img
What picture did you change?
dyingbread said:
What? How did that happen?
Btw you could easly fix that by flashing default logo.img
What picture did you change?
Click to expand...
Click to collapse
I just changed the 03 picture,size 1080X1920.BMP, No other changes to the picture!
addro said:
I just changed the 03 picture,size 1080X1920.BMP, No other changes to the picture!
Click to expand...
Click to collapse
How did you flash the new logo.img? Via twrp or fastboot?
dyingbread said:
How did you flash the new logo.img? Via twrp or fastboot?
Click to expand...
Click to collapse
I use fastboot.
The first time I used this program --> ( https://forum.xda-developers.com/mi-max/themes/guide-to-change-mi-boot-logo-unlocked-t3662117 ) did not change! But it works in my Xiaomi Mi Max!
The second time I used (moonheartmoon) this method was unsuccessful and lost the boot logo! I don't know if it is just a matter of replacing the 03 picture?
I don't know what to do now, can return to the boot logo.
addro said:
I use fastboot.
The first time I used this program --> ( https://forum.xda-developers.com/mi-max/themes/guide-to-change-mi-boot-logo-unlocked-t3662117 ) did not change! But it works in my Xiaomi Mi Max!
The second time I used (moonheartmoon) this method was unsuccessful and lost the boot logo! I don't know if it is just a matter of replacing the 03 picture?
I don't know what to do now, can return to the boot logo.
Click to expand...
Click to collapse
Your device can boot normally right? Just don't have a splash screen. Flash stock logo.img and and your splash screen should be back. You can get stock logo.img from official fastboot rom. Or if you want I can send you the logo img. It's just 3 MB.
dyingbread said:
Your device can boot normally right? Just don't have a splash screen. Flash stock logo.img and and your splash screen should be back. You can get stock logo.img from official fastboot rom. Or if you want I can send you the logo img. It's just 3 MB.
Click to expand...
Click to collapse
Don't give it to me, my stock MIUI ROM everything goes back to normal! You also don't want stock splash screen! Maybe this is only MIUI10 Flash stock!
I have a link, you can refer to it! --> https://xiaomi.eu/community/threads...-image-and-fastboot-image-for-mi-pad-4.47466/
addro said:
Don't give it to me, my stock MIUI ROM everything goes back to normal! You also don't want stock splash screen! Maybe this is only MIUI10 Flash stock!
I have a link, you can refer to it! --> https://xiaomi.eu/community/threads...-image-and-fastboot-image-for-mi-pad-4.47466/
Click to expand...
Click to collapse
I tried with that tool you gave me but still splash screen is gone. Someone who shared that tool in xiaomi.eu forum said that it works but not for me.
Splash screen doesn't have anything to do with ROM. If it works with MIUI it should works with any ROMs.
Have you tried this tool? It works for me on my Mi Pad 4 Plus.
meiser said:
Have you tried this tool? It works for me on my Mi Pad 4 Plus.
Click to expand...
Click to collapse
Do you use miui recovery fastboot?
What do you mean? I use the official fastboot binary.
So I just tried again with moonheartmoon's tool from OP without changing anything. It works, the splash screen is changed to picture no 3 (mi logo with scribble on it).
But when I change picture no 3 with my desired logo it's not working. My picture file type is bmp but it's not working. Is there any special method to make this bmp file?
EDIT: The problem is my picture file size, it's too big. Max picture file size is 2 MB. Bigger than that your splash screen will be gone and shows some warning about bootloader unlocked when booting up.
moonheartmoon's tool is working good for clover. There should be a warning about file size in OP though. Well whatever this tool works, just make sure picture file size is not to big. Thanks
meiser said:
What do you mean? I use the official fastboot binary.
Click to expand...
Click to collapse
You are using MIUI ROM ?