Develop Bugs

Any way to save data on a Nexus in a bootloop?

I have a Galaxy Nexus that after updating is stuck in a boot loop just recycling the Google logo. There is no ADB access as a result.
Is there anyway I can save my photos? Thanks!

You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data

Like Eddy said. Via fastboot, boot up CWM, either you have it flashed or not.
From CWM, you can access the phone via adb over USB.
In a "adb shell", you can .tar.gz up the stuff you like (or your entire /sdcard). Afterwards you can "adb pull" that off the phone.
Requires quite a bit off commandline, but it's not hard, just cumbersome. If your data is important enough, it's definitely worth it.

EddyOS said:
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Click to expand...
Click to collapse
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...

It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?

efrant said:
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
Click to expand...
Click to collapse
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off

Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
Correct. If your bootloader is locked, you're out of luck. Unlocking wipes everything.

EddyOS said:
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Click to expand...
Click to collapse
Once you boot up CWM, you have adb access to the files on your device. Not sure what "mount" you are talking about, but I have never had to do anything to get files off/on the /sdcard directory other than boot up CWM or my ROM.
Sent from my Galaxy Nexus using Tapatalk

Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
You are not mistaken. In that case, try booting to the stock recovery and use the adb pull command.
Sent from my Galaxy Nexus using Tapatalk

Boot loop
If you are having difficulty with boot loop, pull the battery. I had the same issue with my N1 didn't wipe dalvik cache after an update. And because of the loop couldn't get the timing for fastboot as the bootloop was not giving an indication of when the keypresses would activate the bootloader.
If you are unrooted and stock then try this:
Put device into the bootloader by holding down Vol Up + Vol Down + Power
use your volume buttons to change options next select (with power button) the fastboot option, after use the ADB instructions from the more knowledgeable members (ADB is somewhat cumbersome.... but it works and has saved my bacon) After wards using the Bootloader you should be able to resore to factory settings and reload your info after.
If you are Rooted with a custom bootloader and rom
same as above to get to bootloader, but then wipe your cache, and dalvik cache. Reflash latest ROM and Gapps. You shouldnt lose anything.
Good luck bud.... your Nexus isn't dead.... only in a Coma.... or a political promise...
J

You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846

danger-rat said:
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
Click to expand...
Click to collapse
Have you tried and gotten that to work in recovery? Although I haven't tried it, I don't think that works in recovery. It is a feature of ICS, so I'm pretty sure you need to be booted into your ROM for it to work.
Sent from my Galaxy Nexus using Tapatalk

sos lge960
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency

bibi019 said:
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
Click to expand...
Click to collapse
My guess is this question is more appropriate for the nexus 4 forum
Sent from my Galaxy Nexus

Nooooo, necrobumping is fine, since he has the same issue, and this is the first hit on Google... even though he's on a different device. /s
Sent from my Nexus

Hey, I'm running to a similar problem with this guy.
I stupidly reformated my system files without having a rom on my internal sd.
The question is that I'm reading that I can use the adb to push files in but I'm just new to the whole adb.
How would I get my computer to use the adb?
Sorry for such a noob question -_-;
Edit: So it seems from looking around and reading other forums and faq's that I need to have the phone for the adb to be installed.
Is there away around that so that I can access the adb?
Edit2: Nevermind. Fixed it with a toolkit. Sorry to spam

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

[Q] Wiped /system accidentally, no .zip on device - help?

Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab

habylab said:
Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab
Click to expand...
Click to collapse
A factory reset wipes the data and cache, any changes made to the system will still be there after a factory reset. Flashing the complete factory image will also wipe everything. The userdata.img inside the factory image is what wipes everything. You could flash all the images inside the factory image separately except for the userdata image and your data will stay intact.
If you can see it in fastboot just fastboot flash the system.img and the boot.img. Get the "correct" system.img and boot.img (you have to extract the images from a factory image) and put them inside the platform-tools folder of the sdk, manually put your device in fastboot, plug it in to the computer, shift-right click from inside the platform-tools folder, choose "Open command window here," type fastboot devices and you should see your device, type fastboot flash boot boot.img, hit enter then fastboot flash system system.img hit enter. Type fastboot reboot hit enter and your device should reboot normally! All of your data will still be intact. This might be useful 15 seconds ADB Installer v1.3, I personally have the full sdk installed but I did try the ADB installer on my brother's laptop a few months ago.

[Q] Issues with ADB

So I have just taken my One X from stock, unrooted, and am attempting to put CM on it.
I had no problems using adb or fastboot until I flashed CWM, I am still able to see the device using fastboot (when in fastboot) but in recovery on CWM 'adb devices' comes up blank.
I have tried doing kill-server/start-server, restarting my phone and laptop, updated all my drivers and followed the advice given in every other thread I could find to no avail, what should I try next?
Thanks in advance.

Resolved
I ended up resolving this by placing the phone in mass storage mode, moving the zip file like you would on a flash drive and installing it from there with no ADB interface. If you intend to do this DO NOT put the zip in any sub-folder, just save it to /sdcard/. I made the mistake of saving it to .android-secure which CWM can not see, to install I had to reflash to twrp to move the .zip and then go back to CWM to install, much more hassle than was necessary!

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!