Hey there people, new here to these forums and I hope that you can assist me (cause let's face it, I'm a noob).
I tried to flash my Optimus2x with CM7 last night and everything went fine according to the phone.
When I restarted the phone, all it does is show the CM7 logo for a couple off seconds and rebooting... and keeps on repeating itself.
I've tried to connect it to the computer, the lg-update program says that there is a new update available but I only get to 25-30% before it comes to a halt...
I used ROM manager to do the flashing,I installed Clockworkrecovery and so on.
Is there anything I can do, or am I stuck with this loading-screen forever :<?
Related
I played with my Defy today, installed Froyo on top of the Eclair stock, didn't like it, tried to install eclair again didn't work. I tried Cyanogen on top of Froyo using 2nd init, went ok, but had some problems in the applications drawer, tried to install Cyanogen again then everything went really bad.
I am now stuck with the Motorola red logo at the startup, can not even open the stock recovery.
What do i do?? Is my phone bricked?
Hady
Well, some days ago i was trying some changes like you, and i messed my phone, and just the M logo was showing, don't even turn off, need to take batt off.
What i do to revive, is to reflash and .sbf file similar from what i have before install the CM7 (i don't using anymore). Reflash with the RSD Lite, in the Bootloader screen (power+vol up).
Now is good again
Hey all
I've encountered a very weird problem today.
I don't know how, but this morning i woke up ontop of my phone (yeah i know xD), which was extreemly hot & stuck at HTC-logo screen.
I quickly took out the battery and let it cool down, but after i tried to reboot, my red led starting acting really weird..
When i tried to boot, it was stuck at the HTC-logo, so i tried another boot, which also failed.
I then tried to go to my recovery menu, but the same thing happend --> stuck on HTC-logo.
Fastboot on my pc does recognize the device, but i can't seem to install a new rom trough the fastboot menu
I now installed a RUU in hopes of restoring, but still no luck..
Can anyone help me out?
i'd be most gratefull!
BTW, i was running sabsa prime V12 for 2 weeks without issues.
stryker000 said:
Hey all
I've encountered a very weird problem today.
I don't know how, but this morning i woke up ontop of my phone (yeah i know xD), which was extreemly hot & stuck at HTC-logo screen.
I quickly took out the battery and let it cool down, but after i tried to reboot, my red led starting acting really weird..
When i tried to boot, it was stuck at the HTC-logo, so i tried another boot, which also failed.
I then tried to go to my recovery menu, but the same thing happend --> stuck on HTC-logo.
Fastboot on my pc does recognize the device, but i can't seem to install a new rom trough the fastboot menu
I now installed a RUU in hopes of restoring, but still no luck..
Can anyone help me out?
i'd be most gratefull!
BTW, i was running sabsa prime V12 for 2 weeks without issues.
Click to expand...
Click to collapse
I've slept on my phone many times but this has never happened to me o,O
By acting weird could you elaborate? Does it flash repeatedly?
If not, access HBOOT and then go into recovery
the led was flashing lightly and than fast, but now my led turned orange, continues.
Even when i unplug the phone out of the charger, the led stays on.
I tried accessing recovery, but it just hangs at the HTC logo.. I'm getting out of ideas
Battery pull and then try it? Sounds like a HW failure. Post on the Ace Think Tank in my signature and Glevitan will probably help you
If I helped, hit that thanks button!
HTC Desire HD (IceColdSandwich)
Samsung GNote 10.1 (Stock Awesomeness)
already tried that one hundred times
Well thanks, i hope i can find my answer there.
Hi all,
Earlier today I was having issues getting an icon pack to work, so I decided to uninstall, then reinstall the application.
I suppose I should have switched my icon pack before uninstalling it, but didn't expect that to create any problems. Well, everything immediately started forceclosing and my phone went into a bootloop.
I proceeded to do a battery pull and attempted to get into recovery. Unfortunately my phone didn't respond.
I can hold down the power button for a whole minute without the phone vibrating even once now. The screen is totally off no matter what I've tried and should I plug the phone into my computer I get a "Device not Recognized" error.
No charging icon when plugged in either.
I also tried using Wugfresh to reinstall drivers- so far no luck.
Does anyone have any advice? Or is it time to start looking for a new phone?
Thanks all.
(If it matters, this is a GSM Galaxy Nexus which was running the latest PA. Stock kernel, no OC/UV.)
------------------------
Edit: Nevermind. My JIG got my into download mode, and now recovery. That fixed it!
Tried everything I could find, so decided it was finally time to come here. I was happily running CM11 for more than a year and saw that CM12 was available. Used the CM app on my phone, did the whole Windows part, the update started, then failed. Now my phones boots and gets to the first screen after, and for hours the arrow spins round and round.
Tried Vol+/Home and Power, the screen flashes something real quick and it reboots. When I try the same with Vol-, I get a screen that says it's downloading, but nothing ever happens. I'd be happy getting the stock Samsung ATT ROM, CM11, anything so the phone would work. I even tried seeing if I cold flash various other ROMS with Odin to no avail. Must have brain damage (exhaustion) because Odin isn't seeing the file it wants in any of the ROMs I've downloaded.
Thanks in advance.
Before flashing anything else, flash back to cm11 and confirm the bootloader currently installed on the phone.
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)