I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
dev.azra said:
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
Click to expand...
Click to collapse
i posted it also to miui eu community, hope someone will help us
it's a new feature from xiaomi actually. if you want to have custom splash image, flash older firmware
Custom boot logo upgrade problem.
My boot logo used to change after I flashed another boot logo but I recently can't change it after flashing to another ROM called 'Alpha Centauri'. I flashed the logo 10 times but all in hell. Can anyone help me out.
Thanks in advance
primarina said:
I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
Click to expand...
Click to collapse
Alright, make a clean wipe of your phone,everything. Now flash this firmware: https://sourceforge.net/projects/xi..._V9.6.2.0.NCFMIFD_88bb9b1f76_7.0.zip/download (all credits go to this site which is updated with the latest firmware :https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917)
Then flash the file below and tell me if it has changed which it should. If it worked keep the same firmware and go to this site(which i got the logo from,credits to them actually) https://forum.xda-developers.com/re...ow-to-change-boot-logo-splash-t3572441/page17
Search for something like this: name_new_firmware and download it or request one icon of your choice for your new firmware
Flash this via fastboot. Working for me on fw 9.6.2.0
Related
I had twrp installed and then i flashed cm13
A fews days later i flashed xposed using twrp and after flashing, it said that stock recovery was trying to replace twrp and asked to swipe to disable it.
i swiped it.
now when i try to boot to recovery, its stuck at mi logo
everything else working fine
just i cant boot into recovery now.
i flashed twrp again using fastboot
but still i m unable to boot to recovery.
Any help would be appreciated
Thanks in advanvce
Flash it using miflash tool.
You have tried flashing using miflash before , haven't you?
Then the procedure is the same, only this time you have to rename twrp file into recovery.img then overwrite original recovery.img in the target miflash folder. Don't forget to remove other files you don't want to be flashed to your device I.e system , data , etc , just keep .XML files or other text files .
Then after you think ready just go flash it
Good luck sir
Yokohart said:
Flash it using miflash tool.
You have tried flashing using miflash before , haven't you?
Then the procedure is the same, only this time you have to rename twrp file into recovery.img then overwrite original recovery.img in the target miflash folder. Don't forget to remove other files you don't want to be flashed to your device I.e system , data , etc , just keep .XML files or other text files .
Then after you think ready just go flash it
Good luck sir
Click to expand...
Click to collapse
Thanks for the reply
will try that
hope it works
yashthakur797 said:
Thanks for the reply
will try that
hope it works
Click to expand...
Click to collapse
You're welcome and good luck
Now I realised that there is no problem with twrp
Actually booting to recovery is taking too long
Whenever I boot to recovery, it shows the mi logo for 5-10 mins and then twrp boots up
Any idea what is the reason for it??
yashthakur797 said:
Now I realised that there is no problem with twrp
Actually booting to recovery is taking too long
Whenever I boot to recovery, it shows the mi logo for 5-10 mins and then twrp boots up
Any idea what is the reason for it??
Click to expand...
Click to collapse
Because you're still on stock firmware , maybe?
Yokohart said:
Because you're still on stock firmware , maybe?
Click to expand...
Click to collapse
i have installed the cm13 firmware
that might not be the reason
yashthakur797 said:
i have installed the cm13 firmware
that might not be the reason
Click to expand...
Click to collapse
which cm13 firmware by who?
actually if you have cm13 firmware the boot logo should change to cm13 logo.
cm13 firmware provided by thestrix
in my case i get the mi logo and then cm13 boot animation
the normal boot speed is fine
but when i boot to recovery, it takes a long time
Problem seems to be solved. it just did work magically. idk how and why but it works and boots up after some time.
as mentioned in the title, i cant get any twrp recovery to boot up.
i got my phone yesterday and succeeded updating it to the latest official version (V3.88 which is android 5.1.1 with nubia ui 4.0)
now i want to get a custom recovery
problem here is, i tried several versions that i found here and everyone doesn't boot up (just stays at the nubia logo)
i tried to flash it via fastboot of course. it gets flashed (command prompt returns "OKAY")
in fact everytime i reboot to android the recovery gets replaced automatically by the original one (at least thats how i think it happens). that means if i try to enter the recovery after i rebooted to android, the old original nubia recovery got restored.
am i missing a step or am i doing something wrong?
pls help
thanks in advance
where did you get v3.88 file?
not_noober_than_me... said:
where did you get v3.88 file?
Click to expand...
Click to collapse
From the official nubia site
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
I bricked my Note 3 while trying to to flash Miui update. I have tried all sorts of flashing miui roms with miflash but mobile restarts after its reached Mi logo with Android at bottom. However I could flash twrp and have tried all wipe all dvilk, cache, system but similar problem.
If u guys could help me to get my cell. Back.
varin11 said:
I bricked my Note 3 while trying to to flash Miui update. I have tried all sorts of flashing miui roms with miflash but mobile restarts after its reached Mi logo with Android at bottom. However I could flash twrp and have tried all wipe all dvilk, cache, system but similar problem.
If u guys could help me to get my cell. Back.
Click to expand...
Click to collapse
Go to twrp and format data.and Type YES to format. This will decrypt and erase data and internal storage.
And reboot.
---------- Post added at 10:05 AM ---------- Previous post was at 09:39 AM ----------
How u flashed miui update?
Using twrp or fastboot method?
naik2902 said:
Go to twrp and format data.and Type YES to format. This will decrypt and erase data and internal storage.
And reboot.
---------- Post added at 10:05 AM ---------- Previous post was at 09:39 AM ----------
How u flashed miui update?
Using twrp or fastboot method?
Click to expand...
Click to collapse
I accidentally flashed fastboot Miui update with TWRP
I accidentally flashed Miui update with TWRP.
varin11 said:
I accidentally flashed Miui update with TWRP.
Click to expand...
Click to collapse
So now ur phone is ok?
naik2902 said:
So now ur phone is ok?
Click to expand...
Click to collapse
I currently have flashed CM 14.1 Rom but this rom have some bugs like casting doesn't work on this.
I want to get back to MIUI. Tried RR and Lineage rom but it gives error 7 on flashing.
Will try the method you have suggested.Anything else do u suggest if the format data doesn't work
Do u think my boot loader is unlocked since I could install TWRp and custom Rom although I never opted for official boot loader unlock since it always gives error ''couldn't unlock'.
will wait for your reply before formatting data.
varin11 said:
I currently have flashed CM 14.1 Rom but this rom have some bugs like casting doesn't work on this.
I want to get back to MIUI. Tried RR and Lineage rom but it gives error 7 on flashing.
Will try the method you have suggested.Anything else do u suggest if the format data doesn't work
Do u think my boot loader is unlocked since I could install TWRp and custom Rom although I never opted for official boot loader unlock since it always gives error ''couldn't unlock'.
will wait for your reply before formatting data.
Click to expand...
Click to collapse
Just put phone in fastboot mode
And check bootloader status using command
fastboot oem device-info
Unlock= true ?
Device unlock=False
Its locked I think.
I tried formatting the dataand later flashing the MIUI rom but same error it goes to MI logo with Android logo down and the phone restarts.Any thing else u suggest.
varin11 said:
Device unlock=False
Its locked I think.
Click to expand...
Click to collapse
Unlock is false.
Ur bootloader is relocked.
Put phone in edl mode.
And Flash fastboot rom using miflashtool.
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
I tried flashing again in edl mode but the mobile restarts at Mi logo ( Android logo at bottom). Have tried flashing beta MIUI rom also but same error.
varin11 said:
I tried flashing again in edl mode but the mobile restarts at Mi logo ( Android logo at bottom). Have tried flashing beta MIUI rom also but same error.
Click to expand...
Click to collapse
Your bootloader is locked .Unlock the bootloader first and than flash the Rom again. Previously I had same problem, my problem was solved by unlocking the bootloader and clean flashing xiaomi.eu ROM through TWRP. If you have twrp installed than go for xiaomi.eu ROM. It is the best MIUI ROM. Hope this will help you.
varin11 said:
I tried flashing again in edl mode but the mobile restarts at Mi logo ( Android logo at bottom). Have tried flashing beta MIUI rom also but same error.
Click to expand...
Click to collapse
Are u flashing zip or tgz file. ?
Flash fastboot tgz rom with clean all option.
If rom is shown succesfully flashed on computer without any error showing. Then ok. no issues.
Firsboot takes time 10 to 15 min With milogo and Android.
rjrulz007 said:
Your bootloader is locked .Unlock the bootloader first and than flash the Rom again. Previously I had same problem, my problem was solved by unlocking the bootloader and clean flashing xiaomi.eu ROM through TWRP. If you have twrp installed than go for xiaomi.eu ROM. It is the best MIUI ROM. Hope this will help you.
Click to expand...
Click to collapse
How to unlock the boot loader.Mi unlock gives error cant unlock.
naik2902 said:
Are u flashing zip or tgz file. ?
Flash fastboot tgz rom with clean all option.
If rom is shown successfully flashed on computer without any error showing. Then ok. no issues.
Firsboot takes time 10 to 15 min With milogo and Android.
Click to expand...
Click to collapse
I am using tgz file to flash.Although the flashing is shown success but the mobile doesn't restart after the flash by itself.When I restart the phone it restarts by itself at MI log with Android logo at bottom.
I have tried flashing recovery from from TWRP also but similar error.
varin11 said:
I am using tgz file to flash.Although the flashing is shown success but the mobile doesn't restart after the flash by itself.When I restart the phone it restarts by itself at MI log with Android logo at bottom.
I have tried flashing recovery from from TWRP also but similar error.
Click to expand...
Click to collapse
Lol. After flash.when u restart phone the phone will start at android logo.
What u expect? haloween logo?
Then keep it on android logo for 15min. It will boot into miui. Leave it for 15 min.
Why did u flash twrp before? after flashing fastboot rom phone should boot into miui . just leave on android logo for 15 min . It will boot into miui.
http://bigota.d.miui.com/8.11.22/ke...22_20181122.0000.00_6.0_global_b2a5c7e388.tgz
naik2902 said:
Lol. After flash.when u restart phone the phone will start at android logo.
What u expect? haloween logo?
Then keep it on android logo for 15min. It will boot into miui. Leave it for 15 min.
Why did u flash twrp before? after flashing fastboot rom phone should boot into miui . just leave on android logo for 15 min . It will boot into miui.
http://bigota.d.miui.com/8.11.22/ke...22_20181122.0000.00_6.0_global_b2a5c7e388.tgz
Click to expand...
Click to collapse
U r right but in my case the mobile reboots itself once it reaches the Android logo.
Updated TWRP and finally could install RR rom based on Android 8.1. Great rom better than MIUI and don't want MIUI now. Thanks for the help guys.
I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Bkeinn_ll said:
I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/android-12-up-and-running-on-xperia-1.4331341/
I think you should take a look of this post.
In theory this would be the post I needed, but following this guide, with their files, made my Xperia 1 not even show the Rom’s Boot animation and instead ended up in a boot loop which stopped ~2 sec after showing the Sony logo.
But nevertheless thanks. I will ask in this post for help.
Try using fastboot method to install GSI ROM.
See this thread for reference : https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4128911/
Thanks, I did it.
What did I do different:
vbmeta.img from google(was a little bit bigger than the one from the TWRP)
Started from Android 9(directly from Emma)
Flashed system.img as well as vbmeta to system_a system_b/vbmeta_a, vbmeta_b
i have the same problem till now i cant flash any gsi i flashed android 11 and flashed after that vbmeta to a and b and flashed system.img and got infinite loading