solutions the problem with the black screen in the Mad Catz m.o.j.o
The solution I found is after installing the ROM, do not restart before installing Super SU beta v268.
after installing SuperSU restart the m.o.j.o and problem solved
Related
hi all,
my mojo madcatz boots but nothing happens. it freezes on BIG RED logo madcatz...
I dont know why it worked correctly yesterday.
is it possible to hard reset or to acces in a recovery menu?
thanks
regards
I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/
I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.
Stuck on this when i boot any help?
same problem here,did u find any way to fix that?!
same here,i need your help plz developpers and members, i intalled phoenix os latest version and i tried old versions later...the story is when i installed for the first time,it boot normally on my toshiba i7 intel Amd radeon graphics,and everything works normally at the first boot, but when i restart the phoenix os without even getting inside the windows,just restarting the phoenix,it becomes to boot and the image on the screen is dissorted and black and the screen become to flash,and never boot again, i tried to change kernels, or roc , nothing change...same thing happened when i installed prime os, same thing first boot normally and after first restart same problem on the screen, it is clear that it is a developping bugs,and it is related to the screen itself or the vga,plz i need someone who can help me to solve it and to communicate with to fix this together step by step...any help, thank .
Problem solved. It was my Keyboard, tried another one and it works
Hello,
I tried to downgrade to 8.2.3 and had some problems to get it done cause of some drivers issue and in the middle of the process I reboot the system without closing the bootloader and now I´m stucked at the nvidia symbol and nothing happens.
I tried to push A and B on my keyboard (no controller at home) on thre start up process, to come back into the bootloader Menu, but nothing happens. I think because of debug isn´t enabled anymore after I opend the bootloader before.
Is there any other solution around ?
Hello guys. I do have a Gotit 2017 tv box 2gb/16 with amlogic 905-B. It's keeps rebooting before startup. It gives loading screen ( optimizing apps 0-2... ) and when it finishes, it reboots in a loop. I tried multiple roms but still the same problem. I do believe it's a hardware problem but i don't know what it may be. Does anybody encountered the same problem ? I would appreciate the help a lot.