Related
After a total brick, Black screen. I am convinced that this phone is truly un-brickable, I did not ask for help. All you need to do is READ READ READ! Having said that I would like to thank eugene and everyone else for the usefull tips.
30Glock said:
After a total brick, Black screen. I am convinced that this phone is truly un-brickable, I did not ask for help. All you need to do is READ READ READ! Having said that I would like to thank eugene and everyone else for the usefull tips.
Click to expand...
Click to collapse
Congratulations! It is widely believed that this phone is about as close to being unbrickable as any phone out there.
Would you care to share how you got your phone working again? It's possible that someone might actually read this instead of asking, in which case you can forward the cause
Yea--DO SHARE!!!
I wrecked my phone somehow and have not been able to reflash a stock rom no matter what...I have a few days before I have to ship it back with to the warrantee center--I'd love to try and fix a HW locked phone.
this is true, unless u have a hardware locked phone, in that case, ne thing can brick ur phone easily
ookas said:
this is true, unless u have a hardware locked phone, in that case, ne thing can brick ur phone easily
Click to expand...
Click to collapse
That is not entirely accurate, I "bricked" my phone, and I have a hardware locked vibrant, seems download mode can be gotten into with some due diligence("due diligence"=Don't panic and read read read) .
I have a hardware locked phone, obviously I read the threads. I cannot get into download mode - at all. No recovery.
If you're bad at pressing key combinations on your hardware unlocked phone, that's okay. You will eventially get it and then post how you got your hardware locked phone into download mode, I'm sure (hint, take off the back cover, makes pressing the buttons trivial).
Don't spread misinformation.
Hardware locked phones will not let you get into download or recovery mode. They will just power cycle over and over again if you try to hold keys down while the phone is booting up. You can try evey combination immaginable and one of two things will happen:
1. It will power cycle indefinitely (if power button held down) to the Vibrant Logo (turns off and on to that screen forever).
2. It will get stuck at the Vibrant Logo and never move (if the Volume Buttons held down). Will get to Vibrant Screen and stay there.
If you let go of all the buttons, it will just boot up normally (if it can, or get to a black screen if you bricked it /shrugs/).
I know. We tried for 3 hours in the store and I stayed up half the night trying. There's no way to get there, Lol. Seriouly: No way.
T-Mobile says it's a known issue. Asurion knows of the issue. Samsung knows the issue (issued a patch for Canada, but no one else IIRC). All 3 told me the only recourse is to get my phone replaced.
And that's what I'm doing.
I doubt you will get charged for bricking a hardware locked phone, because the manufacturer will have to flash a new ROM onto the phone anyways - at a repair factory.
Mine is locked, but I got into recovery mode via terminal app connected on USB.
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Kippyyy said:
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Click to expand...
Click to collapse
Yup just rsd the sbf back. You will lose everything however so hopefully you've got a backup somehow. Here's the sbf
http://db.tt/H2RuCD8h
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
I've had a similar problem as you with my flipside. Are you sure you're using the right key combination to get into rsd mode? If you can at the very least get it into bootloader mode by holding down the volume + key while holding the power button, I'm sure you can get it into rsd mode.
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
Theres a post here somewhere that has the combo of keys needed to get into bootloader mode. Sorry dont have it saved. Just do a search for it
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Kippyyy said:
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Click to expand...
Click to collapse
Did you by any chance have the stock launcher app frozen and using a different launcher? Just seems if you are seeing the backlight that possibly it is on the home screen but the launcher is corrupt? Not sure.
I'm not entirely sure. I assume it's stuck in the bootloop because when I power it on the backlight changes shades and then vibrates to signal the screen past the motorola M. Then I can touch the screen and feel a vibration to simulate to slide to unlock and if my usb cable is attached my computer makes the noise to signal it sees my device, but moments later my computer dings to signal device disconnected and my phone goes through the above process again.
I feel as if I can get to the factory reset screen and such because if I time it right I can stop it from doing anything mentioned above and it just hangs as if in a menu of some sort. The downfall is I see nothing and the backlight only appears.
I may just have to scrap it and say well done phone. I can't seem to find a similar issue anywhere on the internet. All the other issues can make the bootloader screen appear and that appears to be my number on problem.
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Kippyyy said:
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Click to expand...
Click to collapse
Yes like straight out the box. The backlight issue just seems to me like a launcher problem but that wouldn't explain why you can't get into bootloader mode. Hmmm strange. Here is another way I just thought of. If it connects to the computer (you said you hear the beep) reflash it via Motorola's site. All the instructions should be there (if they still support it)
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Kippyyy said:
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Click to expand...
Click to collapse
Yup that sounds like hardware failure. Haven't ever heard of the screen going out on the flipside but the atrix forums are full of them. Maybe you can get your upgrade early. Good luck
So last night I hard bricked my nexus 4. its rooted, with cyanogenmod 10.1 ROM, and ive never had any issues with this phone. I have no idea what happened, but I sent a text message to someone, and it powered itself down. it was fully charged when this happened, so I know its not the battery. ive done some research, and its a true hard brick. no bootloader, no recovery, I just get a red/orange flashing light if I hold down the power button. google said im still under warranty, and they will still replace it even with it being rooted. My question is, is it possible to fix without having to get a replacement, or JTAG? If anyone has had any success, please help.
And like I said, I was only sending a text. I have no idea why it bricked, it restarts itself once in a while randomly, but this time it didn't turn back on.
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
exb0 said:
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
Click to expand...
Click to collapse
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
sinndissension said:
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
exb0 said:
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
Click to expand...
Click to collapse
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
Nope. It's different.
sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
You can compare it too fastboot mode.
gee2012 said:
You can compare it too fastboot mode.
Click to expand...
Click to collapse
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
Did you press volume down first and then the power button both for a few seconds to get into fastboot mode?
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, or the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone knows of that I didn't just list, my last option is JTAG.
sinndissension said:
yep. ive done EVERY combination of holding down the buttons, no response. when I plug it in to a laptop, the laptop beeps, like the USB connection sound, but the nexus doesn't show up on the computer. I know the computer recognized what kind of phone it was, cuz the first time I plugged it in, I got a pop up message saying "installing qualcom drivers", or along the lines of that. other than that, NOTHING has worked. If theres ANY fix for this, id like to give it a try, cuz ALL my stuff is on there.
Click to expand...
Click to collapse
Try charging it for a while and try again in a few hours or better yet tomorrow. Sometimes that helps bro. If that doesn`t help you`ll have to take it in for repair an maybe they can salvage your data if they are wiiling to do that. Good luck.
I think it's just your battery(RLOD) instead of a brick.
See this:
http://forum.xda-developers.com/showthread.php?t=2250454
I wouldn't be worried about your files stored on your phone because I think Google has more work to do than search in peoples pictures. What I would worry about is your warranty since you have a custom rom, unlocked bootloader and root...
Sent from my Nexus 4 using xda app-developers app
Well, found out it WAS a hard brick. Google replaced it with my warranty. For some reason they returned my money before I even got the chance to send the broken nexus 4 back. Didn't even mail it. So I'm assuming I don't have to send it back. So I'm gonna JTAG the hard bricked nexus, and hopefully it'll work again.
Thanks everyone for your help.
sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
You may not be doing it right. When I get the flashing light on mine it means I forgot to let go of the power button fast enough. When it vibrates, let go of power button immediately but keep pressing the volume. Does your phone vibrate a few seconds prior to the flashing light?
Sent from my GT-P7510 using xda app-developers app
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
sinndissension said:
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
Click to expand...
Click to collapse
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Mashed_Potatoes said:
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Click to expand...
Click to collapse
ok...that has nothing to do with a hard brick. That just means your phone was dying.
dominiqueovalle said:
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Click to expand...
Click to collapse
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
sinndissension said:
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
Click to expand...
Click to collapse
its a hard brick. ive tried it all bought a new battery installed it etc. ive looked up jtag and i have the money but idk if i should do it. do you recomend it? i have no experience doing anything like it and im planning on getting the iphone 6 in the fall but i cant stand not having a phone till then especially since high school starts soon.
But the reason im sure its a hard brick is cuz when it shut down the battery was like 50 and charging and it froze for 25 seconds or so then shut down and refuses to boot or show any signs of life now except a blinking or solid red light but its not the red light of death because i replaced the battery therefore i came to the conclusion that it is hard bricked.
i know ive said alot of unecessary information but my question is do you think i should buy the jtag thing? do you reckon its easy to do? or maybe i could pay an experienced professional to do it?
thanks for the reply btw
Hello
This is my first post here and I'd really appreciate advice in this matter.
I've spent the past couple of hours searching for an answer but nothing works or totally irrelevant results.
I have a problem where I'd rooted my phone with KingRoot, changed it to SuperSU successfully (restarted my phone several times since then and no issues)
I installed TWRP (only the app) from the Google Play store and that's as far as I got before I powered off my phone to cool down before attempting any installation of TWRP. Powered on my phone and I can't get past the Samsung logo.
Recovery won't come up, Download mode works but restarts itself and volume buttons do nothing to let me confirm download mode and so it's sending me in a loop. Samsung logo and restart again and again. I insert my battery and the first thing that happens is my phone goes on a mission, determined to power itself on only to Bootloop.
No, before anyone suggests it be a hardware issue, it's a brand new phone. There's nothing wrong with the buttons.
If anyone is going to point out the obvious in saying that I'm responsible for rooting my device, I'm aware of this. The rooting procedure was a one-click method which was successful and caused no boot issues after restarting the phone countless times.
Basically:
Bootloop
Can't access recovery
Can't get to Download mode without it getting back into the bootloop after 5 seconds or so. Volume buttons do nothing to confirm download mode.
USB debugging wasn't enabled before this Bootloop occurred
Do I have a paperweight or is there a way to salvage something from this?
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
GDReaper said:
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
Click to expand...
Click to collapse
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
adrxano said:
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
Click to expand...
Click to collapse
Oh my god you are amazing thank you so much! Wow. I really appreciate this you've fixed the problem. Thank you!!!
Thanks to all for the time taken to read this and for the responses
Lol it feels great to be helpful.
Sent from my GT-I9500 using Tapatalk
BackShooter said:
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
Click to expand...
Click to collapse
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
GDReaper said:
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
Click to expand...
Click to collapse
You're correct, thank you again I thoroughly appreciate your time and help with this
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
edlovereze said:
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
Click to expand...
Click to collapse
Sounds like you may have more than one problem, but many have been able to get a dead phone to start by holding the power button down for a very long time, sometimes 2 minutes or more. If it doesn't start, fully charge it and try the power button again. Assuming you are stock with a locked boot loader.... you didn't mention.
My phone is stock with a locked boot loader. I held the button for over 5 minutes and got nothing. I'm wondering if Google would be willing to help me out. Unless anyone has other ideas
It's hopeless. Don't waste your time trying to revive. Contact Huawei regardless of date of purchase.
If it won't power on it's either not charged, a bad power button, or something with pcm. Which is on Motherboard.
Most common scenario is a bad power button because it's most used breakable part. That won't allow the board to receive power or not enough power if it's shorted.
Dunno if you've poked around the interwebs some more regarding this, but I've been slammed with the N6P bootloop error (which appears might be part of your problem) and I found a stop-gap solution. If you feel like you've got nothing to lose, you can try what I've done: Make sure the phone has a little charge, hold it with a hot mitt from your kitchen, and blast the back of your N6P in the region between the camera lens and the fingerprint sensor with a hairdryer. Doing so will trip the big cluster off, which is the source of the bootloop problem. If you can get it to boot to the Google logo, applying the heat for the right amount of time (maybe not too long.. 2-4 minutes tops) may cause it to make it to the spinning color graphics and beyond.
I've been able to resurrect my phone doing this, but only to back it up and do very simple tasks. The moment I do something processor-intensive (Waze, YouTube, etc) it immediately crashes and bootloops again. The only solution beyond this is to unlock your bootloader, download EX Kernel manager and use it to completely disable the big cluster. Then your phone will likely be reliable, but extremely hobbled.
I bought from Best Buy about 16 months ago, so both Google and Huawei have been utterly useless, which is infuriating. Shenanigans like this are criminal. This is my 3rd Nexus phone and I'm considering abandoning Android altogether after this experience.