Related
I tried to load up the new gingerbread roms from my current one. I downloaded its content and tried to install it via clockwork.
I first deleted system, logo, and cache followed up by a restore format. When trying to download the new rom, I was getting a weird error that was stopping me from completing the full installation. So basically was in a chokehold because I didn't have any backup files or another working rom in the sd at that time. I just restarted the phone and it for a few times was stuck on the M screen, but now its just green led when I plug it into the computer usb. When plugging it into the outlet, it imediately turns on stuck on the M screen and shuts off when unplugging as if the battery isnt charging at all.
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
bigshotrob22 said:
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
thats the problem.. i got the X.340 sbf and the program aswell but I cant get into bootloader mode. is there an alternative way to sbf?
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Could be your battery same thing happened to me try using a friends battery your battery could be dead and it no longer charges
Sent from my DROIDX using XDA App
bigshotrob22 said:
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
bootloader is such a rare occurance for me, i just had it come out but it was flashing low battery. the thing is, im not quite sure if its charging if i have it plugged into the computer. when i have it plugged into an outlet, the M splash screen comes up so i'm worried that draining the power..
edit: now it flickers for a split second, am i supposed to hold on to it til something shows up? been like 1 minute
i dont think bricking phone blows your battery. at least i hope it doesnt, was working fine before.
Plug it in without the battery if a question mark comes up you ned to use another battery cuz it won't charge in boot loader and the boot loader should pop up right away hold power volume down and camera button it takes about three seconds
swyped from my DROIDX using XDA App
well its basically the same thing. when plug into the outlet it shows the m splash screen with or without the battery.
when its plugged into the compuiter however, its just flickers once. when it is done with the battery in, the led is on forever
EDIT: OBSERVATION
when on the wall, it is actually charging, but REALLY slowly because of the fact that the splash screen stays on. found this out because i had it in for30 min and then tried to connect mit to my comp with bootload and it loaded for a few minutes with the low battery flashing.
is version 320 the latest?
Okay. so it isnt charging as I though because its not working at all... problem is, I dont know if it truly is a battery defect. If I were to Buy a new battery, how would i know if it is charging if it doesnt boot and just stays stuck on the M logo screen?
perhaps I should by a battery charger where i take the battery out and charge it through there? because my bootloader always gives me the same low battery.
Do you have any friends with the same phone? There is also a macgyver (spelling?) Method of doing this by cutting the USB cable open and attaching the cable ends to the battery. However I would only do this if you're really desperate
i just really need make complete sure that this phone is INFACT dead battery
when not plug, it doesnt turn on what so ever with a white spark on the led.
when plugged nto outlet the logo shows but i isnt charging because it isnt booting
when plugged into the computer it is a solid green which i think represent a dead or a low battery state(can someone back thisup?)
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
raziel36 said:
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
Click to expand...
Click to collapse
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
There's a usb trick u can try. Google it.
Sent from my DROIDX using XDA App
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
You definitely need to use the bootloader, and I was implying that in the first reply(SBF'ing requires going into the bootloader). If you had a stand-alone battery charging cradle/dock, that should do the trick. Just make sure to let the battery charge sufficiently. I've successfully gotten an SBF completed, starting with only 30% battery. SBF takes about 7 minutes on my laptop(not that I've timed it, but I usually light up a smoke when I start the process lol). So, as long as the battery is charged enough to no longer give the "Low Battery" warning in the bootloader, you should be fine.
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
froyli said:
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
al the tips or just red for pos and black for neg
Positive and negative google it before you do it
Sent from my DROIDX using XDA App
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
jinho11050 said:
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
Click to expand...
Click to collapse
Glad you got it working! Nearly everyone on here has needed help, at one point or another, and that's what makes Android so great... the community.
Sent from my DROIDX using XDA App
I already posted this in Q&A, but I thought it would get noticed more in this section.
Ok I believe my phone is "Hard Bricked", because it doesn't power up at all. The Green led light will show if i take the battery out and plug it into the computer. This happened as was trying to start the process to unlock my bootloader. I was using RSDlite, loading the "zomgunlock" sbf file, put my phone into rsd mode plugged it in, pressed start and next thing i know it turned off and won't turn back on. Can someone help me?
ninjajtm said:
I already posted this in Q&A, but I thought it would get noticed more in this section.
Ok I believe my phone is "Hard Bricked", because it doesn't power up at all. The Green led light will show if i take the battery out and plug it into the computer. This happened as was trying to start the process to unlock my bootloader. I was using RSDlite, loading the "zomgunlock" sbf file, put my phone into rsd mode plugged it in, pressed start and next thing i know it turned off and won't turn back on. Can someone help me?
Click to expand...
Click to collapse
What version are you on? And can you boot in rsd?
Sent from my MB860 using XDA App
its version before 4.1.83, but i know i can't get to RSD or to get something showing on the screen
Was it low on charge?
Sent from my MB860 using XDA App
No its not from a low charge, it was on already 80%
Oh, does your phone get recognized when plugged into a cp?
Sent from my MB860 using XDA App
no it doesn't seem to be recognized, i tried doing the combos green led light on (volume up + power , etc.)
But the phone stays off?
Sent from my MB860 using XDA App
It stays off unless I take the battery out of the phone and hook it to the computer, that is when I get the green light indicator
Hi,
I am a NOOB but was reading another post that had a similar problem. Not sure how to make a link to it.
The issue the other fellow had was that when he plugged in to the USB port it was actually draining his battery rather than charging it.
There are specific drivers on the Moto website that you need for the computer to charge the phone.
The short way around it is to charge at the wall.
The title of the post I am referencing is "[SOLVED] Atrix will not power on, green light flashes, plugged in and.... nothing!" initially posted 24th Feb 2011 last post was today.
If your issue is more complicated than this then I apologise for wasting your time.
Worst case no further harm done.
I'm pretty sure my battery is pretty good atm but I'll try anything to get my atrix working again
That happened to me when I was trying to flash the unlock bootloader for mine. I'm using the Atrix on Orange running on U4_4.2.0. Completely bricked with the same green light but nothing happening. Told Orange and got a new one luckyly, next day!
Yea well im on my second from at&t bcuz of a hardware problem, unless I'm able to get a third one. .i ned to find out how to fix this, and the battery charger method didn't work for me
Sydpark said:
Hi,
I am a NOOB but was reading another post that had a similar problem. Not sure how to make a link to it.
The issue the other fellow had was that when he plugged in to the USB port it was actually draining his battery rather than charging it.
There are specific drivers on the Moto website that you need for the computer to charge the phone.
The short way around it is to charge at the wall.
The title of the post I am referencing is "[SOLVED] Atrix will not power on, green light flashes, plugged in and.... nothing!" initially posted 24th Feb 2011 last post was today.
If your issue is more complicated than this then I apologise for wasting your time.
Worst case no further harm done.
Click to expand...
Click to collapse
USB port on a computer won't drain a connected device. Problem there was he was trying to charge a drained battery on USB 2.0 which doesn't supply enough power to charge properly. The solution to his problem was to charge with the proper Motorola AC wall charger.
Yea I know but I tried the fixes anyway since there was no harm
If it's an AT&T phone take it to a repair center and they will replace it if its less than 1 year old. You don't even need the crappy insurance.
I thought it's only me
I have same problem, googled it 2 days ago - noboday else reported it
same problem - flashed the unlock-able boot-loader - phone turn off, and died...
I progressed a bit more - after replacing battery with a fully charged one, just to find out it's not a battery issue - I prepared the "special cable" - pin 4 connected to VCC.
now - my phone does recognize my phone, as "APX". after providing drivers found in google - it now recognized as "NVIDIA USB Boot-recovery driver for mobile devices".
it doesn't really help, as RSDlite is still not recognizing it, and using NVflash - i get only errors...
I know - i didn't really helped to solve the problem, as I'm "stuck" with it too, just wanted to share my effort...
Tomer
henrys01 said:
If it's an AT&T phone take it to a repair center and they will replace it if its less than 1 year old. You don't even need the crappy insurance.
Click to expand...
Click to collapse
Even though this is my second phone?
ninjajtm said:
Even though this is my second phone?
Click to expand...
Click to collapse
The phone has a 1 year manufactures warranty.
o ok, thanks for letting me know
Hi im running alien 4 and im unlocked, my ATRIX wont charge through the pc usb or through the stock moto wall charger.. I tried using a different micro usb cable to no avail but if I turn the phone off and plug it in, the green led turns on and the phone starts.. I even have 2 batteries and neither work
EDIT* I just tried using my dads phone wall charger and that didn't work either
Your usb port might be borked, or worse the power supply inside phone is jacked. If you don't find a solution soon then I would think about warrantying the.phone.
I voided my warranty.
Can adb, fastboot or rsd recognize your phone?
Sent from my MB860 using xda premium
Try turning the phone off and then as you plug it in hit the power button and let the phone boot. Will it charge then? I had this problem and ended up having to flash the full Pudding SBF to resolve the issue.
pukemon said:
Your usb port might be borked, or worse the power supply inside phone is jacked. If you don't find a solution soon then I would think about warrantying the.phone.
I voided my warranty.
Click to expand...
Click to collapse
Hey, come on. Fix or get rid of that signature. I've seen tons of people get confused from your posts because you don't have a separating line or anything. And sometimes it (weirdly) goes along with posts and messes everyone up. It's just been bugging the piss out of me...
Hey guys, Im trying to fix this mt4g for a friend.. It wont boot, I cant get into hboot or recovery, all it does is flash the LED. I have read post saying its because I was unsuccessful at loading bootloader, however it doesn't vibrate like the others are saying. I left the battery out for a couple hours along with sd and sim, also tried charging through the night... I cannot figure this one out, also, the computer will not recognize any new hardware or drivers. Is this phone bricked beyond repair?
I put the battery on my battery charger and let the battery charge outside of the phone now when I put the battery in the phone and plug it in to the computer, the red LED comes on and stays on, along with a red glow on the trackpad... Anyone know what to do?
Blinking LED is either the battery is charging to at least one percent, or you didn't press the right button combo to boot into bootloader. Power + Volume Down is bootloader, Volume up will give you three vibrates and a flashing LED, where you will have to pull your battery.
Thanks, I cant get the phone to do anything... I plug it in with the battery in, without pushing any buttons and the LED comes on and the IR trackpad light comes on... It wont respond to anything, no drivers popup.. Is there anyway to recover a bricked mt4g? Im new to it, as I have an Evo and have never had anything like this occur with all the evos i've flashed and rooted... If someone knows anyway to fix this feel free to give input..
Thanks everyone!
ya .. mine is doing the samething.
I just try to turn it on and I get one vibrate ... nothing else
I hit down and power and I get one vibrate .. nothing else
I hit up and power I get 3 fast vibrates and a flashing orange led ... I try to plug the USB here and I get 3 fast beeps on the comp
I hit up and down vol and power I get 5 fast vibrates with a solid green led and noting else... usb again beeps 3 times on the comp
neither will recognize the usb and I have reinstalled the drivers .. and of course none will work with adb either.
I think we are screwed really ... but maybe someone knows something i dont on this here. Thanks for any help.
if you fix your phone. let me know
dragon_usa said:
if you fix your phone. let me know
Click to expand...
Click to collapse
ya .. no luck so far ..I have tried a lot .. different drivers .. HTC sync .. etc.
I have tried different button pushes .. usb ports .. wont work in adb .. nothing is doing anything.
all I hear thru my speakers when I plug it in is that damn the fast 3 beeps .. ike a "hell no go F yourself you arent connecting it"
and there isnt a lot of info online bout this .. other than some others have the same LED blinking and stuff .. I still dont know what the different LED modes mean.
so IM screwed .. BUT I am getting an LG G2X as an alternate exchange thru T-Mobile warranty though. goodbye mytouch 4G Hello to G2X AND Galaxy S II(bought) .. fun times!
I found a thread somewhere, not sure where but it said that if you cant get anything and the infra-red on the touch sensor is lit the phone is completely bricked!
Its not bricked. Somethign is wacky with the phone, mine has done it and thats why im trying to find out what the hell is going on. My phone acts like its completely dead. This post migt end up being really long.
Ok, i notices this, i used my phone as a wifi hot spot. Turned it off. Left my phone alone, i then put it on charge and went to sleep. Woke up looked at the battery, no color other than the lighting bolt. Unplugged it then went off. Pluged charger back in and orange led flashes. Tried to get into recovery nothing. Tried to power it on, nothing, tried the volume down and power, three vibrations. Ok then i decided to take out the battery in and out, didnt work, tried leaving the battery out for a few minutes, then put it back in, same. Took out memory card, sim card. Then plugged in the charger. Let it sit for awhile then it works. I notice if you dont use the orginal charger that may also be the problem. I dont have my orginal but i used a walmart charger and seems like a super charger and some how charged my battery enough to be booted up, i daily use a charger that i found with the same connection x-( , that could be the problem. I dunno what makes this happen but it happened to me at least three times. I kinda figure the battery or the emmc chip is involved, could be the hotspot, could be anything, but we dont have enough evidence to figure it out, ill try to post what my battery usage on here. I use cm7 and it only happens when i use it. I tried all other roms but no repeats. That was my story.
Sent from my GT-P7510 using xda premium
Sent from my GT-P7510 using xda premium
Strapt said:
ya .. mine is doing the samething.
I just try to turn it on and I get one vibrate ... nothing else
I hit down and power and I get one vibrate .. nothing else
I hit up and power I get 3 fast vibrates and a flashing orange led ... I try to plug the USB here and I get 3 fast beeps on the comp
I hit up and down vol and power I get 5 fast vibrates with a solid green led and noting else... usb again beeps 3 times on the comp
neither will recognize the usb and I have reinstalled the drivers .. and of course none will work with adb either.
I think we are screwed really ... but maybe someone knows something i dont on this here. Thanks for any help.
Click to expand...
Click to collapse
I have done all these as well, and still unable to get past the black screen, or acheive bootloader as well. I have even left the battery out for a couple of hours, and still no different. Going to try recharging the battery once more, and some other things.
As for adb it is of no help as of now. I keep getting an error saying no device found. Has anyone found a way past this yet, to try rebooting through adb?
*Edit*
After trying to replace files on the sdcard I was not able to get past this issue. Also spoke with tech support, and was not able to get anywhere with their help. After speaking with them, I have come to conclusion the is bricked. I still cannot figure out what caused the phone to do this I broke down and sending it out to be replaced. Thankfully I have the insurance so I don't have to pay anything for the replacement.
Apparently its not bricked cause I'm still using mine. Try a different charger probly a stronger one like walmarts. I think the battery has a fart and is messed up for a little when it doesn't have a good charge
Sent from my HTC Glacier using xda premium
tnt8902 said:
Apparently its not bricked cause I'm still using mine. Try a different charger probly a stronger one like walmarts. I think the battery has a fart and is messed up for a little when it doesn't have a good charge
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I have done this, fully charged it twice, and no change for me. I am glad it worked out for you.
Its not bricked.
Download the stock rom, and put that .zip in the root of your SD card. Put it in, press Power + Volume DOWN and wait for the bootloader. Once it boots, it should recognize the .zip and ask if you want to update it, run the update and your phone will be at stock again. Then root again, install Clockwork, and hopefully you backed up your ROM. This won't effect S-OFF, but you will have to run VisionARY again to get root permissions to run clockwork.
Hope this Helps.
one more
I am too having this problem
just blink orange
can't access bootloader or any else....
I too had this problem not too long ago. My power button wouldn't work though... I just connected via USB to my computer with the battery out, put it back in while connected and it turned on. Maybe I'm just lucky but give it a try
Sent from my HTC Glacier using XDA
I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?