Red Light: Scared to root

[Rizy7]

Does anyone know how long it will take before I notice any red light problems with my phone? Just received the phone and want to root the phone but dont want to end up with the red light and not being able to turn the device on at all

 

[Basscase]

Exactly 3 days, 4 hours, 27 minutes, and 31.5 seconds. After that, your phone will be worthless.

Seriously? What kind of question is this? If you're scared to root, don't. Why do you want to anyway?

 

[KwietStorm]

Exactly 3 days, 4 hours, 27 minutes, and 31.5 seconds. After that, your phone will be worthless.

Seriously? What kind of question is this? If you're scared to root, don't. Why do want to anyway?

He wants to root because he wants to root, and your type of response doesn't help someone who needs to be eased into it.

But what is this red light business you're talking about?

 

[Basscase]

He wants to root because he wants to root, and your type of response doesn't help someone who needs to be eased into it.

No, it wasn't helpful. But really, his question was like asking "If I put this turbo on my car...how long until my engine blows?"

Plus, if he's scared to root, my question of why he wants to root is relevant. Is it worth "the fear" of bricking his phone?

And by the way OP...there is NOTHING to be afraid of. It's a few clicks of a few buttons. Easy peasy. Just do some reading before you go about it.

But yes...what is this "red light" you speak of?

 

[greydarrah]

Whether you decide to root or not, if you're thinking about doing it, you should at least unlock the bootloader ASAP. The reason is because it wipes everything on your phone, including pictures that you might take or copy to it. It's easier to do now, while your phone is new and you don;t have months of stuff accumulated. It's easy to do...just follow these directions: http://forums.androidcentral.com/nexus-4-rooting-roms-hacks/224861-guide-nexus-4-unlock-root.html

You can decide to root right then, or later. It's only the unlocking of the bootloader that wipes your device.

 

[2defmouze]

I've never heard of this red light issue you speak of.

My advice: Unlock the bootloader as soon as possible. It wipes everything off your device, and you need to do it before rooting. You can always root later after taking care of that step, but better to get the wiping done early before you have so much on the phone you'll be sad to have to lose/recover/etc.

 

[KSmithInNY]

Green Light: if you're worried about rooting (for any reason including technical ability or knowledge) then you need to read more *or* just enjoy and love the phone as is.

 

[Rizy7]

Guys this is my second nexus 4, I already rooted the first one I had. I'm not scared of rooting because I've done a lot of research and a lot of help is available if something goes wrong.

I've read a few stories (maybe not on these forums), but the newer devices although still technically rev 11 have had issues with the battery/other hardware resulting in the phone randomly switching off and just displaying a solid red light. It has been suggested that the red light notifies the user that the phone needs to be charged and doesnt have enough battery to power the display. However, people have had no luck even after leaving the phone on charge over night. Some have managed to get into the bootloader but many have not had any response from the device.

I am aware that if I root, I can just as easily unroot and relock the device if I have any problems and need to send the device back to Google. However, can you guys see that if the screen doesnt even switch on or phone doesnt respond at all, then im kind of stuck?

 

[rluttrell]

I got the red light when trying to root several times. Now my phone won't turn on. Is there anything I can do to fix this?

 

[Rizy7]

Sorry to hear that.. Have you tried getting into bootloader?
Try putting your phone in a fridge for a while (I know sounds crazy)
Also try pressing on the back of the device just below the nexus area
If that still doesnt work then you might have to take your device apart. Apparently reconnecting the battery solves the issue.

 

[CoolBeit]

If you get a hardware failure like this, I think there's a better than even chance google will replace your device even if you're rooted. The terms are that unlocking/rooting MAY void your warranty. But I do understand your concern.

I sent my last phone back to Motorola after the digitizer failed. The bootloader was unlocked (and that phone contained an e-fuse which was burned the minute I unlocked the b/l...so there was no going back) and quickly sent me a new phone under warranty.

 

[ChromeJob]

... However, can you guys see that if the screen doesnt even switch on or phone doesnt respond at all, then im kind of stuck?

No, not stuck. Jist connect via ADB and determine WTF the phone is doing. But if it doesn't respond to ADB, then it may well and truly be brick-worthy.

Guys, please don't advise others to open their device and muck with the hardware internally while the device is still under warranty. Opening the device, breaking seals, and trying to self-repair more than likely WILL void your warranty, even if the original cause wasn't your fault.

Contact Google and arrange a replacement for a bricked phone if you want a warranty replacement.

 

[John-Smith]

adb fastboot -w