Okay,
I had just restored a backup of Kagudroid, and then installed the latest RADIO.
It said update complete. I rebooted the phone to find it was bricked. Can't access recovery image or boot it up... I just get the phone out of the box icon.
Please help... what's my next step? if any...
EDIT - the dumb thing just un-bricked itself. I plugged it in, turned it on, and it showed the animation again. After a couple of minutes of me being on the phone to T-Mobile, it just turned back on...
I'm guessing the mistake was assuming that the animation of the phone coming out of a box meant that it was bricked, when actually, it was probably flashing the radio...
Have a problem...
Hi, if this problem same my problem ...
now you get in fastboot?? reboot and press back
nprussell, you are right. the out of the box sign just tells you that the radio is now "burned" to the phone. it takes a few moments, that is normal. do not ever pull the battery on that sign (unless you waited a few hours, then your phone is probably bricked).
Mine did this after installing a Radio... i **** myself.
I simply left it for about 5-10 minutes and the phone rebooted itself and booted into android no problem.
Hope the same is true for you...
Related
Hey!
Im new to this forum but there seems to be a lot of experts here so i thought i'd try and see if anyone could help me!
Yesterday i put my desire to charge and after one hour i came back and it was showing the boot screen! The white background with the 3 green letters HTC! so i took out the battery and put it in again and restarted the phone but it only gets to that screen vibrates like 10 times and then hangs there! tried waiting for it for 30 min but nothing...
So then i tried to hard reset it and cleared the storage! but afterwards still the same!
Also when in "recovery mode" i sometimes see some green text flashing by for just a sec saying something like "warning...no image...."
Everything is in its original state, i havent rooted or reflashed it or anything... but i am willing to do so if it can solve my problems since warranty matters in my case will take ages!
The phones language is Swedish btw!
Can anyone help me?? its first now that u realize how much the phone means to you Miss my desire!
it sounds like the firmware is somehow corrupted. If you can boot the phone by pressing power and volume down, this will take you to the bootloader. From here you should be able to root the handset by following any number of threads here or on modaco!
Then I'd go Here and install this recovery. From then on you can choose a custom or stock rom to install.
You need to know though that rooting will void your warranty.
Have you also tried booting the phone normally with the SD card removed?
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
you cant get into to recovery either? or fastboot mode?
k786 said:
you cant get into to recovery either? or fastboot mode?
Click to expand...
Click to collapse
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
Then I am afraid you're hard bricked pal
Sent from my GNexus
AdmiralAqbar said:
nope, when i went into recovery it went staticy again and then went back into its bootloop :/
but now it just won't turn at all, i've done a battery pull, battery swap, nothing worked.
Click to expand...
Click to collapse
what about fastboot mode?
Same
AdmiralAqbar said:
So I'm not sure what happened with my girlfriend's Gnex, she updated to 4.2 a couple days ago, then her battery died. So she went to charge it and when it finished charging, she went to turn it on normally, but it went into a reboot loop? So i was talking to someone else on another thread that i saw similar, so i tried to do a flash stock + unroot, it connected i got into recovery menu and everything, went to do it, and then the screen started going staticy, and it said it failed then it said it should take 5-10 minutes or something. So i guess it froze or something, so i took the battery out and the screen was still staticy, and then i unplugged it from the USB, and now it won't turn back on. Did i brick the device? :/ Thanks in advance for future answers.
Click to expand...
Click to collapse
I'm having a similar issue. I wanted to flash the memory so i relocked the phone using the wugkit, then unlocked and rooted. For some reason, it wouldn't load a new rom. I kept getting the triangle exclamation point android graphic. I pulled the battery and that was it. Black screen. Won't turn on. A cpl of times, it was almost recognized by the computer via USB, but just kept failing. This sucks.
cyberelli said:
just a thought: are you sure it's charged up enough to boot? i know i've mistakenly thought my phone was messed up when the battery was just dead
Click to expand...
Click to collapse
Yes the battery is charged. Occassionally, when I plug it into the computer, it makes the new device notification and then fails over and over again. I keep trying to get a glimpse of a lock so i can adb it.
Phone's been slowly giving me more and more issues. Today I was using it fine, turned off the screen, a bit later, tried turning it on and nothing. This has been a common occurrence, about once a day I have to do a battery pull or plug it in to make the screen turn on, then all is normal. Battery pull got it to boot to the splash screen, but then nothing. Plugged it in, and nothing. Left it plugged it in for about an hour, tried again, still nothing. Unplugged and tried powering on, nothing. Pulled the battery again, and could only get to the splash screen. I'm running JB Sourcery, and have the one selected where the apple rots and then it spells out droid. I get through that and then it does nothing else.
Info: just tried again, had to pull the battery, then I could get the google logo to pop up, but that was it.
Info the 2nd: plugged it in for 2 hours, the graphic showed it fully charged. So I tried booting it and again, same response..gets through the boot splash screen, but goes black after. Pressing power button does nothing, doesn't even get the charge graphic to show up.
Info the 3rd: I left it be this time thinking maybe it was just really laggy or something, but after 15 minutes, still nothing. But I can feel a bit of heat as if it is on.
Info the 4th: I can get into bootloader and recovery fine. I was even able to make a backup (only thing I could think to do in there that would take some time and not risk screwing it up more) So it's not a battery issue, seems to be something with the rom.
Please help
Even though the phone is rooted and custom rom, can I take it back to Verizon? I've only had the phone since December. If I could do that, is there any way to get all the pics off of it first?
try to flash stock image from google
Cristi_10 said:
try to flash stock image from google
Click to expand...
Click to collapse
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
VooDooCC said:
Silly question, but how would I go about getting that? And can I get it to the phone without the phone being able to boot
Click to expand...
Click to collapse
deja vu.....million times.
with a little search i found this http://forum.xda-developers.com/showthread.php?t=1626895
Was able to wipe data/cache and re-flash the rom. Seems to be working for now. I think I'll go back to stock (thanks for the link samersh) and see if I'm still having issues.
So, I flashed yesterdays CM10.2 and had no problems, up until today. I was in class, using twitter, set the phone down, and looked back at it 5 minutes later to find it shut off. I restarted it, figured no big deal, it turned off again. I thought there was a problem with that nightly so I flashed back an older, more stable one(still 10.2). It booted up, and shut off again. Now, though, the phone boots up, shows Samsung, then shows the GS3 and CM logo, then just goes into a loop from there. I went to recovery and tried to wipe, which, oddly, the phone restarted again. Luckily I was able to get in and wipe data before a new reboot, but even that didn't fix it. I rebooted into recovery again, and it said something like "root access available" and asked me if I would like to use root, which I didn't get the chance to fully read because it restarted again. When I am able to successfully boot into recovery though, I get a warning saying "no file_contexts", this could be it?
I've already tried to flash back stock Touchwiz with Odin, but it keeps failing to do so. Any help with this?
EDIT: After successfully booting up a CM10.1 backup, I've begun to believe the power button is broke, because the power menu will randomly popup, followed by a shut down.
It's called SDS sudden death syndrome it's very common on the S3. It's a failure of the power button. It's a defect. If your phone is newer than a year old put it back to stock and take it to sprint.
Remember search is your best friend, Have a great day!
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk