I don't know how I did it. I've been rooted/unlocked for over a month (running CM the whole time) with stock kernel. Last night I upgraded to the 03.24 nightly and everything was fine. 3 hours later I downloaded a franco kernel after some reading and I wanted to try it out. I used Rom Manager to reboot into recovery (like I always do) and install the kernel and as soon as I hit "restart now" apps started FC'ing and my phone never came back on. It never made it to recovery mode or anything. It just died completely and I was around 40-50% battery life.
Currently this is what I'm dealing with:
Holding the power button down for 10 seconds flashes a red LED light. No changed on the screen
Holding any combo of the volume keys (up, down, and both) + power does the same as above
The only time the LED flashes red is when I'm plugged in via USB or AC. Otherwise nothing
I've had to charging for nearly 10 hours now... it's like it has no power at all
When plugging it into a PC I see "QHUSB_DLOAD" in my device manager.
I have the Android SDK and Nexus 4 drivers installed
I have seen NOTHING On the screen since this has happened - no charging animations, fastboot, not even a flicker
I've down A LOT of reading and the only thing I haven't tried is charging it for days at a time and taking it apart (which I'm not opposed to doing) but I'd prefer not to. Is there anything else I can try? Thank you
Sounds like you flashed the franco kernel for the Nexus 7. You aren't the first and probably won't be the last. Unfortunately if you see QHUSB_DLOAD its dead.
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
That's what I was afraid of... do you think this is legit? I saw the video and it looks good. Says it fixes phones that don't boot at all. I e-mailed and asked them about my situation but I'm curious if you have heard anything about them?
http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/
blahblah13233 said:
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
Click to expand...
Click to collapse
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
blitzzz3434 said:
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
Click to expand...
Click to collapse
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
Most of them are pretty reliable. The one that you linked to, they have their own YouTube channel where people have left pretty positive comments. They seem legit. I'd try them out if you want to be nice and not RMA it.
https://www.youtube.com/user/MobileTechVideos
Yeah its really legit. I got my HD2 Unbricked from there. I flashed a wrong radio and came back with a "RESURRECTED" Bootloader and just flashed a new rom. Its probably different on the Nexus 4.
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
I would still google them to see if there are actually legit. But hope it all works out for you!
Thanks for the replies everyone. I'm going to send it to them to fix it... I'll post back here with the results so other people can search this thread for answers
its bricked. Next time make sure you look at what your flashing.
I got the red light of death, just charged the phone for around 8 hours and it came back.
Sent from my Nexus 4 using xda app-developers app
Related
i have to have the worst luck in the world..
got my nexus one today. condition is MINT. seller also included the receipt from HTC proving that it got replaced.
popped in my sim, everything worked fine. turned it off to swap batteries and thats when the hell started.
im not able to get past the nexus logo. NOTHING. it would turn on, than go to the screen, vibrate, than repeat multiple times. phone has never been rooted.
i did EVERYTHING. i did the volume down plus power and than i cleared wiped the memory, same result.
than i tried downloading 2.2.1, renaming it to update.zip, put it on my zip, but that doesnt work. the phone can't tell theres a update.
like **** man. i than went here
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
read that i needed FRG33 and rename it to PASSIMG.ZIP. when the phone turns on, it gives me the message if i want to update, i get excited. i click yes, everything says ok, than i reboot and bam, still endless reboot. tried to do the passimg again but this time i get a fail on radio V2 or something like that.
WTF is going on. i didnt do anything. ANYBODY HELP?
maybe the battery you swapped in is bad?
same result with both batteries :/
i hate my effing luck.
Make sure your batteries are fully charged, seriously.
great, now when i click recovery, it doesnt even go to the android guy with the exclamation mark, it just gets stuck at the logo. all im able to do is get to hboot. WTF.
i mean the battery has half a charge. just checked with my desire. i even tried with it plugged in in the wall. nothing.
my aim is screwupboy444. your welcome to help me there or even laugh at me for being a bone head and getting in this situation.
Do you have a different SD card you can use?
Sent from my Nexus One using XDA App
yeah, i was using both the desire 8gb and the nexus one 4gb. both were reading fine in the desire. i read that if it gets to the nexus one logo then my phone isn't bricked, but im starting to think otherwise. nothing works.
ive been searching for the past hour half. everyone seemed to have fixed there by doing the passimg method or wiping data. but unfortunately none of that is working. i tried placing the froyo "update.zip" and running it but when i clicked recovery, it went into the boot cycle again.
http://forum.xda-developers.com/showthread.php?t=614850
thinking about doing that but i have a feeling it doesnt apply to me. that and i don't understand any of the process. i dont think my phone will even be read by my comp.
did the passimg for the third time. went past the logo and actually to the set up screen. than it rebooted again. and now its stuck on the nexus one logo again.
could it actually be that? i left the battery charging in the desire for about 40 minutes, than took it out and put it in the nexus one and actually got to the set up screen for the first time.
but my question is, if thats the solution, does that mean my phone is gonna trip out everytime its less than 60 percent battery power?
this is what i get when i put the 2.2.1 update on my sd card and go into recovery mode
Uploaded with ImageShack.us
most of the threads where people got this fixed required them unlocking the bootloader and doing something. im the second owner of the phone but would like to avoid rooting but if its required in this situation, i will. i just need a dummies guide to do it..
No, there's threads for recalibrating the battery, if needed.
Keep it fully charged, and see if it will run for a reasonable period... That way, we can see if it really is the battery...
Sent from my Nexus One using XDA App
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
frick, i know thats what i should do. it just blows that i got this today and theres already a chance that its trashed...
danger-rat said:
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks for all the help man. you dont think i need to unlock the bootloader right...? im just more curious on why the desire can work with either party no matter the charge. damn.
Wait until your battery is about 75% or more would be better, then try the passimg again...
Sent from my Nexus One using XDA App
not sure if its good news or not but (i apologize for my lack of patient before hand haha), i took out the battery the desire was charging again and put it in the nexus one. it got to the set up screen all three times before it resets again. i tried plugging it in the wall charger but it still resets at that area.
edit:
the battery level was at 74% when i tried it.
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
danger-rat said:
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
oh iam. im charging the nexus one battery in the desire because once i turn on the nexus one, it gets frozen there, and than i cant turn it off.
This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
NOTE: It appears that MANY users are suffering from this issue and haven't realized it yet (because they haven't yet shut their phone down). If you reboot to flash another kernel, please know you may suffer from this problem so do so at your own risk. This is extremely unfortunate as this means there's no way to prevent the problem from getting worse.
ok..hmmm..so I saw this thread and decided to power off my phone and go back to genocide since visionkernal has been acting weird here and there anyways..so i power off my phone and now it doesn't turn on lol
DO NOT PANIC AND POWER OFF/REBOOT THE PHONE OR YOU MIGHT BRICK!!! WAIT TILL A SAFE METHOD TO TURN YOUR PHONE OFF IS CONFIRMED!!!
If YOU ALREADY BRICKED, POST IN HERE:
http://forum.xda-developers.com/showthread.php?t=1043240
--
SO FAR THE FOLLOWING METHODS WERE CONFIRMED TO BRICK:
Power down/Reboot via menu
Battery pull
BRICK DOES NOT HAPPEN FOR EVERYONE, AND MAY HAPPEN AFTER TIME BUT IF IT DOES HAPPEN TO YOU ITS A PERMA BRICK
I work for sprint, If you don't have insurance and the screen is cracked take it to a tech center and they will fix it for $35. If it is a larger crack than 2 inches they might give you some hassle just haggle with them or go to a different store cause my store does it no problem
Sent from my harmonious Bonsai 4.0.1 tree
trobertson said:
This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
Click to expand...
Click to collapse
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App
Custodian said:
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
For me what I noticed was phone randomly shut off at night even though it was stable all day long...
The battery was good...like lost 3-5% in 7 hours of idling and stuff..then when I turned it on after it crashed it instantly lost 50% battery.
You can't get your phone replaced for problems unrelated to cracked screens???
I was actually hoping to brick my phone some day
Dude, WTF!
My phone has acs rom 1.1 and visionkernel 1.2. It started hanging on me so I held down the power button and pressed reboot. Now it wont turn on, and it won't charge either! WTF I AM SO ANGRY RIGHT NOW. IT WAS JUST FINE.
Finally I'm not alone.. I had this issue as well and fixed it by pulling my sd card and battery out a few times and then pressing the power button. After I finally got the phone back on I had to odin back to eclair. Hope this helps...
Note: I also formatted my sdcard. Because just pulling the battery didn't work. So I suspect something on the sdcard was making the phone not turn on..
Hmm..,maybe powering off is the cause of the issue..hmm..I think its safer maybe to crash the phone rather then turning it off/rebooting it then reflash another kernal..
I had an issue flashing 1.2 also. Got stuck at a boot loop after first installing, had to do a battery pull that corrupted everything. None of my back up works so I had to start fresh with eb13 then flash the ec05 modem and then flash my backup after all of that. Glad I had a back up but still a bit of run around having to odin first.
I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.
cerchiara said:
I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.
Click to expand...
Click to collapse
which kernel? also I tried with taking out the sd card altogether and putting in a new one..didn't work....
it has been working fine for me and I only used Voltage and overclocked only to 1300. What applications are you guys using to set your speeds/governor?
Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing
To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?
quik99 said:
Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing
Click to expand...
Click to collapse
Well bricks happen..its nothing new..mostly when experimenting with things...
What other kernel was causing perma bricks?
fhurricane said:
To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?
Click to expand...
Click to collapse
nope, my phone didnt charge, tried it already
I think I just joined
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.
Light does not turn on when plugged in, tried two different full batteries, can't even turn it on to get to recovery or download mode.
hussmanne said:
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.
Click to expand...
Click to collapse
you did "power off" or "reboot" via menu right?
if so can op update the OP telling people NOT to power off their phones! cause thsi thread make get more people to brick their phones as is...it made me break mine lol
I think I chose power off from menu, I remember the phone vibrating faster than usual before turning off. Twas its last breathe.
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
See this thread and good luck.
http://forum.xda-developers.com/showthread.php?t=2013977
Sent from my Nexus 4 using xda app-developers app
chelsierae said:
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
Click to expand...
Click to collapse
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
elliot.newnham said:
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
Click to expand...
Click to collapse
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
chelsierae said:
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
Click to expand...
Click to collapse
This happened to me today. The battery indicator is incorrect, and shuts down before notifying you sometimes.
Phone shut down on me randomly and wouldn't turn back on today. Plugging into the wall didn't help. It was only when I plugged it into my PC and let it charge for 5 minutes that it came back. Scary bug.
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
elliot.newnham said:
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
Click to expand...
Click to collapse
I thanked you on accident, you didn't deserve it. There is no evidence that his phone is bricked, a user above reported the same thing happening and how he resolved it.
Also, he can type in bold if he wants to.
I hope the OP issue gets resolved. Wish you all the best buddy!
I'm having the same issue. Except this happened when I pulled the device new out of the box. Can't even get it to stay on long enough to get into bootloader mode. :-/ RMA time
Good luck on fixing the problem.
Sent from my Nexus 4 using Tapatalk 2
This is not another just my Nexus 7 won't turn on after running out of battery or regular SOD problem. I dirty flashed to the latest LeanRom from Smoothrom 4.3 and it was running well through out the day with the exception of SOD's during the day about 3 or 4 times. I used it until 23% battery and it shut off. I plugged it in and it was rather difficult to get it to boot through button pushes holds and combos. It booted up and I used it while it was charging untill it was around 70% battery and I went upstairs with my tablet and got in bed and used it for a while... It was around 60% and I plugged it in again and went to sleep. Keep in mind I left it overclocked as I always do with M-kernel b35 *1.7ghz default kernel voltage. and GPUat 766mhz 1295mhz voltage. Keep in mind I always manage my Temps. via apps and it never gets hot in my hand not even very warm. Only spot it would ever get even a little warm is lower left back where I think the CPU or GPU is located because that is where the Heatsink is located. I am not sure if it possibly overheated and fried it.. But as I said I have had a generous overclock on it for 3 months. Again it never became very hot ever! Anyways that morning I grabbed it and hoped in my dads car and as usual it had SOD'ed overnight. I began holding the power button for a few mins. A couple of times. It went too the Google logo with the unlocked bootloader and then i tried to turn it off and boot it again because the kernel has never been friendly with the 3.34 boot-loader. It has always had a weird time starting the os and me having to hold the power button untill it goes black and starts the Google logo and then shows my boot-loader and will start up and I release the power button. Well after that last Google logo I have not been able to power it on at ALL not even backlight glow I have charged it 15 hours and nothing. I have spent HOURS researching this and there are no links on Google that have helped. It is not the regular SOD or out of battery not starting issue. It also it not recognized by my computer and I can only see that it thinks it is called APX or something by my computer. I was hoping that some one could help. I even removed my battery and plugged it back in. I have tried all button pushing nothing... I have called ASUS but there warrenty BLOWS. Any help would be much loved =] I love my nexus =[
@@[email protected]@-- [email protected]@[email protected]@--Haha so guess what Asus fu ( ked me royaly after paying $30 dollars for shipping to Grapevine Texas and my tablet is still not turning on. It's not the charger or cord I have tried enough of those to know its not that. Is there any hope at all or am I sending it in again... also there "tech repair" people ****ed the **** out of my tablet under the hood the battery was lose yes I know I tried that too. The copper heat sink was ripped and sticking up. Stickers ripped apart. They had better send me a refurb back. To the guy before I was simply refuring too when I dirty flashed. Not that the def had anything at all to do with it. It was my dirty flash. I am rather mad about sending it in again. Any advice.. Thanks!!!
I now realize that it is APX mode WTF how in the world can I get out of it without a replacement is there anyway at all???
http://forum.xda-developers.com/showthread.php?t=1789135&page=2
Mabey ill button jam while in comp for a while and see =/
situation seems grim...
If it is in APX mode, it will take 15+ seconds of holding the power button continuously to get a restart.
IF that is the case, the black-and-white Google logo will come up - if you press Vol-Down precisely at that moment, the tablet will proceed to the fastboot screen. If you don't press Vol-Down, the tablet will attempt a normal boot.
Assuming that the hardware is not damaged and the battery has a decent charge, you can always get to the fastboot/bootloader
...it was running well through out the day with the exeption of SOD's during the day about 3 or 4 times...
Click to expand...
Click to collapse
LOL. You seem unusually tolerant of non-determinism.
good luck
bftb0 said:
If it is in APX mode, it will take 15+ seconds of holding the power button continuously to get a restart.
IF that is the case, the black-and-white Google logo will come up - if you press Vol-Down precisely at that moment, the tablet will proceed to the fastboot screen. If you don't press Vol-Down, the tablet will attempt a normal boot.
Assuming that the hardware is not damaged and the battery has a decent charge, you can always get to the fastboot/bootloader
LOL. You seem unusually tolerant of non-determinism.
good luck
Click to expand...
Click to collapse
Hey, thanks for responding to my thread. The issue is that my tablet will not respond to anything that I do. When/if I get a new one I may not overclock the GPU as high as that may be why my tablets *****ed*
bump..
It'd be awesome if someone could be of assistance on this issue because I think it could come in handy in the future for people.
Thanks.
[QUOTE=Nexus7
As far as apx mode no one knows how to fix it yet your tablets basically a paper weight.. Sorry dude, you can attempt to send it back and see if they will fix it but that's basically all you can do right now, or sell it for parts
Sent from my Nexus 7 using Tapatalk HD
OK so now i'm wondering if ASUS RMA will know I'm rooted and charge me.. The guy on the phone asked me if I wanted my os restored I said no but I'm a lil worried. Also in USA does ASUS RMA take forever and will they prob. send me a shiity refurb?
xfrancis14 said:
As far as apx mode no one knows how to fix it yet your tablets basically a paper weight.. Sorry dude, you can attempt to send it back and see if they will fix it but that's basically all you can do right now, or sell it for parts
Click to expand...
Click to collapse
Uh, what? This is only the case if you borked the bootloader, which should still be intact in his case. Apx mode is basically a service mode that's even lower than the bootloader, it's just that we don't know how to use it.
I insist that you keep holding the power button or perhaps play with the charge more.
Sent from my SGH-I777 using xda premium
korockinout13 said:
Uh, what? This is only the case if you borked the bootloader, which should still be intact in his case. Apx mode is basically a service mode that's even lower than the bootloader, it's just that we don't know how to use it.
I insist that you keep holding the power button or perhaps play with the charge more.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I have trust me it's not turning on at all. Thanks for replying any other suggestions are much loved and needed lol. I have until Monday when I mail it out to get it fixed.
Nexus7<3 said:
I have trust me it's not turning on at all. Thanks for replying any other suggestions are much loved. I have until Monday when I mail it out to get it fixed.
Click to expand...
Click to collapse
EDIT_ I ducked taped my power button down and i'll see if maybe it comes out of APX death-mode. Also what are the possibilitys I fried a internal inside such as power supply. CPU or GPU? with the overclock...
Nexus7<3 said:
EDIT_ I ducked taped my power button down and i'll see if maybe it comes out of APX death-mode. Also what are the possibilitys I fried a internal inside such as power supply. CPU or GPU? with the overclock...
Click to expand...
Click to collapse
Yepp deader than a door nail. Any ideas are helpful
Nexus7<3 said:
Yepp deader than a door nail. Any ideas are helpful
Click to expand...
Click to collapse
Out of the 400 ish people who have viewed the thread there are 0 suggestions or hints?
[QUOTE=Nexus7
Sorry dude there's no hope, not trying to be mean but there's simply no hope
Sent from my Nexus 7 using Tapatalk HD
766mhz was a silly number to go to for a chip that doesn't even have air cooling. Sorry, but you were asking for that to happen, whether you felt it getting hot or not... It was trying to tell you something by not starting up and crashing overnight all those times...
Sent from my Nexus 7 using Tapatalk HD
knuckles1978 said:
766mhz was a silly number to go to for a chip that doesn't even have air cooling. Sorry, but you were asking for that to happen, whether you felt it getting hot or not... It was trying to tell you something by not starting up and crashing overnight all those times...
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I don't really think I fried it now tbh. I think the Rom did it
Nexus7<3 said:
I don't really think I fried it now tbh. I think the Rom did it
Click to expand...
Click to collapse
I don't think so at all. I think YOU fried it. I don't mean to be harsh but you can't blame the dev's around here because you OC'd your tab way to high, and killed it.
As stated before, did you not think the SODs were trying to warn you of something.
Nexus7<3 said:
I now realize that it is APX mode WTF how in the world can I get out of it without a replacement is there anyway at all???
Click to expand...
Click to collapse
If you got in APX mode then the bootloader is gone for good. The tablet is not able to boot any more.
It happened the same to me while flashing the 4.2.2 stock ROM: something went wrong right after the "fastboot erase xxx" commands and my tablet died.
I have searched the internet for any solutions but I failed miserably. I reverted to ship the tablet back to Asus for assistance.
Well, they picked up the package on Thurs 21 and I got my tablet back on Tue 26.
Repair was covered by warranty even though I had the bootloader unlocked (that's a mandatory step in order to flash a stock rom from Google).
They actually replaced the mainboard instead of reflashing the firmware.
That suited me fine.
slvrbllt said:
If you got in APX mode then the bootloader is gone for good.
Click to expand...
Click to collapse
N7s that are operating correctly can enter and exit APX mode at will; by itself, APX mode does not necessarily indicate a problem. ( Failure to get the boot loader to appear obviously is a problem.)
For devices operating normally:
- From power off, Vol-Up+Pwr (3 seconds) puts the N7 into APX mode.
- From APX mode, holding power for 15+ secs loads the bootloader - which will attempt loading the (regular) boot partition. If the Vol-down button is pressed within about 1 second of the b&w Google logo appearing, this boot sequence is interrupted and the boot loader proceeds to fastboot mode.
Just a clarification that seeing APX mode does not necessarily equal disaster. As you were!
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app
Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348
So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??
Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution
Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2
Yes, it's what I said, ah I forgot this link.
When you search, you find
Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.
Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.
Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.
I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app
Alright. Sounds good.
Got mine last week but it's a Rev 10 not an 11.
indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)
Loosen the screws?? Do you have a link to the YT video?
Ordered mine when they were first available, got it 2-3 weeks later (end of November).
Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again