Long story short, all my apps kept forcing close at work one night, rebooted phone, got stuck at Cyanogen 6 boot screen every time I tried to boot. Wiped the phone and reflashed Cyanogen 6, phone boots but now I can't connect to ATT (phone is unlocked). Tried reinstalling CM6, CM5 and SuperF, nothing. Opened phone up to check the radio cable, disconnected and reconnected it, nothing. Wiped the phone via fastboot and reflashed the radio, nothing again. The SIM works fine in other phones and worked fine on this phone for about 2 months. Anybody have any idea what is going on. Could my radio chip fried itself somehow? The wifi works fine, phone works fine, just can't connect to ATT.
Related
Hello,
I tried flashing the radio on my hero for the first time. So I downloaded the GSM (my hero is a GSM one) 63.18.55.06JU_6.35.09.26 radio in a zip format and updated it through the recovery mode. The update seemed to go fine, the progress bar ended, and my hero rebooted. It booted into the recovery mode though, so I selected the reboot option to bring it back to the regular interface.
Now however, it's stuck on the HERO logo and I have no idea what to do. It's been like that for over an hour.
Can anyone offer any words of advice?
I just pulled the battery out, figuring that if 1 hour wasn't enough for it to do whatever it needed to do, then it was surely just stuck. And now it booted just fine ... I just freaked out, since this is my first radio flashing and it definitely looked borked.
wow you got lucky, after pulling out the battery it worked fine.
I bricked a Dream while updating radio and i had the same issue after the reboot it was stuck on the boot screen.
Good thing it wasn't my dream.
My s4 has been doing this since yesterday where it shuts off and wont be able to turn on. It happened once yesterday and I booted to recovery and wiped data and it fixed the issue. I updated my phone today with odin to ND1(I have a US Cellular s4) and it seemed fine. It shut off randomly once and I didn't think anything of it and it booted up fine. I flashed the Cyanogenmod may 3rd nightly and it was working just perfectly with no problems.
Later today I take it out of my pocket and it wont boot. Cant get to recovery, or download mode. All that happens is it flashes the boot screen for a second or two then goes blank.
Could this be a hardware problem?
If not any idea how to fix this???
purchased a new Galaxy S4, from sprint.
rooted using auto-root and installed teamwin recovery. all good. kept using the phone flawlessly for three days.
was going to flash CM10.2 through the recovery when i noticed the big button in the CyanogenMod home advertising the installer.
since this phone is compatible, then decided to try that.
CM11 installed right away and worked great, charged the phone, took a couple pictures, great.
then an update was requested to the ROM, so i installed it.
that update resets all my settings, so i started downloading all my apps and applying the settings again.
when the phone was around 18% of charge, i plugged the phone and nothing happened.
tried another phone with stock android in the same charger and everything went well fine so, i turned off the
SGS4 and plugged it again.
it vibrated once, (like it was about to start charging) but nothing happened. a few seconds later, it vibrated again, and that went on and on...
turned back on the phone in recovery, i noticed that TeamWin was replaced by ClockWorkMod recovery.
wiped Dalvik, cache and did a factory reset. turned phone back off and plugged the charger.
now it vibrates once, the screen lights up, a drained battery shows up and nothing happens, (just like it froze there).
the phone is not taking charge and its dead jim. doesn't have enough charge to power on.
havent tried anything else.
any clues or workarounds?
please and thanks.
EDIT: downgraded to CM10.2.1 and installed chronic kernel for CM10.2, problem solved.
Hi! I got my Essential Phone from someone that had it boot loader unlocked etc. I have experience with flashing and all so it was not a problem for me. Yesterday when I got the phone I went here and flashed AOSIP Rom again since it was the one it had but a wanted to make sure to have a fresh install etc. All working fine by then until about an hour ago the phone turned it self off and now it doesn't do anything. Every time it finally boots it shuts down again. If I try and enter recovery or Bootloader for fastboot, same thing. Sometimes it holds up for about 20 seconds and goes back to Off and be unresponsive for a period of time.
Has anyone had this problem before? If so, is this a Hardware problem?
I can't fix it by computer so I don't know what I am into right now. Its the only phone I have so I'm kind of stressed right now
I used to have a Pixel 5 phone, which unfortunately was run by a truck and now I am stuck with an old Samsung Galaxy S7 Edge phone. I have decided yesterday to install Pixel Experience on it and it all went fine. I have unlocked the OEM, enabled USB debugging, installed the latest version of TWRP with heimdall, and sideloaded the Android 11 Pixel Experience Plus ROM.
I had done a full wipe of the phone before doing it, including the system, etc. I have then recovered from the backup from my Pixel, and it installed all apps. Then I saw that there is a new version of the Pixel Experience, installed it, and plugged it into the charger and I woke up at the Google logo. I disconnected it from the charger and the Google logo was still there, it took me a couple of minutes to switch it off while holding continuously the power button.
I tried to go into recovery or download mode without any success. Then I have connected it to the charger again and I saw the battery indication with lightning inside, but normally it also shows you the battery percentages but this time, it didn't. I have then tried to connect to my PC, thank God this time, it booted straight into recovery. I have tried to sideload again the ROM, and this time, it worked till the end, but then I was unable to slide the slider to unlock it and restart the phone. Then switched it off and tried once again to sideload it, this time the phone died at half of the sideload. I am completely desperate now. Am I doing something wrong?