Develop Bugs

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] Unbricking One X with no adb?

Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now

Slaxington said:
Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now
Click to expand...
Click to collapse
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc

eyosen said:
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc
Click to expand...
Click to collapse
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight

Slaxington said:
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight
Click to expand...
Click to collapse
Since you will be coming back from jb, wiping would prevent any future problems. Even if you decide to stay with JB, do a wipe as below
In cwm,
Wipe cache
Under advanced, wipe Dalvik cache
Under mounts and storage, format system
Cwm will remain intact. Also, I think selecting factory reset from bootloader menu will take you to cwm anyways. It's been awhile.
Yes, it is the boot.img file inside the zip. But you must use the full rom and not the ota. Ota only includes updates to some of the already existing files. It's just an upgrade.
Sent from my HTC One X using xda premium

Problem installing ROM, (boot.img) (VZW GNex JDQ39 (toro))

So I wanted to flash CarbonRom on my phone, but wanted to do a complete wipe of everything (pictures, music, etc) and then push the rom via adb but I ran into a problem.
So I booted into cwm (v6.0.3.1) did wipe data/factory reset, wipe cache partition, in mounts and storage I did format sdcard, format system, format cache, format data and /data/media (/sdcard), then wipe dalvik cache, and fix permissions. After that I opened up the GNex Toolkit v11.1.0 and entered push files to device, then it said “the toolkit will check for insecure boot.img” It asked am I using a custom rom or insecure boot.img I said no, it booted into fastboot and loaded boot.img then loaded back into cwm and then asked me to select file, I entered carbon* set the location, then about 20 seconds later said “An Error Occurred. You are not using an Insecure Boot Image”
I also tried this, unzipped CarbonRom and copy/pasted boot.img into sdk/platform-tools, then held down shift opened command prompt typed in fastboot devices, my device showed up, then typed in fastboot flash boot boot.img then booted into cwm, and tried to push files again through the GNex toolkit and the same thing happened “An Error Occurred. You are not using an Insecure Boot Image” I also tried this with another Rom (Vanilla RootBox) but got the same error.
I finally tried this, went to My Computer, Local Disk (C: Drive) Galaxy Nexus Toolkit, root, copy/pasted boot-insecure-jdq39-toro.img to sdk/platform-tools, typed in fastboot flash boot boot-insecure-jdq39-toro.img, then went into gnex toolkit and tried the push file and got the same error. I realize I could do adb push in sdk/platform-tools but I’m new to command lines and felt more comfortable using the toolkit.
I think there must be an easier way to do this. Before thinking of adb push to load the rom I was hoping that maybe there was someway that I could wipe everything and then mount my phone as a storage device and just drag and drop the rom and gapps onto my device and then install the zip from sdcard, but then I got this whole boot.img thing (I don’t know what it is) so my plan of dragging and dropping probably wouldn’t have worked. or maybe it would have? is it possible to do that CWM or TWRP? If so what would happen to the boot.img step?
I’m all out of ideas as to what to do next. Any help/advice is greatly appreciated! Thank you

why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT

Zepius said:
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Click to expand...
Click to collapse
Thank you so much! I stopped using the toolkit and just pushed it via adb with command prompt in sdk/platform-tools and it worked!
However next time if I want to flash a rom and do a full wipe of my phone will I have to flash the boot.img via fastboot (taken from the rom) & then push the rom via adb? (sdk/platform-tools) or just push via adb and do nothing to the boot.img ? I'm assuming do nothing wtth boot.img and that it was just the toolkit that was giving me that strange error, is this correct?
Thanks, again

[Solved] Nexus 7 flash stock recovery (waiting for device/ no os installed)

I have TWRP on my device, but I want to flash the stock recovery like when it came out of the box. I accidentally wiped the data so it says there is no os on the device. When I try to fastboot or flash all the command always says waiting for device. How do I fix this and restore my Nexus 7 to factory setting without TWRP on my device? Thank you!

andrew9606 said:
I have TWRP on my device, but I want to flash the stock recovery like when it came out of the box. I accidentally wiped the data so it says there is no os on the device. When I try to fastboot or flash all the command always says waiting for device. How do I fix this and restore my Nexus 7 to factory setting without TWRP on my device? Thank you!
Click to expand...
Click to collapse
You must have done more than just wipe your data. Data would be user apps, storage and configuration. Try updating the sdk. If that doesn't work uninstall your driver (including driver software) then reinstall the drivers. Good usb cable, usb port?

wantabe said:
You must have done more than just wipe your data. Data would be user apps, storage and configuration. Try updating the sdk. If that doesn't work uninstall your driver (including driver software) then reinstall the drivers. Good usb cable, usb port?
Click to expand...
Click to collapse
I have the stock recovery flashed now, but I don't think I have an os. How do I flash the factory image onto the device? Thank you btw!

andrew9606 said:
I have the stock recovery flashed now, but I don't think I have an os. How do I flash the factory image onto the device? Thank you btw!
Click to expand...
Click to collapse
You have multiple choices. I would personally download the factory image for the version that you are running, or were running.
Extract the system image (system.img) from inside the factory image. You will have to unzip the folder three times I think to get to the boot, system and stock recovery images. I use 7-zip by the way. Put the system.img inside the platform-tools folder of the sdk. Put your device in the bootloader screen, plugged into computer. Shift/right-click inside the platform-tools folder and choose "Open command window here," type fastboot flash system system.img in the cmd window, hit enter. I don't think it will auto reboot when done, I think you need to select Start in the bootloader screen using the volume button then press the power button.
If you want to flash the factory image, let's use 4.4.4 wifi version as an example. You will need to have these inside your platform-tools folder:
bootloader-flo-flo-04.02.img
flash-all.bat
image-razor-ktu84p.zip
If you double left-click on the flash_all.bat (windows pc) it will open the cmd window and then install the bootloader and the images inside the image zip folder. When it is done it will auto reboot I believe. Using the flash_all batch file will completely wipe your device including storage. If you don't want the flash_all to wipe your device and the storage a simple text edit will prevent it from doing so. Open the flash_all.bat with notepad (I use editpad lite) and remove the -w from the text. You can then run the batch file and it won't wipe everything, actually it will not wipe any data. Either way only takes a few minutes.

wantabe said:
You have multiple choices. I would personally download the factory image for the version that you are running, or were running.
Extract the system image (system.img) from inside the factory image. You will have to unzip the folder three times I think to get to the boot, system and stock recovery images. I use 7-zip by the way. Put the system.img inside the platform-tools folder of the sdk. Put your device in the bootloader screen, plugged into computer. Shift/right-click inside the platform-tools folder and choose "Open command window here," type fastboot flash system system.img in the cmd window, hit enter. I don't think it will auto reboot when done, I think you need to select Start in the bootloader screen using the volume button then press the power button.
If you want to flash the factory image, let's use 4.4.4 wifi version as an example. You will need to have these inside your platform-tools folder:
bootloader-flo-flo-04.02.img
flash-all.bat
image-razor-ktu84p.zip
If you double left-click on the flash_all.bat (windows pc) it will open the cmd window and then install the bootloader and the images inside the image zip folder. When it is done it will auto reboot I believe. Using the flash_all batch file will completely wipe your device including storage. If you don't want the flash_all to wipe your device and the storage a simple text edit will prevent it from doing so. Open the flash_all.bat with notepad (I use editpad lite) and remove the -w from the text. You can then run the batch file and it won't wipe everything, actually it will not wipe any data. Either way only takes a few minutes.
Click to expand...
Click to collapse
Alright, I got it back to 4.4.4. Thank you so much!

andrew9606 said:
Alright, I got it back to 4.4.4. Thank you so much!
Click to expand...
Click to collapse
Your welcome. Glad you got it straightened out!

Stuck on loading G screen

I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace

Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.

Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat

Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):

Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"

buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata

Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?

Sorry for the problems.
My bootloader is unlocked, so that might be the reason.

buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.

Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble