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

Cant write to/view Interal storage [GNEX]

I cant not view files on my internal SD card. For example pictures in the gallery only display blank thumbnails but ARE THERE. This means i cant download anything and save it (Apps from the play store are fine) but i CAN view files with no problem while connected to a computer and move files to my phone on there with no issues but downloading straight to the phone wont work. I was flasing experemental roms when this happend and yes, i did make a back up but this made no diffrence. I have flashed stock 4.0.2, 4.0.3, locked the bootloader, unroooted, re unlocked the bootloader but the problem persists. Any idea's anyone?

Can you clarify if it's only existing files that are already on your phone, or does this happen for all new files created on your phone as well (taking new photos and videos for example).
Sent from my Galaxy Nexus using Tapatalk

-
Yes it does, but apps are not effected. But these are put on a diffrent space on the phone i think. But no, for example when i take a picture it will not save it, i cannot download files of the internet either. Any idea's would be appreciated

JustArchiee said:
[snip]
Any idea's would be appreciated
Click to expand...
Click to collapse
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.

efrant said:
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.
Click to expand...
Click to collapse
+ 1
Sent from my Galaxy Nexus using Tapatalk

Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?

How to wipe your device completely
JustArchiee said:
Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?
Click to expand...
Click to collapse
N00b step-by-step
1) Ensure you have the drivers installed properly on you computer;
2) Copy everything you want to keep off of your device (i.e., to the cloud, to your computer, etc.);
3) Reboot your device into fastboot mode: turn it off, then hold vol+ & vol- & press and hold power;
4) Plug your GN to your computer;
5) Download the attachment to your computer, and extract the contents to a directory;
5a) Download this and extract the files within to the same directory (extract ALL archives, including the zip inside the second archive);
6) Open a command prompt in that directory;
7) Make sure your computer recognizes your device by typing: fastboot devices
8) Wipe everything by typing the following:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
9) Flash the ICL53F system partition: fastboot flash system system.img
10) Flash the ICL53F data partition: fastboot flash userdata userdata.img
11) Flash the ICL53F boot partition: fastboot flash boot boot.img
12) Download CWM from here, save it to the same directory and rename it to cwm.img
13) Flash CWM: fastboot flash recovery cwm.img
14) Now you are on the stock ROM with CWM recovery. You can flash whatever ROM you want now in recovery.

Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?

Ahh don't worry i used wugfreash to flash everything. Thanks so much for you help - Will donate

JustArchiee said:
Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?
Click to expand...
Click to collapse
For others whovarevhaving that issue: you need to extract ALL the archives. There is a zip inside the archive inside the main archive...
Sent from my Galaxy Nexus using Tapatalk

This may have been a permissions issue. I wish I'd replied sooner
Sometimes pushing files to /sdcard from an incorrectly programmed ROM or over ADB in recovery can result in making "root" the owner of all the files. I experienced this when I pushed a bunch of files to my phone over ADB while in ClockworkMod.
I posted a solution here: http://forum.xda-developers.com/showthread.php?p=23767694

[Q] GNex OTA from 4.1.2 to 4.2 failed, phone bricked :(

Hi guys,
I had my GNex 4.1.2 with SuperSU root survival installed, when upgrading from 4.1.1 to 4.1.2 all went fine. But now, upgrade from 4.1.2 to 4.2 via standard OTA failed and I cannot get through the boot screen with Google text and image of opened lock. Any help would be appreciated.
Thanks.

Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!

manumanfred said:
Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!
Click to expand...
Click to collapse
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?

gabriel31337 said:
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?
Click to expand...
Click to collapse
If you don't want to lose data then you may need to flash manually!
I'm not sure does this keep all data but I think it will keep if just not using fastboot -w command..
Download the factory image and extract files from it to fastboot folder then also extract files from the .zip in .tar package to fastboot folder!
then open CMD (Command prompt) and then write cd /your fastbot folderdestination/ Example: cd C:\GalaxyNexusRootNew
and then when those is done then use exactly these commands:
Code:
fastboot flash bootloader bootloader-maguro-primelc03.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-maguro-i9250xxlh1.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
and finally:
Code:
fastboot reboot
and if that does not work then
Code:
fastboot-reboot

manumanfred said:
Code:
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.

easy way
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.

gabriel31337 said:
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.
Click to expand...
Click to collapse
not actually, it may boot well but may cause some issue so later in CWM wipe dalvik cache and cache

themaskofwraith said:
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.
Click to expand...
Click to collapse
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.

gabriel31337 said:
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.
Click to expand...
Click to collapse
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..

manumanfred said:
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..
Click to expand...
Click to collapse
I don't want to mess with CWM or anything else non factory (apart from SuperSU ). I have restored the phone to 4.2.1 and rooted, apps and data have survived so I'm very happy again. Thanks a lot for your guidance. :good:

[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.

January security update?

I received the download on my 5x that's rooted. Will this break root for me?

Yes but you can easily re-root after re-installing TWRP

bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?

Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview

This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes

Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!

SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.

gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk

jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.

Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"

ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.