Hello everyone,
My wife's Razr I suddenly stopped working today. According to her, all apps began failing at the same time, giving "app stopped working" messages. She tried to shut down the phone, and it took a long time, but it eventually turned off. When she tried to turn it on again, it stayed on the red M logo.
The phone is completely stock, no unlocked bootloader, no root, no custom rom, no modifications whatsoever. It is no longer within warranty, though, and my wife has used it heavily for a couple years.
I've tried pressing:
Power + vol down
Power + vol up + down
Neither worked, resulting only on the phone vibrating then staying off. When connecting it to the PC via USB, it vibrates and shows the logo, but is not detected by the computer.
Any idea of what to do?
Thank you in advance.
If all apps gave that message, it looks like the internal memory died or is corrupted beyond repair (at least for us).
U can try to get into fastboot mode by holding "power + vol down" till it vibrates and shuts down, then release the power button and keep pressing the vol down. It will reboot in fastboot. If the M stays, I think the phone is finished.
Also does the phone still charge with the annimation when on a power plug?
Hazou said:
If all apps gave that message, it looks like the internal memory died or is corrupted beyond repair (at least for us).
U can try to get into fastboot mode by holding "power + vol down" till it vibrates and shuts down, then release the power button and keep pressing the vol down. It will reboot in fastboot. If the M stays, I think the phone is finished.
Also does the phone still charge with the annimation when on a power plug?
Click to expand...
Click to collapse
Power + Vol Down doesn't work. When charging, just like when connected to the PC, it shows the red M logo but nothing else happens.
I'm already prepared to call it dead, but if there's anything that can be done, I wanna try.
My wife phone's died, too, last night
This is an amazing coincidence. My wife phone's, heavily used for the past 2 years, started to throw a lot of app errors last night. I rebooted it, and now it is stuck during boot, cycling through "red logo" and "intel logo" - after 5-10 seconds on the intel logo, it restarts the red M logo.
I think it's an amazing coincidence, for phones to fail in the same way in the same day - probably something in the software. This phone was running 4.1.2 EU rooted, no other change. What version of software do you have ?
I'll dig a bit deeper into it tonite.
ddalex said:
This is an amazing coincidence. My wife phone's, heavily used for the past 2 years, started to throw a lot of app errors last night. I rebooted it, and now it is stuck during boot, cycling through "red logo" and "intel logo" - after 5-10 seconds on the intel logo, it restarts the red M logo.
I think it's an amazing coincidence, for phones to fail in the same way in the same day - probably something in the software. This phone was running 4.1.2 EU rooted, no other change. What version of software do you have ?
I'll dig a bit deeper into it tonite.
Click to expand...
Click to collapse
Honestly, I have no idea. I never looked into the specs and software of her phone before this happened. It's likely it was also 4.1.2 (though not EU, I'm in South America), but all I can say for sure is that it was not rooted because my wife never wanted me to mess with it for fear of me breaking it.
Maybe if I had, now I could do some recovery or something. That's irony for you.
So you're thinking of some kind of scheduled failure? That'd be really shady.
ddalex said:
This is an amazing coincidence. My wife phone's, heavily used for the past 2 years, started to throw a lot of app errors last night. I rebooted it, and now it is stuck during boot, cycling through "red logo" and "intel logo" - after 5-10 seconds on the intel logo, it restarts the red M logo.
I think it's an amazing coincidence, for phones to fail in the same way in the same day - probably something in the software. This phone was running 4.1.2 EU rooted, no other change. What version of software do you have ?
I'll dig a bit deeper into it tonite.
Click to expand...
Click to collapse
Alseid said:
Honestly, I have no idea. I never looked into the specs and software of her phone before this happened. It's likely it was also 4.1.2 (though not EU, I'm in South America), but all I can say for sure is that it was not rooted because my wife never wanted me to mess with it for fear of me breaking it.
Maybe if I had, now I could do some recovery or something. That's irony for you.
So you're thinking of some kind of scheduled failure? That'd be really shady.
Click to expand...
Click to collapse
No it's known as the superbrick. Emmc brick on the galaxy line phones. It seems that our device is suffering from it. The eemc corrupt itself and that's not repairable with software. It can be prevented, but then they need to patch the kernel of the from and the kernel in the bootloader and other stuff.
It just happens, luckily for u only after 2 years.
Hazou said:
No it's known as the superbrick. Emmc brick on the galaxy line phones. It seems that our device is suffering from it. The eemc corrupt itself and that's not repairable with software. It can be prevented, but then they need to patch the kernel of the from and the kernel in the bootloader and other stuff.
It just happens, luckily for u only after 2 years.
Click to expand...
Click to collapse
I managed to get a shell on my device (fastboot, flashed CWM recovery, got ADB shell in recovery), and it shows the internal MMC is dead. There are tons of "mmcblk0: card failures" entries in dmesg.
I called Motorola support, and they were very nice - unfortunately, the solution is to replace the motherboard, since apparently the internal MMC is soldered on. This is above £100, which makes it pointless.
I guess a dedicated developer would get Android flashed to the external MMC and configure the inittab mounts to use that instead of the internal MMC, but there is no out-of-box software solution.
ddalex said:
I managed to get a shell on my device (fastboot, flashed CWM recovery, got ADB shell in recovery), and it shows the internal MMC is dead. There are tons of "mmcblk0: card failures" entries in dmesg.
I called Motorola support, and they were very nice - unfortunately, the solution is to replace the motherboard, since apparently the internal MMC is soldered on. This is above £100, which makes it pointless.
I guess a dedicated developer would get Android flashed to the external MMC and configure the inittab mounts to use that instead of the internal MMC, but there is no out-of-box software solution.
Click to expand...
Click to collapse
Luckily, that's doable. But then we must have access to the boot partition. Or we need to try something with the recovery. And u need a good sdcard. One that matches or exceeds the read/write speed of the scardslot.
It's only never tried before on this device. Many could'nt get even to the recovery or flash a recovery/boot partition.
I'm about to buy a 'dead' Razr I stuck on the red Motorola logo...
I thought I just had to flash the firmware... but maybe I'll keep my money!
zephyro5 said:
I'm about to buy a 'dead' Razr I stuck on the red Motorola logo...
I thought I just had to flash the firmware... but maybe I'll keep my money!
Click to expand...
Click to collapse
Don't. the chances that it has an EMMC error is huge. Most of the time the person with a Razr I stuck on Red Logo already tried things to get it working.
There are still no methodes or methodes translated to this phone that can fix this error.
Related
I may have bricked my phone while flashing with odin to stock froyo 2.2 rom. The download mode works but i cannot get into recovery mode it just flashes at the logo screen gt-i9000m over and over and over again.
Is there a way past this or do i have to send this phone in for repair?
I have stock everything.
My phone battery died and I have spare batteries and changed it to a fully charged one. It booted up and said that a bunch of apps have to be FORCE closed... so I rebooted it.
Now it's doing the same thing yours is... the logo screen flashes over and over.
I pulled the battery to hard boot it. Then without turning it on I plugged it in to charge... so it tries to go to the charging battery icon and then flashes the logo screen over and over again.
This is my second phone... first one kept eating battery life and got real real hot.
omg stoopid samsung. I can get into download mode just fine, when i reflash it just stuck at the boot logo. Are you able to send yours away for repairs? i have mine unlocked but i also got warranty from where i bought it at wireless wave. i rather not send it in though...
I couldn't get into any menu's... sent the piece of **** away for repairs. I almost threw it at the wall behind the clerk at the bell store.
same boat here, i woke up this morning to find a bunch of forced closed messages. so i hit okay, my phone was all screwy so i turned it off, pulled out the battery, put it back in and started the phone and ta-da the galaxy S TEXT (not logo) kept...well it looks like it would boot over and over again just to the title screen, shut off and boot again. If i do the 3 button press to get to download mode i see that screen and i cant do anything else, actually i dont know what to do there.
I bought this thing in august so i am good for warranty, oh i haven't once rooted or lagfixed or anything, i just unlocked it, and with rogers instead of bell, but yeah i called bell and they refuse to help. The guy was not cool with me unlocking the phone, says i might not be covered under warranty anymore.
Next week i am going to take it to the bell repair center in person, see what they say.
Not sure what to do now. EFF!
Last samsung phone ever. the LG optimus 2X looks pretty awesome.
I'm having the same issue, my phones all stock.
When I got my phone this morning is was turned off, I plugged it in, powered it up, saw the Samsung logo and intro play and I walked away. When I came back I tired using my phone but only the lights, on the buttons, turn on but the screen and the rest of the phone doesn't respond. The lights will stay on forever.
If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Sent from my GT-I9000 using XDA App
Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
gtg2 - Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
The flash will go through completely and pass, as soon as it reboots to the Gt-i9000m logo it will just loop continuously. even when you hold down vol-up, home and power, it just doesn't recongize those buttons but will recongize vol down, home, power what gives?
Valinorian - If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Yeah tried darkys 5.6 rom, does the same thing shows gt-i9000m logo then loops it self
dtran00 - that sucks man, but bell offers unlock codes so i dont' see how that can void your warrenty when you have to pay $70 for the unlock codes no?
Spudsicles - hopefully i won't have any troubles but i might end up throwing it at them lol
Seriously this is a good phone but the problems omgosh.
regarding everyone with the boot loop errors, Sounds like you have got the corrupted internal memory. This is a common problem everyone has been having including me. You will have to send the phone off at bell. I'm still waiting for mine to come back to me, sent it off Dec 1, although some people are reporting repair times within 5 business days.
To the best of my knowledge, that does NOT necessarily indicate flawed internal memory. I've experienced a few errors myself - one was a real SDCard issue which required repair while the others I was able to recover from.
Have you tried reflashing firmwares via Odin with the repartition option checked?
Have you tried booting into recovery using ADB? I'm not an ADB pro myself but do know it's possible. You'll have to google for instructions.
my nook color will not boot at all. I formmatted /system and /boot, then it froze. Now I can't boot it up anymore. I was trying to update CM7.
Help please !
Thank you guys.
boot from an SD card. Works every time.
Even backlight doesn'flicker on.
Sorry, but I'll just borrow this thread for my Nook Color nightmare which may be more sinister than anyone else's on this forum.
I've read through Dummies Guide to Fixing 'My Nook Won't Boot' and was unable to come across a post that was able to solve my problem. However, there where three other posters who reported similar symptom as I, and who also were never able to find a solution.
I suspect that my NC, and the three other posters', is truly BRICKED.
Currently my situation is as follows:
- Attempt to power on NC does not yield any response, not even a flicker of the backlight turning on
- Cannot boot from uSD card that had previously successfully booted from in the past (have used it for flashing ROMs to EMMC).
- Attempt to power on while connecting to PC (XP) via USB causes computer to recognise device OMAP3630, but immediately loses it (NC unresponsive as per 1st point).
I had Nookie Froyo 0.6.8 on it for quite some time. And I think I witnessed it die. This is what happened: I turned on the screen using the N button. Everything seemed okay except that it was responding rather sluggishly to my inputs and gestures, and then it just froze (screen still on). I used the power button to try to cycle it but once it turned off that was the end.
I've already followed these suggestions:
- Press power button for 60 seconds.
- Press combination of Power, N, Volume.
- 8 boot attempts (as there is no visible response I press the button for 10 seconds, release it for 5, and then repeat that about nine times)
Hoping that someone could throw some suggestions around before I part with my expensive brick.
It's dead, Jim.
Why not do a warranty replacement?
Rodney
rhester72 said:
It's dead, Jim.
Why not do a warranty replacement?
Rodney
Click to expand...
Click to collapse
My thoughts exactly. Although I don't have extensive android experience, I've got a decent bit of PC time and that sounds like a problem based on faulty hardware rather than improperly installed software.
Sent from my NookColor using XDA Premium App
Other thing is, remember when messing around with flashing roms etc, that your battery is fully charged. Not sure about the nook, but for some phones, they don't charge while in this process and some people have bricked their phones while running out of power doing a flash.
I suspect you might have a battery problem and may not have a charge enough to boot from SD.
I'm in the same boat...
Same thing happened to me. I was fully charged, went to clockwork to boot while trying to update CM7 and now my nook is unresponsive. The only thing I get is the battery too low screen. It has been on its charger for 4 hours. If anyone has any suggestions...
I had the same problem.... wiped the boot and then was unable to boot even with SD card; only got black screen.. Then I decided to hold down the n and the power button at the same time and then after about five seconds I saw my screen flash and I let go of the power button and n buttons. Now the nook is booting fine off of my SD card once again... whew! Won't wipe boot again...
Time to replace this brick
lanje78 said:
If anyone has any suggestions...
Click to expand...
Click to collapse
Well, I've made the decision to exercise the 1 year replacement warranty.
I've been told by B&N customer support that you can simply walk in to a B&N store with the complete package (charger and cable) and they will replace it on the spot. Helps if you take the receipt with you.
For us people who live outside of the US it's a whole different kettle of fish...
UPDATE:
So I sent the NC back to my US seller and had it replaced under the 1 year warranty. I received a refurbished NC, but with the serial number starting with 2010... which I understand indicates a newer version.
I'm still wondering if OCing the NC may have cause the problem on my bricked one... I guess I will find out after I OC it again, which I am certain to do as it improves flash video play...
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium
Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse
I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:
Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app
Well thats unfortunite, I guess it's just for a soft brick.
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?
Hello, first time posting. I have an interesting Moto X, internal test device, confidential property n all that. Bought it on eBay. It's been working fine but I have a very strange problem. I have flashed many devices, many phones, none of this is new to me. I'm now reminded why I like access to the ENTIRE memory, and I get really frustrated with the consumer grade bs we are often forced to endure. That said, my phone works, system partition works, boots up, the main device is normal. So here's what happens- I enter fastboot, I select recovery, nothing. The phone shuts off. So I enter fastboot, select factory, nothing. Phone shuts off. So I enter fastboot, select BP tools... You get the idea. I can flash from Windows command line, all partitions read and write, but when I flash TWRP and try to enter recovery... Yep, you guessed it, nothing. When the phone is plugged in, it goes directly to the charging screen, confirming that the phone is turned off. I can fastboot boot twrp.img and it works, but it's not booting off the device directly, and I have no idea what happened. I installed lineage, installed xt1095 factory t mobile rom, it all worked fine, and then one day it didn't. Seems like it's just not entering the partitions since the device works fine otherwise. But I honestly have no idea on this one, and I can usually figure these things out. Please tell me it's not the phone, because it's a MOTOROLA CONFIDENTIAL PROPERTY NOT FOR SALE internal device, a cool find for a techie like me. HELP PLEASE!
oops
K since I've had views... lol. dumb mistake...thought something went wrong. VOLUME selects, POWER cuts the phone off. Like a pc, when in BIOS the power cuts instantly. Too used to having to hold the power button down on phones, instead of it being immediate. I basically never use TWRP now, I do all my flashing from windows. I only use recovery to flash a custom OS so it's been a LONG time since I've had to use the buttons to enter recovery. My mistake! Too much going on in my life I guess. I'll leave this up just in case it helps someone else. Thanks for your help! lol. phone works fine
Also, here's what mine looks like. I don't think they care now, since it's been a few years. But pretty cool find, there can't be many of these in the world.
https:// goo.gl/images/hDNepV