Ok so I installed the Chucke Rom and the Radio thing for my phone and now it is in an infinite loop when it boots up. It doesn't turn on when I don't have it charged in and when I do have the phone charged in, the Chucke Rom thing loads up the custom boot logo but then the screen goes black and does the same thing over again. This is a serious help needed because I really need my phone. Can anyone help me out here?
please delete this thread mods... i am keeping the other one with the [Q]
Related
i rooted my device and flashed a nightly build of CM 10.1. it was too glitchy for me and i saw a build that i liked more ( google editionv2) but when i tried to flash that from TWRP it would just stay on the bootloader or the GS4 screen forever. getting nervous i decided to try to fix it by flashing a .md5 fix from odin. i watched this video /watch?v=bxNPHKKpvtQ and did all the steps correctly and odin even said it passed but when i try to boot it up it goes to the GS4 screen for about 2 seconds and then turns off. and i cant even get into a twrp anymore! Is my phone dead or is this fixable ?!?!? :crying: PLEASE ANYTHING WILL HELP thank you. and i am not the most experienced with all this stuff but i know a little more than the basics so explanations in detail would be nice
Edit: when I run it in Odin and use the file provided in the video it seems to get out of the boot loader while connected and goes to the android screen with the blue square in the middle, then it goes to the Samsung logo video but then right when it seems it will work Odin says the device has been disconnected and then my s4 goes to a battery charging screen. And then Odin says it passed, but when I try to boot it up it goes to the boot loader for half a second then turns off. Did I brick my phone ?
Hello there!
Well, as the title suggests. Got a new rom onto the LeTV x600/S1. Then it was starting but not getting through the boot. Getting pretty hot after trying to boot for a hour. Also, I can't get to my bootloader anymore for some reason. It start to load but then goes to the starting of the phone and the roms start to boot. Any ideas anybod?
same issue happen,
My stuck in loop of "Letv ..." logo and trying reboot, automatically loop forever.
Just wanted to root, but got Iroot's root failed screen. After this failed iRoot screen, I re-booted the phone functioning normal. then I put in charger for over night. but this morning it is not response.
When restart, it just loops in "Letv ..." logo forever.
Using adb devices, couldn't find the device. I tried all combination of power button with Vol+/-, same ...
Someone happen to know something similar and how to resolve? Want to know if something can do before have to send back to seller.
webster-sd said:
Hello there!
Well, as the title suggests. Got a new rom onto the LeTV x600/S1. Then it was starting but not getting through the boot. Getting pretty hot after trying to boot for a hour. Also, I can't get to my bootloader anymore for some reason. It start to load but then goes to the starting of the phone and the roms start to boot. Any ideas anybod?
Click to expand...
Click to collapse
Hi There.
I Have an HTC One M8 International Version has not been rooted just plain custom stock installed, it was working Fine, all of a sudden it went off and wasn´t able to be turned on, at this point it would just vibrates repeatedly and was flashing led indicator on green or orange (times blinking/at times solid).
I read on some other forums it might be a battery problem, so i swichted the battery with no results, kept doing the same thing. as getting deep into this some other peeps suggested it might be the screen so i changed the display.
Now, with the new battery and a new display i manage to get the screen to work but i just keeps rebboting (on htc logo) after 10 secs even if i power it off it will turn on and keeps rebooting, im able to get to hboot menu but no furthermore, wont go to recovery at all, and will restart boot loop when chose any option (fast boot, reboot or recovery).
Help please since it is not root, quite sure it hasnt been erased the rom.
:crying::crying::crying::crying:
Any help or suggestion to get it to work again, just as a factory device.
Hello guys, I have run into a serious problem here! Please help me out..
I have a GFive President G9 Android running stock Jelly Bean 4.2.1 (ROOTED). I tried to install a boot animation through ROM Toolbox app, when I rebooted it, it didnt show any boot animation and booted straight to the home screen. So I just went into the ROM ToolBox app and restored the bootanimation backup I had created earlier to get the original GFive boot animation back.
However, when I rebooted, my phone showed the GFive Logo, and after it the screen went dark( The screen is backlit but doesnt display anything). It just stops there and doesnt do anything. Ive tried removing the battery but to no avail. For some reason I CAN'T ACCESS the RECOVERY or the DOWNLOAD MODE, as holding the power button and vol up etc still ends up in the same situation - Black backlit screen after logo. The phone isnt in a reboot loop or anything, it just stops at the black screen for eternity.
THE WORST PART, this phone probably has a damaged USB port, since I was previously able to charge it via the PC, but it wasnt detected in the PC. So I CANNOT CONNECT IT TO THE PC.
So is there anyway I could get this phone back alive? Is a factory reset possible? Please help me experts!! :crying:
P.S Custom TWRP is installed, but I cant access it
So there's no expert in this whole forum who has a solution for this? Because no reply means no one has an answer..
Incase theres no way out of this, please mention that.
I have never encountered this kind of situation before.
I flashed my stock recovery and boot image.
But the problem started when I reboot to recovery.
When the phone was going to boot again. the OPPO logo displayed. But it goes off within a second. Then the logo shown again and it goes off again.
When I pressed volume-up+volume-down+power button together. The cycle of the logo stops and now it is ot responding.
Tell me have any of you encountered this situation.
If yes then please tell me how to fix it.
Thank you.
Hello,
Just to clarify: It went boot loops after you flashed or was it in bootloop and that's why you flashed?
Either way, more importantly, after flashing, it stuck in bootloop, you forced power-off and now it won't respond at all? Or if you try to power-up does it go back into bootloop? Maybe a silly question but easy to overlook when you're busy; is the battery charged?
I'm no guru, but I've been studying boot looping and soft brick situations for the last few days and might be able to push you in the right direction.