Flash the zip and fix
200+ download & only 3 thanks
Not quite sure if it is for CM12? Or for CM11 after coming back from CM12?
Please explain whether it is for CM11 or CM12, and what it does?
AlphaX2025 said:
Please explain whether it is for CM11 or CM12, and what it does?
Click to expand...
Click to collapse
A logo.bin included
AlphaX2025 said:
Please explain whether it is for CM11 or CM12, and what it does?
Click to expand...
Click to collapse
There's a glitch on the latest CM 12 nightly that makes the splash screen glitchy as hell. The .zip patches the splash screen and makes it normal again.
So, this works on CM12 to fix that. Can this be used to flash any other logo.bin or just the stock one?
I ask this because there are people running into hardbrick trying to flash a different boot logo on CM12.
sidharth.gtm said:
Flash the zip and fix
Click to expand...
Click to collapse
Thanks so much for the fix, that buggy splash screen was driving me nuts...
I was just wondering if I have to flash this fix everytime I install a new CM12 nightly?
sahilarora911 said:
So, this works on CM12 to fix that. Can this be used to flash any other logo.bin or just the stock one?
I ask this because there are people running into hardbrick trying to flash a different boot logo on CM12.
Click to expand...
Click to collapse
this is different from stock one although looks same . at code level stock one is almost 9 mbs and this one 364 kb .
if u ever installed cm12 or color Os (which causes red logo) using command flash logo logo.bin will brick ur devices.
so this is only fix .
sahilarora911 said:
So, this works on CM12 to fix that. Can this be used to flash any other logo.bin or just the stock one?
I ask this because there are people running into hardbrick trying to flash a different boot logo on CM12.
Click to expand...
Click to collapse
sahilarora911 said:
Not quite sure if it is for CM12? Or for CM11 after coming back from CM12?
Click to expand...
Click to collapse
glitch will be fixed or may have been fix . but people who just installed cm12 for testing and went back 2 cm11 remained with this glitch , so this zip can fix that too
OK. Thanks for clearing that up.
Do you have any idea as to why we are not able to flash a different Logo.bin on CM12, when they use to work fine with CM11. Did something change in Lollipop?
thanks
This worked fine...
djzero86 said:
This worked fine...
Click to expand...
Click to collapse
Then when I restore from CM12 to CM11, after flashing this mod can I use command flash logo logo.bin and I will not brick my device?
RIGHT???
track909 said:
Then when I restore from CM12 to CM11, after flashing this mod can I use command flash logo logo.bin and I will not brick my device?
RIGHT???
Click to expand...
Click to collapse
flashing this mod will solve your screen glitch.
but never use command flash logo logo.bin
it will brick your device
sidharth.gtm said:
Flash the zip and fix
200+ download & only 3 thanks
Click to expand...
Click to collapse
Worked well! Thanks!
I don't understand why logo.bin is different in CM12.
If logo is the same there would be no problems.......
sidharth.gtm said:
Flash the zip and fix
200+ download & only 3 thanks
Click to expand...
Click to collapse
Thank you.
Worked on OnePlus 64GB running bacon NIGHTLY 2015-02-03
Thanks for this, it worked perfectly
Worked fine for me too, thanks!
OPO 64gb @ cm12-20150204
Worked perfect. I'm a little OCD, and the chopped off text was grating on me. Thanks!
Thanks a lot. It works for the latest builds, but i have to flash this every time I update those nightly build. Is there anyway to fix this completely?
Related
Hi there,
installed lastest hellybean (Hellybean-20130114-galaxysmtd) successfully. But after rebooting device i stuck in CM boot logo forever.
Putting off battery and trying to get in CWM also does not work.
Any tipps?
thanks,
warper
warpers said:
installed lastest hellybean (Hellybean-20130114-galaxysmtd) successfully. But after rebooting device i stuck in CM boot logo forever.
Putting off battery and trying to get in CWM also does not work.
Click to expand...
Click to collapse
What do you understand by successfully?! :silly: Could you tell more about the initial situation? Would be nice to know which ROM you were coming from for example.. or if download mode is still working.
Prince_Harming said:
What do you understand by successfully?! :silly: Could you tell more about the initial situation? Would be nice to know which ROM you were coming from for example.. or if download mode is still working.
Click to expand...
Click to collapse
I was on Helly build from 01/10/2013. Flashed 01/14/2013. Flash was successfull. Download mode still working, but CMW not.
It seems the same problem as posted from swilly (http://forum.xda-developers.com/showpost.php?p=36825605&postcount=1403)
Flashing Semaphore 2.9.5 helped me to get my device working.
warpers said:
I was on Helly build from 01/10/2013. Flashed 01/14/2013. Flash was successfull. Download mode still working, but CMW not.
It seems the same problem as posted from swilly (http://forum.xda-developers.com/showpost.php?p=36825605&postcount=1403)
Flashing Semaphore 2.9.5 helped me to get my device working.
Click to expand...
Click to collapse
I think every ROM which can be flashed via Odin would help solving this issue.
warpers said:
Flashing Semaphore 2.9.5 helped me to get my device working.
Click to expand...
Click to collapse
I see you pulled yourself up by your own bootstraps :victory: any idea what caused the problem? Did you change any values like Swilly?
EDIT:
magicw said:
I think every ROM which can be flashed via Odin would help solving this issue.
Click to expand...
Click to collapse
Yeah, that's why I asked him whether download mode's still working... but some people don't want to make such huge efforts and as we can see he managed to solve his prob
i did not changed any value like Swilly. Now i have a working device. I did not tried it anymore. Kind funny now i'am on Helly with Semaphore
For some reason I am unable to flash kernels and ROMs. I am still rooted and unlocked so I'm not sure what the problem is. I've tried both TWRP and CWM.
EDIT: I should also note that the phone reboots when I try to flash.
tkoreaper said:
For some reason I am unable to flash kernels and ROMs. I am still rooted and unlocked so I'm not sure what the problem is. I've tried both TWRP and CWM.
EDIT: I should also note that the phone reboots when I try to flash.
Click to expand...
Click to collapse
Are you also S-OFF? It really shouldn't matter, though.
Rirere said:
Are you also S-OFF? It really shouldn't matter, though.
Click to expand...
Click to collapse
No, never have.
This has happened to me before try flashing Twrp again or another thing that worked for me was flashing a Rom without a custom kernel and usually fixed the problem for me weird
Sent from my HTCONE using xda premium
dandan2980 said:
This has happened to me before try flashing Twrp again or another thing that worked for me was flashing a Rom without a custom kernel and usually fixed the problem for me weird
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
No luck. I relocked and unlocked. I tried flashing a ROM without a kernel and the same thing happens... The phone reboots. The only thing I really have left to try is to RUU back to stock and start over. I was able to flash a kernel using fastboot though.
tkoreaper said:
No luck. I relocked and unlocked. I tried flashing a ROM without a kernel and the same thing happens... The phone reboots. The only thing I really have left to try is to RUU back to stock and start over. I was able to flash a kernel using fastboot though.
Click to expand...
Click to collapse
what ROM and kernel are you trying to flash?
slimc84 said:
what ROM and kernel are you trying to flash?
Click to expand...
Click to collapse
It was just the wolfpack kernel, but I got it now by flashing with fastboot... Recovery still won't flash ROMs and Kernels though.
tkoreaper said:
It was just the wolfpack kernel, but I got it now by flashing with fastboot... Recovery still won't flash ROMs and Kernels though.
Click to expand...
Click to collapse
that is very odd. can you download twrp and flash it in fastboot and try again? I know this has been an issue on other devices and apparently it can be fixed by flashing the recovery in fastboot.
slimc84 said:
that is very odd. can you download twrp and flash it in fastboot and try again? I know this has been an issue on other devices and apparently it can be fixed by flashing the recovery in fastboot.
Click to expand...
Click to collapse
Already tried that as well.
tkoreaper said:
Already tried that as well.
Click to expand...
Click to collapse
I'm at a loss man. I've never had an issue with TWRP.
slimc84 said:
I'm at a loss man. I've never had an issue with TWRP.
Click to expand...
Click to collapse
Strange issue indeed. I ended up having to completely start from scratch to get it to work (RUU > Unlock > Flash)
tkoreaper said:
Strange issue indeed. I ended up having to completely start from scratch to get it to work (RUU > Unlock > Flash)
Click to expand...
Click to collapse
Wish I could have been more help but glad that you are good to go.
Hi,
Tried and managed to install Omni, MoKee Open sourse 4.4.2 and AOKP kitkat 4.4 without any problems. Now I really wanna try the Freexperia project rom. Seems pretty simple it´s just that I cant get into the recovery after flashing the boot.img. Tried the CM10.1 img and CM11 img but after flashing the img and tried to reboot it just doesn´t. Cant get to the recovery and don't see the freexperia logo either. Anyone can plis tell me want can be wrong??
/ CJ
Chingolito said:
Hi,
Tried and managed to install Omni, MoKee Open sourse 4.4.2 and AOKP kitkat 4.4 without any problems. Now I really wanna try the Freexperia project rom. Seems pretty simple it´s just that I cant get into the recovery after
flashing the boot.img. Tried the CM10.1 img and CM11 img but after flashing the img and tried to reboot it just doesn´t. Cant get to the recovery and don't see the freexperia logo either. Anyone can plis tell me want can be wrong??
/ CJ
Click to expand...
Click to collapse
Do you get the Sony screen at least or is it completely black. If possible re download the latest free Xperia rom again and use the mokee roms boot.Img using fastest flash the boot.img then flash the freexperia rom worked every time for me if u still encounter an issue go to the official cyanide mod page CM11 official nightlies are available give the latest build from there a shot
---------- Post added at 02:15 PM ---------- Previous post was at 02:10 PM ----------
Techpenguin5 said:
Do you get the Sony screen at least or is it completely black. If possible re download the latest free Xperia rom again and use the mokee roms boot.Img using fastest flash the boot.img then flash the freexperia rom worked every time for me if u still encounter an issue go to the official cyanide mod page CM11 official nightlies are available give the latest build from there a shot
Click to expand...
Click to collapse
Forgive my spellings autocorrect is still settling in
Fastboot*
Cyanogen*
If the free Xperia boot screen doesn't show up it means the boot.img didn't flash properly further more if you flashed the rom and the free Xperia screen still didn't come that means either you flashed it wrong which I doubt or it is a bad zip..... Therefore re download and try
Dont get the Sony logo on the screen either. I'll try the mokee img didn't occur to me. But was thinking about using the flashtool application instead of going thrue the commando tool. Yeah I think the problem that it didn't flash properly, but it's strange cuz I tried it like 10-12 times but
still can't reach the recovery and the screen just stays black and the red light is on. Any other suggestions??
/ CJ
Chingolito said:
Dont get the Sony logo on the screen either. I'll try the mokee img didn't occur to me. But was thinking about using the flashtool application instead of going thrue the commando tool. Yeah I think the problem that it didn't flash properly, but it's strange cuz I tried it like 10-12 times but
still can't reach the recovery and the screen just stays black and the red light is on. Any other suggestions??
/ CJ
Click to expand...
Click to collapse
By red light is on what do you exactly mean, is it on when you try to turn the phone on
and yeah it looks like your only option is flashtool, considering your able to use fastboot
i am guessing you will be able to get into flashmode, just flash back to stock and then you may
try copying on the rom and then using fastboot to flash the mokee boot then flash the cm rom
hope this helped
Sorry with red light I meant that when I after flashing write reboot in the command prompt and the phone tries to reboot just the red led goes and the phones stays in that position. Doesn't go on to the sony logo and so on. I've got the MoKee rom at the moment should I still flash back the stock rom or can I go right from the mokee rom and I use It's img to get to recovery?!
Thanx / CJ
Thanx man now it's all working just great, was some dum mistakes I did, thanx anyway, cheers
Chingolito said:
Thanx man now it's all working just great, was some dum mistakes I did, thanx anyway, cheers
Click to expand...
Click to collapse
LOL, alright bro have fun
New to me AHD will not boot into any custom roms, I'm confused as to why. But here's what I've done:
Root (motochopper)
Unlock bootloader
Using mythtools, flashed recovery
enter recovery, factory reset, also format /system (CWM Touch 6.0.4.4)
flash CM and Gapps
Afterwards, phone just sits at boot logo. I used mythtools to reflash stock firmware, and that boots and works fine, but when I repeat the process of flashing recovery and flashing a rom, the phone will no longer boot. What am I misssing?
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
quasihellfish said:
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
Click to expand...
Click to collapse
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
mustafu said:
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
Click to expand...
Click to collapse
M8 should work. It's still JB bootloader compatible.
palmbeach05 said:
M8 should work. It's still JB bootloader compatible.
Click to expand...
Click to collapse
Same goes with validus 6.0
It's like fastboot isn't working...keep trying to flash recovery from it and it doesn't seem to work. Going to check those threads.
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Which recovery are you using?
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
bylithium said:
Which recovery are you using?
Click to expand...
Click to collapse
CWM Touch 6.0.4.4
quasihellfish said:
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
Click to expand...
Click to collapse
Thank you, will give it a try.
mustafu said:
CWM Touch 6.0.4.4
Thank you, will give it a try.
Click to expand...
Click to collapse
I recommend philz. What rom are you flashing?
bylithium said:
I recommend philz. What rom are you flashing?
Click to expand...
Click to collapse
Was trying unified CM M8 still.
mustafu said:
Was trying unified CM M8 still.
Click to expand...
Click to collapse
How did philz go for you? I'm running sokp ?
bylithium said:
How did philz go for you? I'm running sokp ?
Click to expand...
Click to collapse
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
mustafu said:
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
Click to expand...
Click to collapse
Damn, I've messaged you.
So after a little this and that, I've realized that the md5 of the ROM isn't matching anymore, and no matter what browser and how many times I download the ROM, the md5 will now never match. Using the md5 checker on PhilZ latest. The gapps match every time when I check.
I've been using my Kingston SD card to store the ROMs and gapps, will try storing them on the phone and see how it fares.
Sent from my MB886 using Tapatalk
It's working now. Flashed the ROM, phone sat at the boot logo for 20 minutes, then the cm boot animation came on and booted from there. This is the 3rd AHD I've owned but the 1st to have this very strange behavior.
Hey everyone , i could really need some help
I have a samsung Note 5 SM-N920P i rooted the device and everything went smoothly but after a week the phone reboots and got stuck on a bootloop i flashed a 5.1 and 6.0 , 7.0 ROMs but nothing works it's been 10 days since this happens and now ANY RECOVERY! custom or stock , every time i boot into recovery it freezes after 10 seconds
Does anyone plz knows how to fix this
Moonshodw said:
Hey everyone , i could really need some help
I have a samsung Note 5 SM-N920P i rooted the device and everything went smoothly but after a week the phone reboots and got stuck on a bootloop i flashed a 5.1 and 6.0 , 7.0 ROMs but nothing works it's been 10 days since this happens and now ANY RECOVERY! custom or stock , every time i boot into recovery it freezes after 10 seconds
Does anyone plz knows how to fix this
Click to expand...
Click to collapse
Flash a different boot.img.
Hey @MrMike2182 thanks for replying
A noob question haha
What do u mean by different boot.img. , like different rom or extracting the boot.img from the rom and flash it ?
Moonshodw said:
Hey @MrMike2182 thanks for replying
A noob question haha
What do u mean by different boot.img. , like different rom or extracting the boot.img from the rom and flash it ?
Click to expand...
Click to collapse
There's usually different boot.img in Stock firmware and other devs usually create their own and put them on here for others... Try using a different one.
MrMike2182 said:
Flash a different boot.img.
Click to expand...
Click to collapse
MrMike2182 said:
There's usually different boot.img in Stock firmware and other devs usually create their own and put them on here for others... Try using a different one.
Click to expand...
Click to collapse
Ok I'll try it and hopefully it works
If you don't mind me asking , why do u think is causing the recovery to freezes after couples of seconds ?
Thanks for ur time
Might be a stupid question.
Moonshodw said:
Ok I'll try it and hopefully it works
If you don't mind me asking , why do u think is causing the recovery to freezes after couples of seconds ?
Thanks for ur time
Click to expand...
Click to collapse
But have u tried to flash a new recovery thru odin yet? Maybe a updated twrp?.
pacods61 said:
But have u tried to flash a new recovery thru odin yet? Maybe a updated twrp?.
Click to expand...
Click to collapse
Yes , i have tried to flash TWRP recovery from every version available same issue , and the stock recovery also freezes
I don't know what to do at this point , do u think it's a hardware problem that causing this ?
Flash an up to date Rom form sammobile and reboot to recovery (original) and clear data and cache then reboot
olojotob said:
Flash an up to date Rom form sammobile and reboot to recovery (original) and clear data and cache then reboot
Click to expand...
Click to collapse
I have tried this many times , no luck
Thanks for reply
Moonshodw said:
I have tried this many times , no luck
Thanks for reply
Click to expand...
Click to collapse
Try downloading pit file for ur exact model and flash it with ur Rom..