Develop Bugs

[Q] How do you format internal memory?

I know the formating option in cwm recovery but that only deletes the
data files it does not format the whole internal memory.
So how do you do this? i heard people just use oem lock
and oem unlock to relock the bootloaded and unlock it again since that seems
to wipe everything.
But i wanna know if theres legit command that does formatting of internal
storage for galaxy nexus?

best way is to use the fastboot commands
fastboot oem lock
fastboot oem unlock

0806sung said:
I know the formating option in cwm recovery but that only deletes the
data files it does not format the whole internal memory.
So how do you do this? i heard people just use oem lock
and oem unlock to relock the bootloaded and unlock it again since that seems
to wipe everything.
Click to expand...
Click to collapse
Zepius said:
best way is to use the fastboot commands
fastboot oem lock
fastboot oem unlock
Click to expand...
Click to collapse
That does not erase everything.
0806sung said:
But i wanna know if theres legit command that does formatting of internal
storage for galaxy nexus?
Click to expand...
Click to collapse
Yes. Reboot your device into fastboot and type the following:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Device is now wiped. You will need to flash a new ROM afterwards...

ive followed these steps and done all of the commands but now i cannot flash a rom.
im launched straight to fastboot, (as theres no rom) and it says no boot or recovery img.
i can get into CWM, but i see this.
E:Can't mount /sdcard/
any ideas anyone? think i need to look for a boot.img?

iamdarren said:
ive followed these steps and done all of the commands but now i cannot flash a rom.
im launched straight to fastboot, (as theres no rom) and it says no boot or recovery img.
i can get into CWM, but i see this.
E:Can't mount /sdcard/
any ideas anyone? think i need to look for a boot.img?
Click to expand...
Click to collapse
If you followed my steps above, you have effectively wiped your device (except the bootloader, radio and splash image).
You can't see /sdcard, because /sdcard is just a symlink to /data/media, which you just wiped.
You need to re-flash all the partitions that you just wiped. What ROM are you trying to flash, and how are you trying to flash it? If you are trying to flash a ROM in recovery and need /sdcard, you need to first flash the userdata partition with the stock userdata.img found in one of the images here.

great minds... i have already done that, went here http://code.google.com/android/nexus/images.html#yakju then flashed each .img one by one through nexus toolkit.
booted up into stock already. nice
thanks

I have the battery not charging issue. On top of that I can't fastboot my phone since it is not recognized by my PC. So how can I wipe the internal storage? I have only a certain amount of battery left. And I do not want to send all my private data to Samsung support.

ouilsen said:
I have the battery not charging issue. On top of that I can't fastboot my phone since it is not recognized by my PC. So how can I wipe the internal storage? I have only a certain amount of battery left. And I do not want to send all my private data to Samsung support.
Click to expand...
Click to collapse
Why is it not recognized by your PC. Did you install the drivers properly?

let me introduce u another way :
get to download mode and use oding to flash a new stock rom . if u dont have xda page u can use this to get proper file i used it 5 time with no fail
h t t p : / / androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/#.UBdkTSK42U0
flashing new kernel willerase all internal storage that gnexus let u use
---------- Post added at 09:30 AM ---------- Previous post was at 09:27 AM ----------
but this method will wipe your recovery image , after that u should flash recovery image and su

afraaa said:
let me introduce u another way :
get to download mode and use oding to flash a new stock rom . if u dont have xda page u can use this to get proper file i used it 5 time with no fail
h t t p : / / androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/#.UBdkTSK42U0
flashing new kernel willerase all internal storage that gnexus let u use
---------- Post added at 09:30 AM ---------- Previous post was at 09:27 AM ----------
but this method will wipe your recovery image , after that u should flash recovery image and su
Click to expand...
Click to collapse
Odin is a leaked Samsung tool. If you're suggesting such tool, search around for Heimdall, see if it supports galaxy nexus, if it does, suggest that.

Excuse for digging out an old thread.
Just wanted to check if there is a way to to format internal memory without loosing root?

blinkjona said:
Excuse for digging out an old thread.
Just wanted to check if there is a way to to format internal memory without loosing root?
Click to expand...
Click to collapse
As long as you don't format /system, you won't lose root.
a maguro wrote this.

Thanks. Is there a tool/app to do that please. Or I can just go about and delete
The reason I want to format is after having flashed 4.3( 3 different build) im no longer able to use instagram with an error 'unfortunately,Instagram has stopped' whereas all other things is working fine. I can't clear data/cache Instagram either.
Sent from my Galaxy Nexus using xda app-developers app

blinkjona said:
Thanks. Is there a tool/app to do that please. Or I can just go about and delete
The reason I want to format is after having flashed 4.3( 3 different build) im no longer able to use instagram with an error 'unfortunately,Instagram has stopped' whereas all other things is working fine. I can't clear data/cache Instagram either.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
In your custom recovery
Sent from my Galaxy Nexus

pls help
i have yueka plus yu5510 ,
i've installed cm13 on it.
when i'm wiping its cache using twrp 3.0.8 , it shuts down.
after reboot i tried again then it shows 'failed to mount cache' , 'failed to mount system' , failed to mount data'.
size of internal storage,cache,system become 0 mb.
What have to do ???? pls. help me . i'm stuck .
i tried every thing under my knowledge like erasing and formatting using fastboot .
i tried to flash stock rom cm12.1 but it says "flash write failure".
also cant change twrp to cwm cause of 'flash write failure'.
pls. pls. can someone help me

Hi efrant, it seems that I have exactly the same issue: My evita was a bit slow so I performed a factory reset from the bootloader... stupid idea as it removed the OS (ROM) from my SD. I tried to push a ROM in the device, it said it was successful but there is still nothing on my SD card.
In the bootloader adb is not detecting my phone, fastboot is working though. Sideload is not working.
When i try to wipe anything from TRWP it says : it says "failed to mount 'sdcard' (invalid argument)"
Charac:
EVITA PVT SHIP S-ON RL
HBOOT2.15.0000
TWRP 2.8.7.5
I can't try your solution because I don't know how to flash system, userdata & cache (I know how to flash boot & recovery). Can you help me on this?

antonin2503 said:
Hi efrant, it seems that I have exactly the same issue: My evita was a bit slow so I performed a factory reset from the bootloader... stupid idea as it removed the OS (ROM) from my SD. I tried to push a ROM in the device, it said it was successful but there is still nothing on my SD card.
In the bootloader adb is not detecting my phone, fastboot is working though. Sideload is not working.
When i try to wipe anything from TRWP it says : it says "failed to mount 'sdcard' (invalid argument)"
Charac:
EVITA PVT SHIP S-ON RL
HBOOT2.15.0000
TWRP 2.8.7.5
I can't try your solution because I don't know how to flash system, userdata & cache (I know how to flash boot & recovery). Can you help me on this?
Click to expand...
Click to collapse
I found the solution : Plug the phone to the PC, open in TWRP recovery / click on mount, then the PC ask to format the device, format in fat32. Then copy the rom to the sdcard. Flash it with TWRP. Done!

Galaxy Gio Boot Loops With CPU Tuner

Hey guy im posting on behalf of a mate "Hi. A few days ago, I rooted my Galaxy Gio with an SD Card file that I downloaded (the file was something like Bell___.zip). It worked perfect until yesterday, when I downloaded an app called CPU Tuner from Google Play. After setting it to a battery-saving CPU, it started to lag my whole system. The screen froze and alot of applications forced close when I tried to open them. I decided to reboot my system, however after turning off my phone and taking out the battery (inserting after), it got stuck on the Galaxy Gio boot screen. I kept on trying to boot it, even wiping cache in recovery mode did not do anything. Is there any way I can fix this problem without having to factory reset? (And yes, my phone was fully charged)"
I own an Xperia Play so im clueless when it comes to the gio
Sent from my R800i using Tapatalk 2

1. Nandroid backup
2. Factory reset
3. Advanced restore data partition
Should work
Sent from my HTC Sensation

Back up data only from Recovery
Reflash Stock Rom or the current Rom you're using.

Will the data be lost? He runs the stock kernel, does it have that option?
Sent from my R800i using Tapatalk 2

If he has cwm installed, do what I said and he won't lose data.
Sent from my HTC Sensation

It's I who is the one with the problem with the Gio, and it hasn't been fixed...
Hi, I'm the mate that Zerosuit was posting on behalf of. I originally posted on gbatemp.net (gbatemp.net/topic/328585-galaxy-gio-wont-boot-after-rooting/), however they referred me here after being unable to solve my problem. I installed CWM via recovery mode and installed an update via the 'apply update from sd card' option. It failed to fix any problems, so I tried Odin. The people on GBAtemp say I used the right files (on page 4 of the GBAtemp thread), however now I can't even boot to recovery mode. A warning message appears when I try to boot and says something about going to recovery in Kies. Doesn't work. Only download mode. Kies doesn't work...Anyways, help please!

Codename13 said:
Hi, I'm the mate that Zerosuit was posting on behalf of. I originally posted on gbatemp.net (gbatemp.net/topic/328585-galaxy-gio-wont-boot-after-rooting/), however they referred me here after being unable to solve my problem. I installed CWM via recovery mode and installed an update via the 'apply update from sd card' option. It failed to fix any problems, so I tried Odin. The people on GBAtemp say I used the right files (on page 4 of the GBAtemp thread), however now I can't even boot to recovery mode. A warning message appears when I try to boot and says something about going to recovery in Kies. Doesn't work. Only download mode. Kies doesn't work...Anyways, help please!
Click to expand...
Click to collapse
if you flash the stock recovery from a PC can you go onto recovery on the phone?

Maybe solution
Boot in recovery and connect your phone to your pc
On your phone click mounts&storage -> mount /data.
Download ADB from here: http://motyczko.pl/qtadb/windows_binaries.zip
Place it in a directory and open a command shell and cd to that directory(or go to the folder with adb.exe and hold shift while rightclicking and choose open command prompt here).
Now enter this command: 'adb shell'
You are now in the shell on your phone if the drivers are there(samsung kies needs to be installed)
Do 'cd /data/app' in the cmd, then 'ls'
Look for a apk file that looks like the overclocking app, if you found it do:
'rm <nameofoverclockapp>.apk'
Reboot your phone and have fun

wbrambley said:
if you flash the stock recovery from a PC can you go onto recovery on the phone?
Click to expand...
Click to collapse
Probably...The thing is, I'm not sure to exactly which files to download and where to put them (in Odin). If you could tell me that, I'm sure my problem would probably be solved...My Gio's a GT-S5660M, is on Virgin Mobile Canada...and it's stock firmware (in which it came with) was 2.3.4. So please help me ASAP!!!
---------- Post added at 05:56 PM ---------- Previous post was at 05:52 PM ----------
lemmymet said:
Boot in recovery and connect your phone to your pc
On your phone click mounts&storage -> mount /data.
Download ADB from here: motyczko.pl/qtadb/windows_binaries.zip
Place it in a directory and open a command shell and cd to that directory(or go to the folder with adb.exe and hold shift while rightclicking and choose open command prompt here).
Now enter this command: 'adb shell'
You are now in the shell on your phone if the drivers are there(samsung kies needs to be installed)
Do 'cd /data/app' in the cmd, then 'ls'
Look for a apk file that looks like the overclocking app, if you found it do:
'rm <nameofoverclockapp>.apk'
Reboot your phone and have fun
Click to expand...
Click to collapse
That's not my problem anymore. I had installed CWM and then used it to boot Aroma Filemanager. With that, I had successfully uninstalled ch.amana.android.cputuner-1.apk (CPUTUNER). But it still won't boot. I tried to install stock rom with Odin and was unsure of which file went where. So now it won't even boot to recovery and only to download mode.

Now it can boot to recovery and even to the Samsung logo! But then it loops on and on. Maybe I should delete the boot.img from the rom and reflash? If not, immediate help needed..

Help again!
So I flashed my phone, and it finally boots. However, the mobile network state only stays activated for a short moment then it disconnects, making me unable to actually make phone calls and send text messages. Also, the wireless internet randomly switches off and doesn't turn back on unless I reboot it. And third but last, the screen sometimes blacks out even when the touch screen is still activated. Then the display either turns back on and even brighter (doesn't actually change the system settings brightness), or when I press the power button, it flickers and turns off (just as the whole system goes into standby mode when you press the power button). My phone was rooted before flashing and I rooted it once again. I just know this is all the troubles of flashing, rooting and my problem put together. So if anyone can help in anyway (I really don't want to send my phone in), please do.

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...

I have the same problem

Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???

I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.

Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.

I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.

Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.

No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.

karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.

Nexus stuck in boot loop - unrooted - Backing up photos from bootloader or recovery

Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.

@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards

____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?

mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..

____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.

Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.

____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.

If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...

____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/

A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?

Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..

@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..