Database Users

IMPORTANT!! Regarding VisionKernel 1.2

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.

Solution for One Potential Cause of Rapid Battery Drain

I've was using 5.2.3 for the last several weeks and to begin with, it worked wonderfully.
Until around 10 days ago, I'd never suffered any rapid battery drain problems, then all of a sudden one morning, I woke up and the phone was at 10% charge despite being left on charge overnight.
I figured there was an issue with the ROM and decided to reboot. This seemed to work fine for a day. Then the same charge problem was back.
I thought the ROM was now failing so decided to install the latest version 5.2.6 directly over 5.2.3 but the problem still persisted so the problems didn't seem to be ROM related but could be due to the unwiped areas but this seemed unlikely.
Just as a final test I decided to change the cable. I normally use the cable provided by HTC as it seems pretty sturdy. Turns out it was the cable all along.
The phone is now charging fine with a different cable and it's running fine again.
So, if you're having problems with overnight power drain when your phone is on charge, try changing the cable.
Edit: There is no visible damage to the cable and it has never been stressed in anyway as I take great care not to stress the pressure points.

Thanks for the info mate. Probably not in the right the right section though.

Your response to that post is probably in the wrong section. Oh, wait..! [email protected]*!t now this post is probably in the wrong section, see what you started.
Sent from my Inspire 4G using xda premium

My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.

Sorry for posting in the wrong thread everyone. I don't create new threads very often so I wasn't thinking clearly.
Diffler said:
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Click to expand...
Click to collapse
I'm not saying the cable problem was caused by the ROM - I was just explaining how I identified that the ROM I was using wasn't the cause of the battery drain.
Cables breaking are very rare - happened once to a phone cable once after engineers had been called out to check the fax machine about 6 times before someone gave the cable a try.

Be carefull with the new ICS ROMS. Always shut down by holding the button for 20 secs

I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.

Thanks!
Sent from my Kindle Fire using xda premium

It happened to me already, but it woke up with the original charger.
Thanks!

yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery

It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.

This just happened to me...
My kindle died after shutting down for one day. No battery at all...

Did you even read the first post of the kernel thread?

ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA

StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.

If the devs were offered a dime every time somebody failed to follow directions...

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.

Not going to argue with you on that one.

ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?

@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.

umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.

This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2

It will always work best with the stock charger, but until the bugs are fixed, who knows.

KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).

For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.

Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA

Red Light Of Death - Should I Be Concerned?

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

Pretty sure I bricked my Nexus 4

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