So I was helping my friend root and install PA on his phone. I got everything going good and asked him to find me the rom he wanted to use while I was doing everything else on it. Only problem is that he gave me the file for a Galaxy S II Paranoid Android rom. Found out after flashing it, and GAPPS and the phone wouldn't turn on. I have already tried a few things. I cannot get the phone to boot into fastboot, all it does is show the red light for a second and disconnect from my PC after a few seconds. It does the little device connected sound really quick, then nothing.
Holding power shows no LED, but my PC does detect a device.
Holding power+volume down shows the red LED error and that's it.
Edit:
For anyone wondering we already tried all power up options and it still just gives a red LED.
It gets connected so you can use adb?
Skickat från min Nexus 4 med Tapatalk 4 Beta
norpan111 said:
It gets connected so you can use adb?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
It only connects for a second. Like, basically it turns on for a split second and immediately turns back off.
It's dead. Sorry. Only way to revive it is with JTAG.
Sent from my Nexus 4 using Tapatalk 4 Beta
El Daddy said:
It's dead. Sorry. Only way to revive it is with JTAG.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well that sucks. I'm still fairly new to android but it was pretty straight forward with the toolbox to get the basic stuff done. Oh well, warranty time now I guess.
Sent from my HTC One
Warranty time!? So someone else should pay for your mistake? Unreal...
Sent from my Nexus 4 using Tapatalk 4 Beta
El Daddy said:
Warranty time!? So someone else should pay for your mistake? Unreal...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yea.
Sent from my HTC One
So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta
cadcamaro said:
Yea.
Sent from my HTC One
Click to expand...
Click to collapse
Well thats what happens if you don`t know what you`re doing and on top op that use a toolbox. Sorry for your loss but you have yourself to blame.
norpan111 said:
So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
It was loaded to the internal memory and flashed on the device itself from the recovery menu. So no, no safety as far as I know.
gee2012 said:
Well thats what happens if you don`t know what you`re doing and on top op that use a toolbox. Sorry for your loss but you have yourself to blame.
Click to expand...
Click to collapse
Everything went fine on my end. I told him to research and find which Rom he wanted so he had downloaded it. Toolbox worked amazingly and everything else went fine, and I've never done a nexus 4 so I didn't know what the file name is even supposed to look like so I just assumed he got the right one. Either way thanks guys, I know there's nothin else we can do now but I figured it wouldn't hurt to ask.
Sent from my HTC One
I remember when I was using s3,couldnt flash a mod for a different firmware even because mismatch
Skickat från min Nexus 4 med Tapatalk 4 Beta
norpan111 said:
I remember when I was using s3,couldnt flash a mod for a different firmware even because mismatch
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
Consider yourself lucky then haha. The Nexus just let it flash without a problem and just didn't turn back on.
cadcamaro said:
Consider yourself lucky then haha. The Nexus just let it flash without a problem and just didn't turn back on.
Click to expand...
Click to collapse
That really sucks.. Luckily if someone would be able to brick their device it was almost always a way to get it back somehow. Is it able to boot in boot menu? Or it's just black? Really sad for your friend either way
Skickat från min Nexus 4 med Tapatalk 4 Beta
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
http://forum.xda-developers.com/showthread.php?t=2208289
[WIP] Unbricking the Nexus 4 using QPST
Skickat från min Nexus 4 med Tapatalk 4 Beta
norpan111 said:
That really sucks.. Luckily if someone would be able to brick their device it was almost always a way to get it back somehow. Is it able to boot in boot menu? Or it's just black? Really sad for your friend either way
Skickat från min Nexus 4 med Tapatalk 4 Beta
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
http://forum.xda-developers.com/showthread.php?t=2208289
[WIP] Unbricking the Nexus 4 using QPST
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
Won't boot at all and the screen stays black. I've only rooted a few phones and my N7 so that link is pretty advanced for me. Still a good read so I'll look into it but for now if insurance will replace it then well just do that.
Sent from my HTC One
cadcamaro said:
Won't boot at all and the screen stays black. I've only rooted a few phones and my N7 so that link is pretty advanced for me. Still a good read so I'll look into it but for now if insurance will replace it then well just do that.
Sent from my HTC One
Click to expand...
Click to collapse
People are asking if the N4 is able to get to the bootloader/fastboot...since you used a "toolbox", it is safe to assume that you rely on ADB and the auto-scripts provided by said GUI tool only after a full boot. Since you cannot get a full boot, you feel stuck...Are you aware of Vol Up + Vol Down + Power taking you to fastboot from an off state? The OP doesn't mention you trying this key sequence at all. Make sure your battery is charged first because you, likely, have a dead battery if your device has only shown a "black" screen...plug it in, let it charge (if it shows the battery charging, you are probably going to be ok).
Since no one has bluntly suggested trying the basics and told you the button sequences, you probably haven't even tried them. I am just trying to assist you so your flippant "warranty time" approach doesn't cause MY deductible (used only for physically damaged or lost/stolen devices) to rise, yet again, anytime soon.
Please reply on here so you can get that thing fixed. It is likely that you just had a bad install of an actually compatible ROM or failed install of that GS2 ROM versus a rogue full install from another device. Asserts are in scripts for a reason.
Sent from my GT-N5100 using Tapatalk 4 Beta
VicFreeze said:
People are asking if the N4 is able to get to the bootloader/fastboot...since you used a "toolbox", it is safe to assume that you rely on ADB and the auto-scripts provided by said GUI tool only after a full boot. Since you cannot get a full boot, you feel stuck...Are you aware of Vol Up + Vol Down + Power taking you to fastboot from an off state? The OP doesn't mention you trying this key sequence at all. Make sure your battery is charged first because you, likely, have a dead battery if your device has only shown a "black" screen...plug it in, let it charge (if it shows the battery charging, you are probably going to be ok).
Since no one has bluntly suggested trying the basics and told you the button sequences, you probably haven't even tried them. I am just trying to assist you so your flippant "warranty time" approach doesn't cause MY deductible (used only for physically damaged or lost/stolen devices) to rise, yet again, anytime soon.
Please reply on here so you can get that thing fixed. It is likely that you just had a bad install of an actually compatible ROM or failed install of that GS2 ROM versus a rogue full install from another device. Asserts are in scripts for a reason.
Sent from my GT-N5100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322593
That is the exact rom he chose. I asked someone else about it and he replied with this "The OP has cooked the kernel inside the rom. Your mates phone doesn't have a dead bootloader, it's trying to boot the S2 kernel but can't due to the diffirent chipsets".
I also tried powering it on every way possible without any luck, guess I should have mentioned that. Yeah though, already tried with
Just holding power
Holding power +vol down
hold power + vol up
holding all three down
No luck with any.
If the boot loader is fine you should try to get into fastboot mode. Power off. Now press Power and volume down together until you get something on the screen. I would be surprised the phone is bricked just because you flash the wrong kernel.
Sent from my Nexus 4 using xda app-developers app
rasengan82 said:
If the boot loader is fine you should try to get into fastboot mode. Power off. Now press Power and volume down together until you get something on the screen. I would be surprised the phone is bricked just because you flash the wrong kernel.
Click to expand...
Click to collapse
This.
The ROM, Kernel, and Bootloader are totally different parts to the Nexus 4. You can commonly flash a wrong ROM, and even Kernel, but the Bootloader should be the last thing touched.
So, as long as you have a bootloader, you can access fastboot, and restore Google's factory image (or flash TWRP and have another go at a custom ROM/Kernel).
norpan111 said:
So weird it was flashable isn't it? Shouldn't there be special line for model match while flashing?
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
you probably had signature checking turned off in your recovery
I have never heard of a phone being bricked from only a ROM flash. It doesn't make too much sense. How could the wrong rom influence the bootloader?
Your phone should boot. Either you're doing something wrong while trying to boot, or the rom flash wasn't the only thing you have done to that phone.
Related
I have a case on my Nexus 7 that uses the four sensors on the side to turn the screen on and off. I was using the tablet just fine, then I close the case like normal, and upon opening it, it would not turn on. The only way to get a response from the device is by plugging it in and the screen just lights up black. Any type of power reset using the button combinations result in the screen shown in the video at the end of the post.
videobam.com/oLcTA
Sorry I can't post the link. I don't have 10 posts yet.
Solution: I removed the back cover and disconnected and reconnected the battery.
Re: Strange Screen When Booting
MX6Booster said:
I have a case on my Nexus 7 that uses the four sensors on the side to turn the screen on and off. I was using the tablet just fine, then I close the case like normal, and upon opening it, it would not turn on. The only way to get a response from the device is by plugging it in and the screen just lights up black. Any type of power reset using the button combinations result in the screen shown in the video at the end of the post.
videobam.com/oLcTA
Sorry I can't post the link. I don't have 10 posts yet.
Click to expand...
Click to collapse
That's really weird, are you stock?
Sent from my SPH-L710 using Tapatalk 2
dante32278 said:
That's really weird, are you stock?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
100% stock. It never did anything of the sort. I didn't get the 4.2.2 update until around Wednesday of last week and it happened on Friday
Re: Strange Screen When Booting
MX6Booster said:
100% It never did anything of the sort. I didn't get the 4.2.2 update until around Wednesday of last week and it happened on Friday
Click to expand...
Click to collapse
Might be a rogue app...have you added any new apps since the update?
Sent from my SPH-L710 using Tapatalk 2
dante32278 said:
Might be a rogue app...have you added any new apps since the update?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Not that I can recall. The tablet is purely my Portable Netflix/Evernote slave. I've left it on the wall charger for 24 hours, and on a usb port charger for 24 hours, to see if that helps but that won't do anything.
Re: Strange Screen When Booting
If you don't have anything important saved, you might to just try and wipe everything and start fresh. Are you rooted?
Sent from my SPH-L710 using Tapatalk 2
dante32278 said:
If you don't have anything important saved, you might to just try and wipe everything and start fresh. Are you rooted?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I have nothing that I would need to save, and how would I accomplish the wipe? I've never done it with an ASUS device before.
Re: Strange Screen When Booting
Check the stickies in the dev section, they will show you how to root/unroot and flash back to stock. You can likely just use the updated nexus 7 toolkit.
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my SPH-L710 using Tapatalk 2
tbh i dont get the problem your vid is just you holding the tab? could you maybe do a better vid o the problem
dante32278 said:
Check the stickies in the dev section, they will show you how to root/unroot and flash back to stock. You can likely just use the updated nexus 7 toolkit.
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
All of the options are saying it needs to be in ADB or in Android. I can't get it to show any of those screens to verify I'm in that mode.
MX6Booster said:
All of the options are saying it needs to be in ADB or in Android. I can't get it to show any of those screens to verify I'm in that mode.
Click to expand...
Click to collapse
I got it fixed. I ended up just removing the back and disconnecting the battery to force a power off. Thanks for your help though that tool will come in handy later
MX6Booster said:
I got it fixed. I ended up just removing the back and disconnecting the battery to force a power off. Thanks for your help though that tool will come in handy later
Click to expand...
Click to collapse
Good deal!
There have been a couple threads where folks reported similarly-behaving screens. "sparkles", "static", "like an old tv screen", et cetera. I think at least several of them were similarly traced to battery charge issues or loose terminals on the battery connector.
Maybe add "[SOLVED]" to your thread title and it will help future visitors with the same issue.
cheers
I had Franco's 110, then flashed Faux's kernel resetter and Motley's 37 one after another. Phone now would not turn on. I searched other threads and it seems like holding vol + and - together with Power, should fix it. However in my case,only the led turns on and stays solid red.
Any ideas?
Check and make sure you didn't flash a Nexus 7 kernel version.
If you did its toast.
Sent from my Nexus 4 using xda premium
Rest in peace if n7 kernel..
The Kernel file name is motley_422_n4_exp_build_37
However, Kernel resetter was downloaded from N7 thread, for some reason I was under impression its the same file...
The file name is grouper-faux123-reset-kernel-4.2.2
moldovanos said:
However, Kernel resetter was downloaded from N7 thread, for some reason I was under impression its the same file...
The file name is grouper-faux123-reset-kernel-4.2.2
Click to expand...
Click to collapse
Kernel resetter is just the stock kernel. If you got it from the N7 forum its the N7 stock kernel.
Sorry.
Sent from my Nexus 4 using xda premium
You can't even boot to the bootloader ?
Farewell Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
Never rooting the Nexus if i get it, such a fragile phone...
abdi7451 said:
Never rooting the Nexus if i get it, such a fragile phone...
Click to expand...
Click to collapse
Hi,
This is not the phone that is fragile, it's what the user do with it... If you flash a kernel from a Nexus 7 to the Nexus 4... for me it's legitim to have "a little problem"... It's the same thing for all the phones, try to flash a kernel from another phone instead the one make for your phone and see the result...
If you don't read correctly and don't paid attention at what you do or flash... It's not the phone that is the responsible...
viking37 said:
Hi,
This is not the phone that is fragile, it's what the user do with it... If you flash a kernel from a Nexus 7 for the Nexus 4... for me it's legitim to have "a little problem"... It's the same thing for all the phones, try to flash a kernel from another phone instead the one make for your phone and see the result...
If you don't read correctly and don't paid attention at what you do or flash... It's not the phone that is the responsible...
Click to expand...
Click to collapse
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
abdi7451 said:
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
Click to expand...
Click to collapse
This issue and the battery issue you are referring to aren't related.
The N4 led just flashed red when there is an error. It could be a variety of things.
Sent from my Nexus 4 using xda premium
El Daddy said:
This issue and the battery issue you are referring to aren't related.
The N4 led just flashed red when there is an error. It could be a variety of things.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Has it happened to you?
abdi7451 said:
Has it happened to you?
Click to expand...
Click to collapse
No. I don't do things to my phone that cause problems.
Sent from my Nexus 4 using xda premium
abdi7451 said:
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
Click to expand...
Click to collapse
You bought a Nexus device. Use it. Root it. Flash it. Play with it. You worry too much. Stop being so paranoid. Again, if you carefully do the correct steps you will get the results you desire. If you miss a step you will be sad that you screwed up your phone. If you're in math class and you miss a step to the formula to the equation you will get it all wrong. Pay attention to all the little details. You will be a pro at rooting in the future if you follow the steps meticulously.
Sent from my Nexus 4 using Tapatalk 2
So...as I understand I should just throw it in the garbage now?
scream4cheese said:
You bought a Nexus device. Use it. Root it. Flash it. Play with it. You worry too much. Stop being so paranoid. Again, if you carefully do the correct steps you will get the results you desire. If you miss a step you will be sad that you screwed up your phone. If you're in math class and you miss a step to the formula to the equation you will get it all wrong. Pay attention to all the little details. You will be a pro at rooting in the future if you follow the steps meticulously.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So everyone with the red light of death is an idiot that didn't follow the steps?
moldovanos said:
So...as I understand I should just throw it in the garbage now?
Click to expand...
Click to collapse
It may be able to be repaired. Here's the same problem from the other day.
http://forum.xda-developers.com/showthread.php?t=2208312
There is a link to a JTAG service in that thread.
Sent from my Nexus 4 using xda premium
have you tried flashing the factory image via fastboot? can you get into the bootloader?
El Daddy said:
It may be able to be repaired. Here's the same problem from the other day.
http://forum.xda-developers.com/showthread.php?t=2208312
There is a link to a JTAG service in that thread.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
thank you, I guess thats the only option left
simms22 said:
have you tried flashing the factory image via fastboot? can you get into the bootloader?
Click to expand...
Click to collapse
nope, I just can make the Led flash for a quick second:crying:
abdi7451 said:
Never rooting the Nexus if i get it, such a fragile phone...
Click to expand...
Click to collapse
yeah not fragile at all. people don't know what they are doing (no offense guys). they just need to READ everything. the stickies at the top of the forums explain everything in detail. flashing a kernel for a completely different device is just asinine. as long as people arent stupid about things, fastboot can always save their asses.
---------- Post added at 11:10 AM ---------- Previous post was at 11:06 AM ----------
abdi7451 said:
So everyone with the red light of death is an idiot that didn't follow the steps?
Click to expand...
Click to collapse
im guessing so. i had the "red light of death" last night. i was using my phone at like 2% battery left, rebooted it and it said i had 5% left. big whoop my battery calibration is a little jacked. well i kept using it and instead of going through the shutting down thing when the battery died, the screen just went blank. again, because the battery calibration is way off. so i plug it in, and the light turns red for about 10 seconds. then the light turns off, and the battery charging icon appeared. i waited 10 mins for it to get a small charge then booted right up. not a single problem. i really dont get why everyone is having such freak accidents and problems with this phone.
Bricked my Nexus 4 flashing a wrong ROM. Since i'm in EU and the phone USA probably will not get warrantly either
Now it won't even go to recovery, is there anything i can try?
Razer(x) said:
Bricked my Nexus 4 flashing a wrong ROM. Since i'm in EU and the phone USA probably will not get warrantly either
Now it won't even go to recovery, is there anything i can try?
Click to expand...
Click to collapse
Can you get into bootloader mode and flash stock imgs
Sent from my Nexus 4
Is anything happening when you power it up, can you get to the download mode?
Sent from my Nexus 4 using xda app-developers app
neky92 said:
Is anything happening when you power it up, can you get to the download mode?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No download mode, the only thing i could get out of it was a red led
You could try to charge it whole night, and then access the recovery /download mode, or maybe open it and unplug battery terminal and plug it back after few minutes....
If that won't help, I think RMA is the only solution (they should not be able to check it if it wont give anything but black screen)
Sent from my Nexus 4 using xda app-developers app
I don't think RMA covers user mistakes Its hard bricked if you flashed the wrong ROM. You have to send it away for J-Tag. Likely your only solution.
Gonna ask to the local LG store for repairing costs, then i'll value the best option
I erase my n7 boot loader and they fixed it for free should be the same with the n4
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
Once flashed a sammy N7100 rom on a I9300, the phone was dead as a duck and rooted on top of that. Got it repaired under warranty :angel:
Try turning it in and see what happens, i doubt they will be able to tell the phone has the wrong software and the bootloader is unlocked.Good luck
Thought repairs should be done worldwide but swaps only in the country where you bought it.
Razer(x) said:
No download mode, the only thing i could get out of it was a red led
Click to expand...
Click to collapse
i know this might be a long shot but try this if you can...
http://www.youtube.com/watch?v=oATx6fO35tg
gee2012 said:
Once flashed a sammy N7100 rom on a I9300, the phone was dead as a duck and rooted on top of that. Got it repaired under warranty :angel:
Try turning it in and see what happens, i doubt they will be able to tell the phone has the wrong software and the bootloader is unlocked.Good luck
Thought repairs should be done worldwide but swaps only in the country where you bought it.
Click to expand...
Click to collapse
Same here. Flashed wrong ROM on my galaxy s ii and they replaced it for free
Sent from my Nexus 4 using xda app-developers app
gee2012 said:
Once flashed a sammy N7100 rom on a I9300, the phone was dead as a duck and rooted on top of that. Got it repaired under warranty :angel:
Try turning it in and see what happens, i doubt they will be able to tell the phone has the wrong software and the bootloader is unlocked.Good luck
Thought repairs should be done worldwide but swaps only in the country where you bought it.
Click to expand...
Click to collapse
The problem is the warrantly is in USA, and the phone is here in Italy.
Did you lost all the personal datas?
I had the same issue. Windows Explorer on my Win 7 computer was not downloading the image properly from Google, and when I tried to install the factory image I got the red led and it was stuck on the "X" screen. After trying several times to get it into download mode, I discovered that I could eventually catch it if I hit the volume down and power buttons at a certain exact time during bootup, at which time I reloaded a non-corrupted factory image and I was up and running.
pjc123 said:
I had the same issue. Windows Explorer on my Win 7 computer was not downloading the image properly from Google, and when I tried to install the factory image I got the red led and it was stuck on the "X" screen. After trying several times to get it into download mode, I discovered that I could eventually catch it if I hit the volume down and power buttons at a certain exact time during bootup, at which time I reloaded a non-corrupted factory image and I was up and running.
Click to expand...
Click to collapse
Yep but you got an X screen, mine doesn't even show a thing
Razer(x) said:
Yep but you got an X screen, mine doesn't even show a thing
Click to expand...
Click to collapse
Volume down and insert USB cable. What happens when you do it? Does it go in boot loader?
Sent from my Nexus 4 using xda premium
It's a hard brick...
Nope, the phone is dead.
I'm selling it to US people so they can repair it, if you're interested send me a PM
Have a look here.
http://forum.xda-developers.com/showthread.php?t=2208289
Sent from my Nexus 4 using xda premium
mariosraptor said:
Have a look here.
http://forum.xda-developers.com/showthread.php?t=2208289
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Sounds interesting even tough it's pretty difficult
Razer(x) said:
Sounds interesting even tough it's pretty difficult
Click to expand...
Click to collapse
Yes, but where is the fun in easy stuff?
Sent from my Nexus 4 using xda premium
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
eksasol said:
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
Click to expand...
Click to collapse
Nope it doesnt turn on at all, also treid volume down and power button, still no succes. But like i said if i put the charger on it and try to power on, the red light goes on. The phone was at 35% when i flashed the twrp update
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just give it a few hours of charge, it will be back.
Mercado_Negro said:
Just give it a few hours of charge, it will be back.
Click to expand...
Click to collapse
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It happens. Battery stats in our device isn't too accurate. I've had that a couple of times. In fact, when my Nexus 7 2012 runs out of battery and I don't charge it for 4 hours or so it always needs half an hour to turn on.
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
frankvcs said:
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
Click to expand...
Click to collapse
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
I had a similar issue, I ran antutu and my phone went into a coma, no button combos were working and when I plugged in my phone I got the flashing red death light. But like PsyOr says just take of the back undo the two little screw's the hold the battery connector on, pop it off the put it back on and you're good. Worked like a charm for me.
Sent From a Slim Sexy Nexy
Actually seems like a hard brick. http://forum.xda-developers.com/showthread.php?t=2347060 try this.
And don't forgot to thank that guy, it's a brilliant post
No, its not a hardbrick, its the red light issues which is well known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
eksasol said:
No, its not a hardbrick, its the red light issues which is if en't it ll known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
Click to expand...
Click to collapse
That doesn't explain why the pc is asking him to use drivers for download mode. If the phone really dint have enough battery shouldn't it have not connected to the pc.
Also the device will be hard bricked even if a wrong kernel/rom is flashed. But it can be unbricked by the above method.
Try the Nexus 4 toolkit. There are options to re-install everything up again. If you are sure that your battery is in good working order, then it might be software related issue. I don't think it's a hardware problem.
soylukral said:
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are in download mode as indicated by your pc detecting the phone as QHUSB_DLOAD this is not the common battery fault.
You will likely get here by the bootloader failing
At this point you are more bricked than a general soft brick. But still not completely hard bricked.
There is a very useful thread in the general section about how to fully flash using download mode.
You can find the info below, note that there are a lot of steps involved so if your not confident. Rma is probably your best bet
http://forum.xda-developers.com/showthread.php?t=2347060
Sent from my Nexus 4 using xda app-developers app
Thanks guys for all of tour help. I wil try everything to bring the phone back. I will report if something happens. Btw what is RMA?
Sent from my Nexus 4 using XDA Premium 4 mobile app
RMA is return merchandize authorization.
sent from xda premium app
eksasol said:
RMA is return merchandize authorization.
sent from xda premium app
Click to expand...
Click to collapse
ok, and that is??
Guys, i did send it back to LG for repair. I want to thank all of you for the help you gave!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Nexus 6P takes well over one mine to bootup compare to my Note 5 20 second.
what could be the cause of this? could it be from android 6 ?
Mine does, too, but I don't know why boot time would ever be a concern to me.
Sent from my Nexus 6P using Tapatalk
Never rebooted. I'll check it out 2016
Skickat från min iPhone med Tapatalk
EVOme said:
Mine does, too, but I don't know why boot time would ever be a concern to me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not a concern at all but when I rooted my nexues, flash recovery or update to 6.0.1 I noticed this. Since this is my first nexus I was wondering why would it take this long.
Yathani said:
Not a concern at all but when I rooted my nexues, flash recovery or update to 6.0.1 I noticed this. Since this is my first nexus I was wondering why would it take this long.
Click to expand...
Click to collapse
Verified boot takes an extra ten seconds, from what I hear, just to show you that message. So maybe it's an unlocked bootloader?
I'm guessing device encryption has something to do with it.
Sent from my Nexus 6P using Tapatalk
Phone is being decrypted at each boot. That's normal, nothing to worry about.
mlin said:
I'm guessing device encryption has something to do with it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
anmar21 said:
Phone is being decrypted at each boot. That's normal, nothing to worry about.
Click to expand...
Click to collapse
That explains it.