Database Users

[Q] Need help restoring my N7 after a crash...

Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!

OldDogEyes said:
Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!
Click to expand...
Click to collapse
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/

Oli1122 said:
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks

OldDogEyes said:
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks
Click to expand...
Click to collapse
Yes locking and unlocking your bootloader will wipe all data as far as Im aware. I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors. You could try to pull your nandroid back up using adb to see if theres anything salvageable from it and Id redo everything on your device. Heres a link to a bunch of useful ADB commands which may help ya out. ADB useful commands

cjsspape said:
I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors.
Click to expand...
Click to collapse
That is true. As you can tell I am semi-knowledgeable but not as proficient as many.
So I thought that the Nandroid backup was divided into different pieces... And that I could choose which pieces to restore and by doing that, just restore the portion of my tablet that represented the 'setup' (apps, layout, etc) but not the OS... Maybe I'm wrong about that...
As for ADB, yes, I thought about that as well and already did an ADB Pull to grab the Nandroid ... now I'm doing one to grab everything on the SD Card.
Thanks for that!

Yeh you should be fine so long as you backup your sd before hand. You can also use the same nexus tool to backup your apps and restore them using the developer tools backup

[Q] Need help. OS was wiped using TWRP v2.3.2.1

hello all. I really need some help. I let my friend play around with my nexus 7 and he got into the TWRP and accidentally wiped everything off my nexus including the OS so now when i boot it just hangs on the google splash screen. I can get into fastboot mode and the team win bootloader screen but thats it. When i connect to my computer it is not recognized so i cant drag and drop a new boot image. I would just like to have my nexus back to factory unrooted bone stock
Please help me out. I'm new to the android scene and freaked out that i have a bricked device.
Thanks in advance!

1ll3st said:
hello all. I really need some help. I let my friend play around with my nexus 7 and he got into the TWRP and accidentally wiped everything off my nexus including the OS so now when i boot it just hangs on the google splash screen. I can get into fastboot mode and the team win bootloader screen but thats it. When i connect to my computer it is not recognized so i cant drag and drop a new boot image. I would just like to have my nexus back to factory unrooted bone stock
Please help me out. I'm new to the android scene and freaked out that i have a bricked device.
Thanks in advance!
Click to expand...
Click to collapse
First of all, stay calm! :good:
If you are able to reach fastboot mode, nothing of value is lost (beside your personal data). You can just follow this guide.
At the end, your Nexus will be as fine as before. And don't forget to threaten your friend not to do such things again if he doesn't understand how to repair it.
P.S.: You don't have to unlock (flashing step 2) and re-lock (flashing step 5) your Nexus as you may have unlocked it before (according to information about installed TWRP). And be sure to use the nakasig/Tilapia image for flashing.

1ll3st said:
hello all. I really need some help. I let my friend play around with my nexus 7 and he got into the TWRP and accidentally wiped everything off my nexus including the OS so now when i boot it just hangs on the google splash screen. I can get into fastboot mode and the team win bootloader screen but thats it. When i connect to my computer it is not recognized so i cant drag and drop a new boot image. I would just like to have my nexus back to factory unrooted bone stock
Please help me out. I'm new to the android scene and freaked out that i have a bricked device.
Thanks in advance!
Click to expand...
Click to collapse
is this guy still your friend?! why would anyone go into recovery on someone else's device? sounds like he C.I.A'd you lol

kistenschieber said:
First of all, stay calm! :good:
If you are able to reach fastboot mode, nothing of value is lost (beside your personal data). You can just follow this guide.
At the end, your Nexus will be as fine as before. And don't forget to threaten your friend not to do such things again if he doesn't understand how to repair it.
P.S.: You don't have to unlock (flashing step 2) and re-lock (flashing step 5) your Nexus as you may have unlocked it before (according to information about installed TWRP). And be sure to use the nakasig/Tilapia image for flashing.
Click to expand...
Click to collapse
Thanks I'll try that guide out tonight after work.
How it happened was I received the OTA update for 4.2.2, but didn't update. So when I let him use the tablet he thought he was being nice by updating for me and when the nexus reset it kicked into TWRP which he thought he f*ucked up and decided to "wipe" what he did.

Odp: [Q] Need help. OS was wiped using TWRP v2.3.2.1
1ll3st said:
Thanks I'll try that guide out tonight after work.
How it happened was I received the OTA update for 4.2.2, but didn't update. So when I let him use the tablet he thought he was being nice by updating for me and when the nexus reset it kicked into TWRP which he thought he f*ucked up and decided to "wipe" what he did.
Click to expand...
Click to collapse
That's the reason why I don't let anyone (even my best friends) to do anything on my phone without me looking what they are doing ATM. You should have done the same.
All your data you've had on your phone/tablet is permanently gone, all you have to do now is to restore your os from a backup (if you have made backup before) or flash other ROM and you are good to go
For the future knowledge - if you can access any recovery mode it's almost impossible that your phone is bricked. If you can only enter fastboot there is like one percent chance of this that your phone / tablet is bricked.
Sent from my R800i using xda premium

You could flash a recovery with fastboot < fastboot flash recovery recovery.img > (just necessary if TWRP got wiped during the update) and then push a ROM with adb.
This method wouldn't delete your SD card.

How do you know that he just didn't wipe system? It's possible that he didn't, so all you may need to do is flash the system image. If you have driver issues while in fastboot, I recommend the official Asus drivers.
Sent from my Nexus 7 using Tapatalk HD

[Q] Bricked Nexus 4

Hi, It may not be completely bricked but as far as I am concerned it is. I tried to free up some space on the phone by formatting everything in ClockworkMod. Factory resets did nothing and the phone showed I had used over 10 GB. I figured formating was just going to clear out all the backups and old files.
As of now I can get into recovery but that's about it. When I try to reboot all it does is bring up the words GOOGLE. My PC wont recognize it as I cant enable USB debugging. I thought if I could just drag a new rom, gapps, zip file into the internal storage I would be good. I also thought I might be able to restore it to stock with a toolkit but again they request USB debugging on.
I am real new to this so any help would be greatly appreciated. Is there a way to bring this phone back to life in some sort of straight forward way?
PS. As of this morning things seem to have gotten worse. I used a toolkit to try and get things working and now I cant boot into recovery. All I get is the robot on its back with red triangle icon. I can press power, then volume up and get another menu but I am really at a loss. Any further help would be great. Thanks.
Thanks

You're definitely not bricked.
You must restore the factory image, which you can find from Google... Google "nexus factory image" and restore in bootloader mode.
I'm not going to go into detail on how to restore, there are dozens of threads on how to do that. Start by Googling "how to flash nexus factory images"...
I'm assuming that since you've dabbled with modifying your Nexus that you are familiar with the super duper important ADB/Fastboot procedures? If not, you've got a lot to learn before you start messing with your phone...
Edit: You can also attempt to ADB push a stock rooted ROM (only so you don't have to mess with gapps at the moment) through your custom recovery. Again though, do your due diligence and read before messing with this sort of thing.
Sent from my Nexus 4 using xda premium

Just sideload a rom with adb.

adb push a ROM into your memory via cmd prompt. I think you can adb push data using the Nexus 4 toolkit in the stickies.
When you figure out how to push files into your phone, flash the new ROM.

Alternatively, use efrant's guide from my signature. The only correct & educative way of returning to stock. Avoid toolkits!

Did I hardbrick my nexus?

New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even get to the red android error screen.I am forever stuck at the GOOGLE screen or a blank one. When stuck at the google screen it is recognized as Nexus7 but when i try to reset to bootloader (black screen) its QHSUSB_DLOAD.
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.

vinland123 said:
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even turn it on. My device manager recognizes the nexus 7 as "QHSUSB_DLOAD"
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
Click to expand...
Click to collapse
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.

cgehring said:
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
Click to expand...
Click to collapse
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.

http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution

Aria807 said:
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Click to expand...
Click to collapse
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?

vinland123 said:
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
Click to expand...
Click to collapse
If you can get to your bootloader, and follow directions, then the above will work. Good luck!

It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?

vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Why did you try to install the factory images from the old Nexus 7?

vinland123 said:
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
Click to expand...
Click to collapse
Glad to hear you got it running again!

http://forum.xda-developers.com/showthread.php?t=2381438
Try this. I had the exact same problem as yours and I fixed it. This works!

vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Not sure if you are clear on this or not but the Nakasi image is for the old Nexus 7. The new Nexus 7 is named Flo and the official Google image will have that as part of the file name (Google still hasn't released a factory image for our device though. However, there are a few unofficial versions floating around on the forum).

[Q] Trying to backup an encrypted RAZR M

Ok, I'm new at this, here's what I've got, hopefully someone can shed some light:
-My RAZR M is fully encrypted
-It is successfully rooted
-I have installed Rom Manager with CWM 6 as the custom recovery
-I want to make a NANDROID backup (to eventually install Carbon), but whenever I try to reboot into the backup/recovery mode, it won't, it goes to what I think is the ADB screen? Not sure tho, this screen says "Connect data USB." Then, when I do, it just changes state and says USB connected, nothing else happens. Then I just reboot the phone normally and everything still works.
So after googling and researching a lot, I'm assuming since my phone is encrypted it won't access the CWM because it never asks me for my password to decrypt the internal storage. Ok cool, but here's my question now tho; if I perform a Factory Reset from the settings menu, will it actually do the reset and reinstall itself since I have CWM installed??
Thanks for any help.

Anyone got any ideas??

Is your bootloader unlocked?
Sent from my XT907 using xda app-developers app

Hmm. Is this screen where it says "Device is LOCKED" mean that my bootloader is locked? Btw, this is the screen that I referred to in my first post. It comes up whenever I try to select "Recovery"

Your bootloader is locked and on that version it can not be unlocked... So... unfortunately you can not install a custom recovery... Well you can use safestrap but the ROM selection is very limited...
Sent from my XT907 using xda app-developers app

So you say I cannot install a custom recovery, do you mean a different ROM that I would "recover" to install it? Or do you mean ClockworkMod (and its various counterparts)? Because in the ROM Manager app, it says I have CWM 6.0.4.4 as my "current recovery" (see attached screenshot)
Please forgive me if this is a dumb question lol but like I said, I'm new at this whole thing

It does say that huh unsure as to why... i do have a locked M around here somewhere ill see if it does the same thing to it...When I say custom recovery I do refer to cmw n twrp... With a locked bootloader you can not install those... we have for safestrap as a recovery for locked bootloaders it's been a year since I used it but I believe you can make backups on it... I would just sit tight and.wait on kit kat it shouldn't be to much longer... till then just freeze all the bloat and use xpossed to your liking... When kk comes out I'm sure development will pick up for locked bootloaders again..anyone else with more experience care to provide more in depth assistance..
Sent from my XT907 using xda app-developers app

So any further advice on what I can or can't do?
I would like to perform a factory reset on my device to get rid of this stupid encryption (it slows everything down), but with CWM installed (supposedly?), can I still do a factory reset? I guess what I'm trying to get at is what does the factory reset option use to re-flash everything from? The recovery partition where CWM is now supposedly installed? Will that affect the factory reset?
I hope this makes sense, I don't want to brick my phone...

Alrighty, for anyone interested:
I never tried the factory reset. What I did do is try the OTA KitKat update just like 2 hours ago. That was a mistake; upon downloading and automatically rebooting to start the upgrade, my phone would not reboot, it got stuck at the AP Fastboot screen with the error code 0x56 (see attached picture).
So, I powered off and powered on my phone, at which point it powered up normally, until after about 2 minutes on the home screen, it automatically rebooted itself (to presumably "continue" trying to install the OTA). Then it got stuck again on the AP Fastboot screen. This continued over and over and I soon realized I soft bricked my phone.
Did some further research, found the House of Moto program (http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/) which saved my life. If anyone is having any issues similar to the situation I was having, or just issues with the KitKat OTA, this House of Moto program will restore your phone to completely stock. Just follow the instructions on that web page exactly. Kudos to the dude who developed that.