Database Info

[Q] Screen won't turn on after trying multirom wrong way

Hi everyone. I have a problem and i hope i can get the solution from you guys.
My oneplus one screen won't turn on manually, either double tap or power button. sometimes i try it randomly and repeatedly with tapping the screen and power button and suddenly turn on. but when the screen turn off (manually or automatic turn off), it won't turn on again.
My phone can still receive call, notification, etc but when trying to turn it on, futile. I try to trigger it with charging it and it's work. but when it turn off, it won't turn on again. i can plug/unplug the usb to turn it on, but i won't do that because you know why.
This is happened when this morning i want to try to install colorOS (http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853) and calkulins cm11s rom (http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365) in multirom using this guide (https://forums.oneplus.net/threads/...ere-are-my-samples.176376/page-3#post-8703604).
My rom at that time are already on calkulins cm11s. but the bad thing is i forgot that my kernel are franco kernel r34 while multirom need kernel with kexec hardboot.
this is my step by step how can i get this:
- nand backup the current rom (calkulins cm11s)
- wipe, flash colorOS
- install multirom manager, download multirom and the recovery without cm11 kernel. reboot recovery
- add rom using my last backup, reboot to colorOS
- install cm11 kernel from multirom manager, reboot.
- try booting to cm11s but won't boot. hard reset and try booting again. it work. play it quite a while. try to turn it on manually but failed. REALIZED that i'm still using franco kernel. reboot recovery. (the problem start from this step)
- wipe 2nd rom, add rom without using backup, same problem (cannot turn on manually).
- wipe 2nd rom again, wipe colorOS, restore backup without add another rom, same problem.
- uninstall multirom, install twrp, restore backup, same problem.
- install new rom without backup, for 15 minutes is working and then same problem.
- Now i'm charging my phone because it's out of battery.
Can someone help me?? and i'm sorry for the long post and maybe for my bad english.

Currently I try flashing colorOS and everything work normally. Can I assume that maybe some colorOS setting stuck on the phone and made the cm11s rom behave like that? and if it is, how can i remove it?

Same Issue
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings

g.tscharf said:
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings
Click to expand...
Click to collapse
worked for me too

flash color os 1.2 (Android 4.3) and flash CM11S

[SOLVED] [help] Phone stuck after flashing CM12

[SOLVED]
Hi guys,
This morning I decided to flash the latest CM12 on my N5. I wiped system, dalvik and cache and i flashed the ROM after a data backup (my bad I forgot to backup system). The CM logo appeared and it did optimize the apps. What I got now is a black screen and the "go back" button. My idea is that I forgot the gapps but now I don't know how to pass them from the PC, the USB-OTG doesn't work, my pc doesn't recognize the phone as a MTP nor a mass storage device but i can hear the sound windows make when a new device is detected.
I was on stock 5.0.1
Is there a solution? Please tell me there is!
Thank you very much,
Bovotech
EDIT:
I found the solution, I didnt factory resetted the phone.

Bovotech said:
Hi guys,
This morning I decided to flash the latest CM12 on my N5. I wiped system, dalvik and cache and i flashed the ROM after a data backup (my bad I forgot to backup system). The CM logo appeared and it did optimize the apps. What I got now is a black screen and the "go back" button. My idea is that I forgot the gapps but now I don't know how to pass them from the PC, the USB-OTG doesn't work, my pc doesn't recognize the phone as a MTP nor a mass storage device but i can hear the sound windows make when a new device is detected.
I was on stock 5.0.1
Is there a solution? Please tell me there is!
Thank you very much,
Bovotech
EDIT:
I found the solution, I didnt factory resetted the phone.
Click to expand...
Click to collapse
Please add [SOLVED] to the thread title, @Bovotech

Need help with a hard bricked phone

Hi people. Today I needed to install a file inside system/etc/permissions to enable OTG Host. Since I couldn't create a file there, I had the stupid idea of changing the permissions of the system folder. I changed it with root browser, to Owner: read/write/execute (the other stuff was unchecked). My phone turned off instantly, and now it wont turn on at all. Seems like I'm in big trouble. Still, I want to ask if something like that is recoverable somehow, and if anyone can point me in the right direction.
Phone: Samsuing A5
OS: Android 6.0.1
Root: Yes (systemless, with Odin)
Custom Recovery: No
Edit: I just connected the phone to my PC, and it detected a USB device called SAMSUNG_Android. It's weird, the phone seems to be off. Kinda gives me a bit of hope, but I'm a noob with these things.
Edit2: I waited a few minutes and tried to turn it on again. It worked! But now it boots to recovery, so it seems to be a soft brick. Factory Reset doesn't seem to do anything, I guess I'll have to flash a ROM. But I have no idea how to do that. Any help?
Edit3: With the help of a friend, I installed TWRP custom recovery, and used it to flash a Resurrection Remix ROM and GApps. However, I cannot make it reboot into system. It always goes to recovery. When booting, it shows the message "Recovery is not Seandroid Enforcing", and then opens TWRP recovery. I can see my device has a system folder with stuff in it, but I can't make it boot properly. Any suggestions?

Lenovo Vibe X3 restarting automatically.

Hi All,
My friend's Lenovo Vibe 3 was working properly but it started giving restart problems automatically. It was working perfectly fine but now it just starts and restarts and nothing else. I even tried to go into safe mode to do some changes in settings and try to the pull the data from the device but it restarts there also, all I want is the data thats it.
I can not install the custom ROM also in this device because of this condition.
Very long time back I used SP flashing tool just to install the custom recovery in my Mediatek device and in there I guess I was able to see some options to copy the data from phone's internal storage to the SD card, correct me if I am wrong because I did it long time back.
So is there any way just to install the custom recovery without wiping all the data in Snapdragon devices also ???
I read somewhere that if I try to unlock the bootloader that will also wipe all the data but the thing is I cant even go to fastboot mode, is there any alternative way to just install the custom recovery with all my data as it is ?

Oppo R7S - ROM installation crashed, cannot get back to recovery mode, keeps crashing

Hi there,
I am a newbie and hoping that someone could help to give me some clear pointers about options that i could take to rescue my phone - I hope its not bricked.
I was attempting to install LineageOS 16 on my Oppo R7s. This is my second attempt at installing a ROM - I did it a couple of weeks ago with Project Spectrum, and it worked, but Project Spectrum didn't impress me, so i wanted to try lineage OS instead).
I entered developer mode and enabled USB debugging
I downloaded the LineageOS zip to my SD card, as well as a Google Apps zip.
I downloaded the TWRP app on my phone just in case it was needed, however I've never used that app and not 100% sure how to use it.
I rebooted in recovery mode, and tried to install from the LineageOS zip file. It didn't start installing, I got some error message which I cannot recall... so I tried wiping the application data first, to see if that would help (maybe that was my mistake??)
I then went back to the install menu, and tried to install the Google Apps package first.... it started downloading, but then crashed and black screened.
Now, when I try to power on the phone, I get the oppo logo, and then it briefly goes back to the install screen for a second, with a message on the screen saying: "updating please wait, do not remove battery, do not co other operations" - but this only lasts for a second, then it crashes.
When I try to reboot into recovery mode (Power key +volume down), it does the same thing. I cannot get back to the white recovery menu.
Is there any way that I can rescue the situation and get back into recovery mode to try again? Or get back to a functioning USB connection so I can load a new ROM zip to try that instead?
When I plug it into the power, I get no indication that the phone is charging.
I'm worried the battery will go flat.
I have ADB installed on my computer, but I dont really know how to use it - the only command I know is "adb push" to load the roms onto the SD Card
Any advice on how to get access again would be greatly appreciated!