Related
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you ill try that. it was at 33% battery when this happened though
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
i know about the screen time out, i tapped the screen for it to rewake and it didnt work, then i tried pressing the sleep button once for it to unlock and that didnt work. so it indeed shutoff
frap129 said:
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Click to expand...
Click to collapse
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.
Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.
For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.
good luck
** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.
bftb0 said:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Click to expand...
Click to collapse
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
frap129 said:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
Click to expand...
Click to collapse
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
bftb0 said:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
Click to expand...
Click to collapse
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
frap129 said:
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
Click to expand...
Click to collapse
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Odin is Samsung only
Sent from my Galaxy Nexus
You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.
This is all I know!
Sent from my Nexus 7 using xda premium
NEXUS 7 Bricked - NO OS - tried everything but...
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.
Installing drivers does not need android to be booted.
Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.
Sent from my Galaxy Nexus
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.
Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.
----------------------
Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...
Copy whatever ROM .zip you want into this folder.
The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.
Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.
Open a command prompt window on the aforementioned folder... and type...
Code:
adb devices
...which should yield something like the following...
Code:
List of devices attached
012345679ABCDEF recovery
(If you don't see a serial number... then you definitely have a driver problem...)
Otherwise, it's just...
Code:
adb push smooth.zip /sdcard
Or whatever ROM you wish to 'push' to the emulated SD card.
This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience a liitle. You can always pull up another command prompt window and type adb devices again to ensure you still have an ongoing ADB connection.
Once copied over, and still in TWRP, you can just flash it.
Good luck.
Rgrds,
Ged.
Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o
If You familiar with Linux, You can try to understand the logic of
changing the modes.
You need to run udevadm monitor in one terminal. Then press some
combinations of key/s and look for changes with usb-devices.
The better, if You run wireshark and sniff USB interface with your device.
Put attachment here, with a comments what was pressed.
since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.
Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance
Have you tried using a different usb port on the PC, and rebooting the PC?
bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.
When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!
Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.
bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out
I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this
Same deal here! Not sure what to do short of wiping and losing my info.
Same here...any advice? Not sure what happened. OTA update too.
Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)
Same boat here, even sideloaded the factory image via ADB.
[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".
Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk
Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)
killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.
tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.
Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839