----FIXED----- dunno how to delete posts
---- did specific combination of keys = power+vol_up till the screen turns black, power+vol_down after that, and all keys together till recovery mode boots up. Took me quite a bit of tries, reseted to stock and went on with flashing again from there ----
Hello all,
So I'll start off from the beginning. I was updating my 3.6 Havoc custom OS to the latest 4.2 Havoc custom OS. I started off with making a backup, went on with the data reset, booted into TWRP and flashed the v4.2 img on slot B. And then I booted into the system instead of rebooting into recovery, without Magisk flashed. I feel like not having Magisk flashed is the real culprit here. Please enlighten me on this topic if I'm wrong.
So the problem is that I'm stuck in an endless "bootloader in unlocked", tried out the combinations of pressing P+V_UP and P+V_DOWN, tried out pressing all 3 (P, V_UP, V_DOWN) buttons at the same time, also ADB and fast boot are not detecting the device, so I have no way of entering TWRP again. Please please please help me in fixing this
I have read many articles trying to find a solution to my problem, and none seem to be an closely related to my problem, please guide me to the thread if it already exists. Im on a Mac OSX so MSMtool won't be any help of me.. I would really really apreciate an urgent reply.
Thanks in advance.
Related
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
help needed !!
I have a KFHD7(tate) and had been running CM12.1 for a while with only an occasional update using the nightly builds, I only updated occasionally as the unit would not always turn on at the first attempt and would stick at the CM boot logo, after switching it off and back on the unit would run quite smoothly, however none of the updates seemed to cure the problem.
I noticed that there was a new release 'cm-13.0-20160218-UNOFFICIAL-tate' which I flashed via TWRP along with 'open_gapps-arm-6.0-stock-20160301', these were flashed at the same time.
after a reboot the KFHD7 worked fine with no apparent problems, I then downloaded one of the dark themes,(not sure exact one) and this seemed ok at first, I entered the settings screen and only a few words and graphics were visible!
I rebooted back into TWRP recovery and performed a factory reset from within TWRP ... big mistake, now the unit only boots to the blue TWRP boot screen and blinks off after a few seconds it is stuck in a loop and I dont know how to recover it, I have tried the usual combinations of holding the power and vol buttons but still comes on the same .. any suggestions would be appreciated (dumbed down solutions please as not that techy, but can muddle through if step by step instructions)
Hello,
Welcome to XDA.
Try posting your issue in the thread linked below that you got your ROM from.
http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-marshmallow-t3315075
The experts there may be able to help. Good luck.
Hi Friends,
I installed cm-13.0-ZNH0EAS2JK and it was running fine but today something weird happened. I rebooted my OPO and it got stuck in TWRP recovery.
No matter what I do, after powering up, it goes to TWRP recovery. I tried to installed another ROM also, but that also didn't helped.
Can someone please help me out over here?
Flash the COS 13.1 fastboot zip using bootloader...
deepakaryan1988 said:
Hi Friends,
I installed cm-13.0-ZNH0EAS2JK and it was running fine but today something weird happened. I rebooted my OPO and it got stuck in TWRP recovery.
No matter what I do, after powering up, it goes to TWRP recovery. I tried to installed another ROM also, but that also didn't helped.
Can someone please help me out over here?
Click to expand...
Click to collapse
I've got the same problem as you, but different build of cm13. Nothing I've tried has worked. Is there something wrong with your volume button by chance? I've researched this issue thoroughly, and that seems to be the common denominator. Apparently the volume button is somehow being pressed, and making the phone boot into recovery when powered on. If you figure it out let me know. It's the bane of my existence right now
Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you
Hello all
First off I'd like to say thanks to this site (it enabled me to root and custom rom my G6 plus that I have passed on - hence I want to do the same to my G7 Power)
Panicking slightly as not sure how to correct and it's semi bricked. Tried to install CRdroid but that gave me no end of trouble with looping. installed Havoc OS fine, but somehow managed to boot back to it before installing gapps. Not a problem I thought just reboot into TWRP and redo the whole lot. Only now TWRP is unresponsive. Tried restarts and all sorts. cannot got TWRP to do anything.
Any advice appreciated - let me know what info you need.