Database Users

I think i bricked it!! Help me please!

So I installed Paranoid rom and wiped just like normal but now its stuck at the JB splash screen. My pc wont recognize it in fastboot and I cant get into recovery. Did I brick this thing or what?

poliati said:
So I installed Paranoid rom and wiped just like normal but now its stuck at the JB splash screen. My pc wont recognize it in fastboot and I cant get into recovery. Did I brick this thing or what?
Click to expand...
Click to collapse
how do you know for sure its not recognizing it in bootloader?

When I plug in my nexus I can't do anything. The hardware buttons don't work. I don't see anything in the drivers when I plug it in either.
Sent from my HTC One X using xda premium

Well, just to let you know, you haven't bricked it. Bricking something means you can't access the device what so ever i.e. it won't boot, won't go into recovery/bootloader mode etc. As to fixing it, I'm not sure. Can the device turn off and on? Have you got drivers installed properly (was fastboot and adb working before this happened)?

deleted

I am sure you tried every option , have you tried adb reboot recovery command, when u turn on phone, or adb reboot bootloader. If the manual way does not work, for example when device is powered off (volume down then holding power for 10 seconds). Let me know. Need more details.
Sent from my HTC Glacier using xda premium

Ok I'm trying that now.
Sent from my HTC One X using xda premium

Hi I think I'm facing the same issue as poliati. I tried to flash it back to stock image but the process freezes at "sending 'system' <438656kb>. Can someone please help?

r1tesh said:
I am sure you tried every option , have you tried adb reboot recovery command, when u turn on phone, or adb reboot bootloader. If the manual way does not work, for example when device is powered off (volume down then holding power for 10 seconds). Let me know. Need more details.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
So rebooting isnt the problem but getting into recovery or even getting my computer to recognize my device is what i need help with. The entire thing freezes when im in bootloader and try to plug into my computer. So i have to reset by holding down the power button. Ive installed and uninstalled drivers through wugfresh toolkit and nexus 7 toolkit.

poliati said:
So rebooting isnt the problem but getting into recovery or even getting my computer to recognize my device is what i need help with. The entire thing freezes when im in bootloader and try to plug into my computer. So i have to reset by holding down the power button. Ive installed and uninstalled drivers through wugfresh toolkit and nexus 7 toolkit.
Click to expand...
Click to collapse
Try plugging in and then going to boot loader.
Sent from my Nexus 7 using xda premium

When I plug it in, I can't do anything at all.
Sent from my HTC One X using xda premium

CharliesTheMan said:
Try plugging in and then going to boot loader.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That doesnt work either. The thing is, I can use the volume buttons BEFORE I plug it in, but as soon as I plug it into a computer the tablet freezes and i have to reset it.

So ive uninstalled all drivers including the SDK and reinstalled everything and im still stuck at the bootloader. Im starting to believe that its pretty much a lost cause. Can anyone help with trying to figure out what i may have to do now.

If you can get into the bootloader, you're not bricked, nor is it a lost cause.
Since you uninstalled them reinstall the drivers. Download the factory image (nakasi) from here, and then follow these instructions to use cmd and fastboot to reflash the stock ROM.

Ok I will try this.

Freakin love this site!!!
OK, so i now have everything up and running after about 2 hours of uninstalling and installing everything. Turns out that my cpu (or me) was duplicating the drivers. I feel dumb for that

[Q] Stuck in FTM Mode?

Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")​
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?

Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.

Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.

OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!

Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2

drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem

ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install

same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help

[Q] Fully Bricked n7?

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.

[Q] nexus 4 Any way to copy data (broken touch input - physical buttons work fine)

Dropped my nexus 4 yesterday and it fell right on the edge of the screen shattering it. First time I've broken a phone, and this one seems like a particularly bad one to have broken - no reasonable price screen replacement with the screen attached to the digitizer.
Anyway the phone boots up and charges fine, but I can't unlock it, which means my computer isn't connecting to it. Is there any way I can save all of my photos and other files?

Is USB debugging enabled?
Sent using xda-developers app

Chromium_ said:
Is USB debugging enabled?
Sent using xda-developers app
Click to expand...
Click to collapse
I believe so. But I have no way to check.

foofiebeast said:
I believe so. But I have no way to check.
Click to expand...
Click to collapse
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?

foofiebeast said:
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?
Click to expand...
Click to collapse
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app

Chromium_ said:
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks mucho, I will try to get that set up now.

Set it up, but no devices listed
It's frustrating because it's so tantalizingly close. I have a pretty good idea that when I send it in to LG they are probably just going to send a different refurb back. I find it hard to believe that they do a 1 to 1 repair job on each phone that comes in.

foofiebeast said:
Set it up, but no devices listed
Click to expand...
Click to collapse
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app

Search for how to unlock the bootloader without wiping all your data. Would be moot otherwise...
Of course if all that's been done in the past and you already have cwm/twrp, just boot to that and you'll be able to adb in.
Also, you can hold onto the power button for 10s to force it to power down.

EDIT: restarted and tried again, making some progress now.

foofiebeast said:
Doesn't work because I can't enable usb debugging.
Click to expand...
Click to collapse
Again, that's why we go into cwm/twrp. Insecure debugging is enabled there.

Awesome, it appears to be copying everything over now!
Can't thank you enough! Just saved a years worth of pictures and videos, that pretty much chronicle the start of my current relationship up to the present.
Of course right now it is just pulling all of the EA real racing data, but I assume it will eventually get to the pictures, haha.

Chromium_ said:
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app
Click to expand...
Click to collapse
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance

likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4

hackergnome said:
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4
thank you but how exactly do you do that
Click to expand...
Click to collapse

likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
you don't save as google contacts?

Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908

TMc1908 said:
Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908
Click to expand...
Click to collapse
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?

Chromium_ said:
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?
Click to expand...
Click to collapse
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908

TMc1908 said:
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908
Click to expand...
Click to collapse
Before you can run the adb pull command, you'll need to get your phone recognized by "adb devices". Try installing Koush's adb driver.

[Q] Update to 4.4 brick

Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!

Same problem here. I'm running a pure stock. In rooted device and it bricked on me.
Sent from my SGH-M919 using XDA Premium 4 mobile app

theblackout said:
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Click to expand...
Click to collapse
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.

noradoor said:
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
Click to expand...
Click to collapse
Same thing using that thread, I.
fastboot erase system
fastboot flash system system.img (old 4.3 img)
stuck on sending system <529061 KB>
getting nervous here, any other ideas?

OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it

theblackout said:
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
Click to expand...
Click to collapse
I will try this when i get home from work and see how it goes.

Ksealy03 said:
I will try this when i get home from work and see how it goes.
Click to expand...
Click to collapse
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.

GedBlake said:
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ok im actually trying it now. i have a different USB cable that I will use.

teraonic 318
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.

Ksealy03 said:
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Click to expand...
Click to collapse
I had a similar issue that I was able to fix. Hopefully this will help you too.
I have a Nexus 7 that is rooted, stock ROM, unlocked bootloader. I have gotten many OTA updates since buying the device, and all previous OTA updates have completed without a hitch.
On the most recent OTA Kit Kat update, the device froze when trying to apply the update. It just displayed the boot animation in perpetuity.
I was able to use the Nexus Toolkit here on XDA (LINK) to load the stock Kit Kat ROM. Hope that helps.