Hey i recently flashed a faux kernal and everything was running fine then all of a sudden my phone turned off and i cant turn it back on if i try nothing happens and when i plug in the the usb a red light appears and keeps flashing then after a awhile a battery pops up as if its charging then just disappears. I am able to get into the boot loader but i cant get into recovery or do anything else can someone help me !
Also every now and then booting does work but it only goes to the Google screen then turns off again and goes back to the battery then just keeps restarting from there
Keep the phone plugged in and see if you can boot up. Sounds like your battery died.
Anyways, if you can get into bootloader, you should be able to use fastboot to flash a stock image or get to recovery to flash another ROM/kernel.
ZzzZ
Stryder5 said:
Keep the phone plugged in and see if you can boot up. Sounds like your battery died.
Anyways, if you can get into bootloader, you should be able to use fastboot to flash a stock image or get to recovery to flash another ROM/kernel.
Click to expand...
Click to collapse
How would i flash a stock rom using fastboot ?
Bosnianwog said:
How would i flash a stock rom using fastboot ?
Click to expand...
Click to collapse
Using the fastboot flash command. Google it
Sent from my Nexus 4 using Tapatalk 2
to be honest, RMA time!
ntt1409 said:
to be honest, RMA time!
Click to expand...
Click to collapse
Yep. I think this is the third post with the exact same issue. Be sure to try and re-lock your bootloader before sending it in for RMA or you'll probably be charged for another device.
Sent from my Nexus 4 using xda premium
Yeh i think i will just send the phone back to them hopefully they replace it for me :crying:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Clarkster said:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Click to expand...
Click to collapse
Agreed wait until a stable build comes out.
Bosnianwog said:
Hey i recently flashed a faux kernal and everything was running fine then all of a sudden my phone turned off and i cant turn it back on if i try nothing happens and when i plug in the the usb a red light appears and keeps flashing then after a awhile a battery pops up as if its charging then just disappears. I am able to get into the boot loader but i cant get into recovery or do anything else can someone help me !
Also every now and then booting does work but it only goes to the Google screen then turns off again and goes back to the battery then just keeps restarting from there
Click to expand...
Click to collapse
Happened to a few people already. Here's my thread on it.
Unlucky man i know how you feel and what are you going to do about it?
Bosnianwog said:
Unlucky man i know how you feel and what are you going to do about it?
Click to expand...
Click to collapse
Called Google and ordered a replacement yesterday. They said it should be here in a few days.
It's not bricked, do this hold down volume down and power till you see the bootloader then volume up till it says restart recovery, boot into recovery, wipe cache then dalvik cache, redownload faux kernel from his site, then reboot into bootloader, flash new kernel with fastboot, reboot and you should get into Android, I had the same issue with the red light after flashing his new kernel, this fixed it.
Clarkster said:
This is now at least the third post I've seen about people bricking their devices with the faux kernel.
I think everyone else should stay away from that kernel for a while.
Click to expand...
Click to collapse
Exactly, with all the respect to faux, whom is a well known developer and a very good one too...
Sent from my Nexus 4 using Tapatalk 2
djkinetic said:
It's not bricked, do this hold down volume down and power till you see the bootloader then volume up till it says restart recovery, boot into recovery, wipe cache then dalvik cache, redownload faux kernel from his site, then reboot into bootloader, flash new kernel with fastboot, reboot and you should get into Android, I had the same issue with the red light after flashing his new kernel, this fixed it.
Click to expand...
Click to collapse
Thank you for trying to help, but please stop suggesting things if you don't thoroughly understand the issue. I'd hate to waste your time and mine going over the things I have already with other people. Just read my op to learn why what you're saying will not work.
kaiowas82 said:
Exactly, with all the respect to faux, whom is a well known developer and a very good one too...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I really dont think their devices are bricked, my heart stopped when I had the non-booting red led issue after installing his 005 kernel, but a wipe of cache and dalvik then reflash fixed the problem, of course im not using the OC kernel version, which might be causing all these issues.
djkinetic said:
I really dont think their devices are bricked, my heart stopped when I had the non-booting red led issue after installing his 005 kernel, but a wipe of cache and dalvik then reflash fixed the problem, of course im not using the OC kernel version, which might be causing all these issues.
Click to expand...
Click to collapse
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
@OP
Please use your head... this is alpha software, built blind... unless you know exactly what you're doing don't flash software that can/will brick your phone.
And don't send back phones on warranty when it's not a manufacturing defect. Overclocking exceedes the manufacturing specs and thus you voided your warranty, don't steal from google.
abnormalreply said:
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
Click to expand...
Click to collapse
I understand the issue, and your line Doing "fastboot getvar battery-voltage" does not give an output, meaning my overclocking (to 1.6Ghz) fried something involved in the battery communicating with the motherboard. implies your hardware was functioning properly before you flashed the OC kernel...which then means that the malfunction happened from software not hardware...of course if something is fried then yes...YOU borked the hardware and it would need replacing...I had a similar issue and was just reporting what fixed my issue with the Red LED and not being able to boot.
abnormalreply said:
You don't think it's bricked, because you don't understand the problem. My post in this very thread explains why this is a hardware issue of a defective battery, and not a software one.
Click to expand...
Click to collapse
You're in the same boat mate, you're sending the phone back on warranty, when it's your overclocking that broke it. There is a reason why its pegged at that speed. I mean if you want to argue it was a manufacturing defect that was only found via overclocking that is fine, but it doesn't help the case that you ran the phone outside of spec. Don't steal from google.
Related
There is no way to rule out GB as the cause of this failure right now. All we have is theories and the best fitting one is an emmc chip failure. Until we can find a user with a brick, who is still s-off, we can not learn more.
DO NOT FLASH OVER BRICKS, We need you to have s-off for trouble shooting.
UPDATE
We need info from brickers and non brickers please see
Please see here http://forum.xda-developers.com/showthread.php?t=1098363
--old post--
It has came to our attention, over the last few days that the recently leaked Gingerbread radios maybe causing a oddly large number of bricked phones.
This can affect any Thunderbolts running Gingerbread (except CM7 users), even after running fine for several days.
The cause at this point is not completely understood, and AndIRC as a whole recommends you revert back to Froyo until we understand it, or have a new leak.
When bricked, the phone is sent into an endless bootloop, no matter if you are booting into Android itself, or into the recovery. Trying to revert after the bootloop does not fix this issue.
Theories:
GB Radio causing corruption on the emmc:
Undisclosed chipset issue (Sorry no details will be coming unless verified)
GB miss reporting battery stats, aka just dead battery (Debunked by ryan2600 and I)
"Not sure if its the radio, i got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later the phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Good thing i have a 2 extra battery and an external charger from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%" http://www.reddit.com/r/Android/comments/hk54l/if_youre_using_the_leaked_gingerbread_build_or/
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Awww fiddlesticks! Well at least I get my baby back. Landscape Rosie is the girl for me.
swimminsurfer256 said:
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Click to expand...
Click to collapse
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Wow this sucks, I don't really wanna go back to froyo
Thanks jcase and Team AndIRC! I nearly flashed the latest BAMF GB update. I'm glad that I stuck with 1.6.3
Wow, mine just started 2 mins before this thread went up. I was sitting at my desk and saw it reboot and now it won't stop. It actually loads up Android entirely, gets to Lockscreen and then restarts.
zskate311 said:
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone using the GB Radios (ie everyone on GB but CM7 users)
jcase said:
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Click to expand...
Click to collapse
Ah didn't see that. Does bootloader not work?
Well crap, back to froyo I go then, just to be safe.
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
I actually think I read about this somewhere else in the forums. I don't know if he was running gb but I'm guessing so. Thanks for this, I'll be reverting back later.
Sent from my ADR6400L using XDA Premium App
adrynalyne said:
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
Click to expand...
Click to collapse
It's all your fault.
Sent from my ADR6400L using XDA Premium App
reverting now... can I just flash a froyo radio and rom or do I have do the whole process in OP?
Thanks for looking out for us
Sent from my ADR6400L using XDA App
Thanks for the heads-up!
Might as well Nandroid my Ginger builds so I have them for when we get a more stable radio release. Curses Verizon! I will miss my Sense 3 elements!
This sucks! Thanks for the heads up, though, Justin!
Bootloader works. I ran into this problem once. Have a backup of the ruu handy. It will get you back to a stock rooted froyo state
Btw...I'm staying on gb. Ill take a risk.
Well I have had my Xoom now for about a month. I use it pretty heavily and as soon as I got it I rooted it and installed Tiamats v1.4.4 kernel with OC'd GPU. I was running pretty flawless OC'd to 1.5Ghz until last night. I was in the middle of reading some posts on here on tapatalk and out of the blue the screen went black and rebooted. It was stuck on the spash screen for 20 minutes. I tried a hard boot and got bootloops.
I then downloaded the stock images and reflashed it back to stock and even relocked the bootloader. Still bootloops. I ended up flashing the stock images like 3 times in all with the same results. Sometimes I can get into the OS and go through setup and sometimes not. Most of the time if I can get into android apps start force closing and it reboots, or the touchscreen becomes unresponsive. I noticed most of the time when rebooting I get bright white flashes of light on the splash screen. Here is a video of the boot sequence:
http://www.youtube.com/watch?v=1ctODeIPANU&feature=player_profilepage
Around 1 minute into the video you can see the white flashes of light. Anyone know if there is any chance of recovering this? BTW, its a verizon 3g xoom. I'm pretty sure its a brick. I just wanted to see if anyone else had seen this same thing happen.
EDIT: I also noticed that sometimes the front camera is flashing red also when rebooting. Weird.
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
okantomi said:
Had you updated any apps like superuser or busybox installer? Were you able to do a nandroid recovery through CMR? What stock files did you flash (what version?) I'll bet you are not completely bricked...there seems to be a fix for almost every crash. It's just that without knowing anything about why it may have crashed or exactly what you did afterwards it hard to know how to help.
Click to expand...
Click to collapse
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
sabbotage said:
I didn't update anything at all. I tried my stock nandroid and it locked up too. I tried flashing both factory images for the VZW xoom from motorolas website and they both do the same thing. I've never seen it lock up so much and the screen become unresponsive like it is. Restoring it to factory should fix it and after 3 times of flashing the stock images it should be fine, but its not. The stock files I tried were MZ600_HRI39 and MZ600_HRI66. I'm not sure what else to even try. The flashing white screen and the camera flashing red are definitely not a good sign.
Click to expand...
Click to collapse
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
okantomi said:
Wow, maybe you have a hardware failure. Did it act funky before at all? I saw that it just bootloops by itself...can you still get it into any kind of recovery? I think that if you can get into fastboot and use adb, you can do a wipe and maybe start over. Of course it you have a hardware fail that's another issue.
Click to expand...
Click to collapse
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
sabbotage said:
Yeah i can get into fastboot and I tried erasing everything before reflashing the stock images with no luck.
Sent from my HTC Thunderbolt using Tapatalk
Click to expand...
Click to collapse
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
okantomi said:
If you can go to the IRC Xoom Channel you could chat with people who know much more than I do. I think with your weird light flashes and continuous boot cycle, that might be your best bet. The address is in brd's signature line.
I sincerely wish you good luck!
Click to expand...
Click to collapse
Thanks I jumped on there and i'll see what everyone says. I've tried it all and nothing is working.
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium
This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.
Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...
Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!
TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.
TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
scythefwd said:
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
Click to expand...
Click to collapse
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
lj50036 said:
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
Click to expand...
Click to collapse
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
scythefwd said:
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
Click to expand...
Click to collapse
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
charesa39 said:
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
Click to expand...
Click to collapse
Like hit them and let go, or till it reboots again?
scythefwd said:
Like hit them and let go, or till it reboots again?
Click to expand...
Click to collapse
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
charesa39 said:
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
Click to expand...
Click to collapse
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
scythefwd said:
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
Click to expand...
Click to collapse
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
charesa39 said:
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
Click to expand...
Click to collapse
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
scythefwd said:
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
Click to expand...
Click to collapse
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
charesa39 said:
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
scythefwd said:
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
Click to expand...
Click to collapse
Thx for taking the time to learn mate, Let us know when you get it back
Thx Josh