I noticed recently that when booting up my OPO I see the 1+ logo, however there is a text in the bottom that is cut off.
I noticed this after flashing the Sabermod ROM, but now I have flashed back to BlissPop ROM. There is no issues with the phone or recovery, everything works fine, however its just that boot logo.
Is something wrong with my bootloader or is the boot logo corrupted? See the pic attached.
Don't worry too much, it's due to a bug in the recent CM12 code, I'm sure it'll be rectified soon.
Transmitted via Bacon
I had this issue also but it doesnt affect your phone...
Flash new firmware... I got it from katinatez server... works good...
Okay great! I thought some how I corrupted part of my phone's partition or something.
I thought I messed up my phone too lol but like timmaaa said it's normal, CM did this themselves don't worry about it [emoji106]
Sent From Lollipopified Bacon Goodness!
150206 night bulid had fixed it.
happens to me too with BlizzPop
I did a clean flash of BlissPop's latest ROM (2/11). The corrupted boot logo is still there... If BlissPop's 2-11-15 release is more recent than the CM 150206 nightly buid, doesn't that mean the bug should be fixed?
Related
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.
i recently flashed cm 10.2 unoffical build on my p5110 but finding that the SIM card was not working, i tried to flash cm 101.1 stable. NOw i am stuck on boot up(blank screen... not even boot animation). Tried clea wipe and flash it over and over, even after /system wipe, does not seem to work. How to fix this?
That looks really bad. It may be permabricked. Just guessing but i hope not.
I think the sim card issue was 10.2 related I've seen in the note2 forums some people have no data. Not sure if that's the same with the tab2 cause I haven't researched 10.2 for mine yet. Are you able to turn off and get to download mode? Maybe try to odin back to stock and see if this will work to fix. Never seen a screen like that so I'm kinda shooting ideas right now but anything is worth trying at this point right
Sent from my SCH-I605 using xda app-developers app
agent47er said:
i recently flashed cm 10.2 unoffical build on my p5110 but finding that the SIM card was not working, i tried to flash cm 101.1 stable. NOw i am stuck on boot up(blank screen... not even boot animation). Tried clea wipe and flash it over and over, even after /system wipe, does not seem to work. How to fix this?
Click to expand...
Click to collapse
enter download mode and flash stock samsung firmware via odin(you can find firmware on official samsung site)....you have a lot tutorials how to do that,just searc a bit....follow titorial to the letter
Hi all,
Was wondering if anyone else is experiencing the same problem? My OPO has no backlight after it boots up. The backlight is fine during the initial boot up (the powered by android page) but it disappears right after that page. Everything else works fine! How do I know? I shine torchlight onto the screen and I can see the LCD pixel to be working but NOT the backlight. Any help? Thanks!
Unlocked and rooted with CM12 nightlies installed before backlight disappeared. Done everything suggested for corrupted memory, bootloop, hard bricked etc. I am currently on stock unrooted CM11s with stock recovery.
How did you flash CM11S back onto your device?
Transmitted via Bacon
Fastboot mode, unzipped CM11S and flash images.
You flashed everything from within the stock image zip?
Transmitted via Bacon
Yup I did. I followed the exact instructions for changing from colour OS to cm11s, I reckon that is the best way to restore the OPO to original state.
It definitely is. Seems like it's possibly a kernel issue, have you tried a custom kernel to see if it changes the situation?
Transmitted via Bacon
Sigh I tried both franco and boeffla and it still does not work. Thanks anyway!
If not working, I suggest you flash Calkulin's Stock CM11S XNPH44S. It's all stock with root. I always use this build when I need go back to stock, saves all fastboot hassle.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
That was what I did before creating this thread. Maybe I should play around with other CM11 roms+their other kernels see which one works
Does the backlight work in recovery?
And I assume (sounds like yes) you did a full factory reset?
Once had a similar problem caused by an 3rd-party app that controlled the backlight. If you did a factory reset that shouldn't be the case, though. logcat?
I tried franco and it works! Not sure why though. At first I was having system ui fc which is a bug with r37+cm12 roms. I reverted to cm11 roms+r37 and it worked. Still, no backlight while booting though, but the backlight turned back on once it finishes booting up. Thanks all!
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.