Related
A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app
A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue
I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.
Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers app
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
unlock bootloader
wcorey1974 said:
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
Click to expand...
Click to collapse
Also forgot to add, hen I try and run recovery from toolkit it tells me to unlock bootloader, when I try to unlock bootloadermy nexus asks me if I want to then when I hit yes, unlock it gives me neither usp nor cac partitions found.
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Dark Jedi said:
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Dark Jedi said:
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It sat in erasing for 1 hour and didnt do anything. I was doing factory reset in recovery.
As long as the boot loader starts you can recover your Nexus. Check this guide: http://forum.xda-developers.com/showthread.php?t=1907796
If he can't unlock the bootloader then there's not a whole lot he can do. Run "fastboot getvar all" while in bootloader and tell us what it says please. If adb is seeing your phone in recovery, then run an adb shell and do "ls -l /dev/block/platform/sdhci-tegra.3/by-name/" please.
Sorry I can't help further but I just got this and don't know much. I am glad others came in to give you more help.
Sent from my Nexus 7 using Tapatalk HD
Damn... I didn't see he can't unlock the bootloader. This is going to be difficult.
wcorey1974 said:
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
Click to expand...
Click to collapse
Im exact in the same situation. No rooted phone, nexus wont boot anymore, cant dont anything in the bootloader section ...
I would be extremley thankfull for hints how to fix this issue.
Cheers
Papa
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
tnt0303 said:
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
But this will void my warranty right ?
They have no way in knowing you pulled your back cover off. Just be careful so not to leave pry marks. Only way they will know is if you tell them you did it.
Sent from my Nexus 7 using Tapatalk HD
Hello All,
About 2 days ago i tried to root my google nexus 4, I dont know what i did, but now when i turn it on it shows the google logo then goes to where it shows an android with a red exclamation mark, does anyone know how this can be fixed, any help would be much appreciated!!
Can you be a bit more specific on what you did? Or what guide you followed?
Rooting is quick and easy on a nexus
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
Then flash ROM of choice in recovery
Reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
Ok, i had successfully rooted my phone, i then went to put on a new rom so i could use OTG storage. That got me completely stuck, i tried toget back to my normal phone but didnt know how. I foolishly went into recovery mode, and wiped everything off it. and just now i cant even do anything it just has a red light flashing at the bottom, i hope this has helpt in some way.
Do you have a custom recovery? Use adb sideload to flash the ROM, or if you have a working otg cable this should be fine too
Sent from my Nexus 7 using XDA Premium 4 mobile app
UPDATE: The red light has gone (was just low on power) But the phone is still stuck in recovery mode. i have tried to "apply update from ADB" with my mac but it doesnt work and im not sure if i am doing it propperly.
I am pretty new to this kinda stuff, so i dont know what a custom recovery is, and i honestly have no idea what to do, im not really bothered about the root anymore i would rather just have my phone back to normal.
Please dont take this the wrong way and I mean no disrespect, but maybe we should just get your phone up and running and then maybe a few months from now after you've done a whole lot of reading you can consider rooting again. The n4 isn't the most expensive phone in the world but it would still be a shame to brick it, as much as I believe all androids are best to be rooted the user really needs to understand fully what s/he is doing, 95% of "help my device is bricked" threads come from lack of homework, which is easily 100s of threads a day across xda alone
OK, sorry for the lecture I've just ran into this a lot lately, and I'd be glad to help
I try not to use apple products as a whole so I can't say for sure why its not connecting with adb, is this for sure set up properly? As in has adb or fastboot worked fine in the past? Also is device currently unlocked? By a custom recovery I mean nonstock, not an oem, like twrp or clockwork.
If you want root let's download the latest twrp image for the n4, if you want factory than download latest from here
https://developers.google.com/android/nexus/images?hl=de
Let me know how you want to proceed
Sent from my Nexus 7 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2010312
This will get u up and running.
Next time make sure u know what u are doing.
Credits: efrant
Sent from my Nexus 4 using Tapatalk
Short version: phone won't boot, won't go into download mode, won't properly do a factory reset (tries but doesn't do it), need help.
Finally bricked my phone after tampering with it too much.
I was on the stock KK rom released by LG themselves, no root. Reverted back to the 10c firmware, OTA to 10g, rooted and installed TWRP - flashed a Vodaphone Germany KK ROM for the LG G2 because I heard it had minimal bloatware and no bluetooth wakelock unlike the KK version I was on for T-Mobile (my carrier). It had the touchscreen issue which I never experienced before. Tried multiple times to go back to any T-Mobile LG G2 ROM using the LG Mobile Support Tool - no dice. Uninstalled and reinstalled everything twice. So I figured, oh hey, I probably need to use the Vodaphone Germany JB.kdz file, root that, install TWRP, then flash back to the T-Mobile KK version that I had before. Seemed fool proof in theory. Used the LG Tool to do such, it finished smoothly and now my phone won't boot. It won't do a factory reset (it enters the factory reset mode and it attempts to do one but just reboots). It won't enter download mode either. I think I'm screwed here. Any advice?
I found 2 guides, but to even begin to do the first one I need my phone to enter fastboot mode and I can't find out how to do that anywhere.
you say Won't go into download mode? What happens when you try?
It just shows the first screen as it tries to enter download mode, with the blue dots. The screen that comes after that doesn't happen anymore. It used to switch to it after a few seconds and then the LG Mobile Support Tool could connect to the phone, but it can't anymore.
Sent from my SGH-T989 using xda app-developers app
your phone may be was hard brick, can't do anything
Mine did that once. I complely powered it off and left it alone for 20 minutes and it suddenly worked. Freaked me out
This is what you need http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1
I'm nervous to try that. I have no experience with ubuntu. But I'll give it a go tonight
Sent from my SGH-T989 using xda app-developers app
CHlCKEN said:
Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1
Click to expand...
Click to collapse
would you PLEASE fix your posts so the signature is at the bottom?
The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk
Gonna try what offenberg suggested in a few hours. Fingers crossed
Sent from my SGH-T989 using xda app-developers app
uToTMeH8 said:
The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over $10 a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app
ducidni said:
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
So did they fix it for you under warranty?
or they figure out that you root it and play with it !?
because I'm having the same problem with my f320k and I'm thinking to send it back to Korea
Same is the case with me, my phone is dead for more than 20 days.
here are the details if any one can help?
Hey there,
My phone started bootlooping this morning out of a sudden.
Tried going to recovery to wipe cache etc but not booting in recovery.
Tried adb commands but the phone doesnt detects itself.
Surprisingly/be default the phone is recognised by fastboot commands.
I have some important data in my phone would be glad if it is saved.
Else have to make do with whatever is necessary to bring the phone alive.
When connected this is what it looks like.
Please guide .
Thanks in advance.
You just described the legendary Boot Loop Of Death or more commonly known as BLOD. In my experience with my phone, no way to get anything from the phone once it's in this state. There is a great tutorial by Heisenberg on here. Maybe on of the chapters addresses saving data. Once you give up on the data, do a flash-all.bat using a factory image through fastboot. If you get no errors but continue to boot loop with no access to the recovery, your most likely looking at RMA as your only option.
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
You just described the legendary Boot Loop Of Death or more commonly known as BLOD. In my experience with my phone, no way to get anything from the phone once it's in this state. There is a great tutorial by Heisenberg on here. Maybe on of the chapters addresses saving data. Once you give up on the data, do a flash-all.bat using a factory image through fastboot. If you get no errors but continue to boot loop with no access to the recovery, your most likely looking at RMA as your only option.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I did tried getting it to restore it to stock.
followed https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 post 10.
Still bootlooping.
My phone is out of gurantee so rma is out of question!
Any other suggestions?
divyanshu308 said:
My phone is out of gurantee so rma is out of question!
Any other suggestions?
Click to expand...
Click to collapse
Try pressurizing Huawei and hear what they say.They should be knowing about the issue.
Several people have talked then into doing the RMA by referencing the hundreds of people talking online about it. Just ask them how they can sell a faulty device and not support it.
Sent from my Nexus 6P using XDA-Developers Legacy app
divyanshu308 said:
I did tried getting it to restore it to stock. followed https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 post 10. Still bootlooping. My phone is out of gurantee so rma is out of question! Any other suggestions?
Click to expand...
Click to collapse
It's normal for ADB to not work unless you are in recovery mode. Without ADB you cannot push/pull files from the device. Try to fastboot flash or fastboot boot a TWRP recovery image from your PC. Any errors? Sorry, but If you cannot access recovery mode you are "dead in the water". Options are to start over with a new phone or source a used 6P and swap the motherboard. One guy in Korea found a used one for around USD $60.
v12xke said:
Try to fastboot flash or fastboot boot a TWRP recovery image from your PC. Any errors?.
Click to expand...
Click to collapse
It does flashes fine without any errors.
Doesn't boot into it though!
I was able to boot to recovery mode for once last night but didn't do much help although made me more optimistic about it.
Will try tinkering around more before giving up.
I'm actually flashing every google official image to see if it works on any version.
Will post the result soon.
One more thing if you see the screen shot I posted originally the last shows "Connect USB data cable" but it doesn't shows connected status even though it does gets detected and fastboot command works well.