Hi guys I need some help with getting my Bionic to boot up. I was installing the files linked in this thread: (http://forum.xda-developers.com/showthread.php?t=1594804&highlight=overclock) so I could OC my phone. I flashed the zips successfully and I rebooted my phone however it didn't boot and instead it is stuck in a black screen. I didn't disable safe system, so I am wondering if that caused it. Can anyone help?
Edit: Nevermind, I fixed the problem by hard reseting an disabling Safe System.
Related
It's been randomly crashing and and shutting off a lot lately. Today, whilst on a call, it shut off and wouldn't boot back up.
ClockworkMod still works and I have wiped boot, system, data and cache and then re-installed CM7 (the rom it was on when it died) but it hangs at the boot ani. Tried a rooted 2.3.4 and it hangs/reboots on the X.
It's had the mobo replaced a while back - could this one be dead now too? Or is there something else I can try?
TIA
managed to get it to boot again with updated hboot (spl) from here:
http://forum.xda-developers.com/showthread.php?t=744605
That's the whole problem. Everytime I reboot the phone it gets stuck at G1 screen and I have to reinstall the rom from recovery if I want to boot back into Android. This started happening a while ago and I have no idea what's causing it. It happens with every ROM. Any tips on how can I fix this? I really don't want to get stuck on G1 screen if I'm somewhere far from home where I can't fix it.
Thanks for the help in advance.
SlashSpeed said:
That's the whole problem. Everytime I reboot the phone it gets stuck at G1 screen and I have to reinstall the rom from recovery if I want to boot back into Android. This started happening a while ago and I have no idea what's causing it. It happens with every ROM. Any tips on how can I fix this? I really don't want to get stuck on G1 screen if I'm somewhere far from home where I can't fix it.
Thanks for the help in advance.
Click to expand...
Click to collapse
Have you tried flashing another kernel?
alexisguitarra said:
Have you tried flashing another kernel?
Click to expand...
Click to collapse
Tried and the problem persists.
Seems like it's fixed. I ran remove-CustomMTD_S.zip and installed the latest clockwork touch recovery. Thanks for the help anyway.
I was able to root my ME572c without issue, installed Titanium backup, removed a bunch of Asus apps, and the device was working fine. I randomly decided to restart the tablet this morning, and now it is stuck at the Asus boot screen, and It is not even going through the boot animations (no boot loop). I'm not sure what i did to make this happen. I did use ROM manager to flash clockwork recovery, and I'm not sure if i flashed the correct version.
What can I do to fix this? I can't boot into recovery mode at all, nor turn off the device.
Any help with this would be greatly appreciated.
I didn't know there was Clockwork recovery for this as I looked and couldn't find it. Do you have a link?
So I had reverted back to my Galaxy S6 today because i tried an iPhone and didn't like it. Anyways I completely messed up my phone and have no idea how to fix it. I rooted my phone then went to go get the xposed installed and i tried to install the framework and it was the wrong one and messed up my phone and put me in a black screen with a blue LED light and all i can do is go in recovery and download mode. I have searched up everything trying to find how to fix it and somewhere it said factory restart your phone under wipe in recovery mode so i did that and now it is stuck in a infinite boot loop screen where it just says the Samsung Galaxy S6 Android logo. Please help I don't know what to do.
Model: SM-G920T
MikeFe said:
So I had reverted back to my Galaxy S6 today because i tried an iPhone and didn't like it. Anyways I completely messed up my phone and have no idea how to fix it. I rooted my phone then went to go get the xposed installed and i tried to install the framework and it was the wrong one and messed up my phone and put me in a black screen with a blue LED light and all i can do is go in recovery and download mode. I have searched up everything trying to find how to fix it and somewhere it said factory restart your phone under wipe in recovery mode so i did that and now it is stuck in a infinite boot loop screen where it just says the Samsung Galaxy S6 Android logo. Please help I don't know what to do.
Model: SM-G920T
Click to expand...
Click to collapse
Wrong section.
Nevertheless, I will try to help you.
You say that you are able to boot into recovery. Did you wipe cache&dalvik after factory reset? The easiest way to uninstall Xposed is by flashing the Uninstaller.zip, which can be found in the corresponding thread.
Portgas D. Ace said:
Wrong section.
Nevertheless, I will try to help you.
You say that you are able to boot into recovery. Did you wipe cache&dalvik after factory reset? The easiest way to uninstall Xposed is by flashing the Uninstaller.zip, which can be found in the corresponding thread.
Click to expand...
Click to collapse
I wiped everything and factory reset and thats when it went from black screen blue light to blue light with logo displayed on it. I'll try to flash the uninstaller zip.
Hello today I need help with my GT-I8190 I had trouble booting into TWRP with this device. I tried many times to boot with the boot keybinds but it always seemed to bootloop, once i tried using ADB I got it to work, but something seemed off, It keept bootlooping and the hardware buttons were flashing also if it was connected to charge it wouldnt even boot. So if somebody can help me with this issue or even do something to make it better it would be helpful!
Comment:
I have realised i have installed 3 differnet twrps, I dont know how i did that but I can boot to the 3.0.1 in ADB and boot to a 2.7.1.0 with QuickBoot. Ill tell you if i find a solution
Comment 2: Now i have another problem, im stuck in a boot loop, I am using a custom rom cyangoenmod 12.1 or 12.0.
Flashed stock rom and it boot loops on there too
Sucessfully fixed this problem after a long time, Turns out the bootloader had a update which broke the recovery combination! so if you are watching this and have the same problem here is a file to fix it! (flash in BL)