$10 paypal to who can help me solve this
Here's the deal people,
My GNex was slowing down and acting all funny with stock 4.3 after about 6 months
I finally decided to try out a 4.4.2 ROM
I had TWRP on the phone so I said I'd just copy the Zip to the root folder along with the Gapps
Long story short, I accidentally wiped the storage.
Then I said no biggie, and figured that I'd just mount the USB to my laptop and transfer the Zip file of the ROM I wanted over to the storage.
BUT when ever I tap on mount USB nothing shows up in the devices.
Now I have nothing to transfer the files to.
I have windows 8 on the computer I'm currently using if that matters.
Forgive me people. I am not an avid flasher like I was when windows phone 6 was still around. So spare the insults . Just need my phone running so I can contact my loved ones
Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
throwback1718 said:
$10 paypal to who can help me solve this
Click to expand...
Click to collapse
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11
AndyYan said:
Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
agh I have read that the drivers don't work on windows 8 PC's . But I'll try
I flash my phone usually 2 or 3x per 12 months. so please pardon me if I forget some things...
In addition, the phone has nothing on it but TWRP
so no OS is on it at the moment. and no USB mounting.
I think USB mount is used for mounting USB flash drives attached through USB OTG.
The essentials. Contains ADB, fastboot and USB drivers from the Android SDK (should work on 8 and 8.1).
ADB_usb-driver.zip (8.79 MB)
To transfer files within TWRP, you need to use adb. Start by installing the driver. To verify for successful driver installation, type in:
Code:
adb devices
It should show you a "List of devices attached" and there's at least 1 item in the list.
Then copy the zip you want to flash into the same folder as adb. Let's say the file is named rom.zip. To "push" it to the phone, use the following command:
Code:
adb push rom.zip /sdcard/rom.zip
After it has finished "pushing" the file, just tap "Install" in TWRP and the zip file should be there!
You can now proceed flashing the ROM of your choice.
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.
Can you temporarily put the SIM in another operable phone to get your calls and texts?
Not sure about the fastboot error. You'd need to download a Google stock ROM image directly from them, and fastboot flash the system and boot partitions. This should be enough for a reboot to regenerate the user data partition. You cannot flash the custom ROM in fastboot unless a version has been made available in that format.
Sent from my Nexus 5 using Tapatalk
throwback1718 said:
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
Click to expand...
Click to collapse
Might as well use another non-Win8 computer, drivers are hard to mess with.
Sent from Google Nexus 4 @ CM11
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
Is that so?
Sent from Google Nexus 4 @ CM11
AndyYan said:
Is that so?
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk
cmstlist said:
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3
AndyYan said:
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3
Click to expand...
Click to collapse
I don't have all the answers to that. Wiping data in custom recovery should not be an issue because TWRP & CWM are both designed to keep /sdcard intact and erase the rest, which means it's just deleting files not formatting the whole partition. What I'm saying has to do with when you're in *fastboot* and you either factory reset, reflash userdata.img or wipe userdata.img, or unlock the bootloader.
On my GNex in this situation, circa 1.5 years ago, TWRP gave an error in which it thought the data partition was encrypted. CWM did not give an error but any files I attempted to write did not actually stick. One boot into a working ROM fixed it.
I have also observed that after a fastboot wipe, it starts booting into the ROM, possibly displays the Android "unpacking" screen, and then resets to the Google splash screen one more time, and then the second boot is the successful one. I have no idea if it has to do with permissions, formatting, or whatever else, I just know that it happens.
throwback1718 said:
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.
Click to expand...
Click to collapse
Your 4.4.2 ROM install most likely failed due to outdated TWRP. You must install twrp 2.6.3.2 via fastboot first, then you should be able to install and get going.
Let me know if you need links to anything
---------- Post added at 05:11 AM ---------- Previous post was at 05:10 AM ----------
Also, next time don't "wipe/format data" in twrp. Do factory reset. (Unless they changed the damn name again on us lol)
Related
Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is
demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.
El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????
Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.
Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.
Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806
tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.
Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users
any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum
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!
UPDATE: PROBLEM SOLVED
Hello,
I recently flashed a rom with a custom gapps that had themes, but one of the apps, G+, did not work since it was outdated. In an attempt to take the easy way out, I installed a "system app uninstaller"-app and used it to remove G+. It removed it, but I could not install G+. I decided to reboot the phone, but it took an abnormally long time amount to turn back on, stuck at the "Google" logo screen. I decided to reflash one of my previous backups.
My phone uses ClockworkMod Recovery v6.0.1.0 currently. After wiping data/factory reset and wiping the cache partition, I decided to restore one of my recoveries. It restored boot, system, but then failed to restore the /data with "Error while restoring /data!" popping up. I tried these steps again but with another backup, and the previous one before that, and none of them worked.
I did some research online, and learned that I could flashboot a stock recovery to my phone, so I attempted to do that; I noticed that when using the "adb devices" in the command prompt, no devices were listed.
If it makes a difference, I did not install the proper drivers for use of ADB since this computer is new. As of now, I can not boot my phone, and I can not access the files on my phone when connected through USB when attempting to use the "Mounts and Storage Menu" in CWM. Because of this, I can't use Fastboot to flash a stock recovery image from my current knowledge and self-research.
I now come to you guys for assistance; what other steps can I take that I haven't tried? Or perhaps have I done something incorrectly in my method?
If there is any other info needed, please let me know so I can reply with that information.
TL;DR - Can not use CWM to restore my backups (stuck at /data), cannot use fastboot because my GNex isn't listed on the adb devices, what should I do now?
Thank you for your time. (And sorry if this is not in the correct section)
Okay, so, first we need to fix your driver issue. I'm assuming you're on windows.
1. Boot to recovery, connect your device to the computer.
2. Download the driver here http://forum.xda-developers.com/showthread.php?t=1766220
3. Start menu>Right click computer> Properties> Device manager>Find your phone, right click, properties> Uninstall driver if any, then install the driver you downloaded.
4. Your phone should now appear as an ADB interface. Try ADB devices.
5. Now that ADB should be working, backup your SDcard. Type "adb pull /data/media/ SD". This will backup your SDcard to a folder named "SD" in the directory your ADB file is.
6. Now it's time to reflash the phone. Use ODIN. I'm sure someone can link you to ODIN images. If not, I can let you directly download them from me in the morning. I used the 4.0.2 images
7. Boot to odin (Phone powered off, hold Volume Down and power. Phone will say "Downloading...."
8. Flash the ODIN images with the ODIN program. Flash a PDA and PHONE file.
9. Once the phone boots up, turn it off, boot to the bootloader (Phone off, then Vol up and down, with power).
10. in your CMD, use "Fastboot devices". If the phone isn't detected, then update the driver of the device detected to the driver you downloaded.
11. If fastboot works, type "Fastboot oem lock", then reboot the phone.
12. Allow the 4.0.4 OTA to install.
13. Go back into the bootloader, and do "Fastboot oem unlock", then flash your recovery to CWM. (Download the .img from the website, and use "Fastboot flash recovery <filename>")
14. Boot the phone. Let it fully boot, then shut down and load bootloader again.
15. Boot to recovery, and restore your SDcard by typing "adb push SD /data/media/"
Once that wall of text is done, your phone should be fully functional, and ready to flash. That is how I solved all of my issues when I experienced the same thing.
I know I was short with a how-to on ODIN, but I'm super tired. ODIN is easy, and I'm sure you can find guides.
With your help I have managed to fix the drivers and my phone is now listed in adb devices. I downloaded Odin3 v.1.85 and I have downloaded the odin 4.0.4 images from the sticky'd threads. What I downloaded was a .tgz and contains a .tar. I do not know how to use these files with Odin however; when I try using ODIN with the .tar file the ODIN executible crashes.
Also, "adb pull /data/media/ SD" yields "remote object '/data/media/sd; does not exist". Is it correct to assume this is because the Galaxy Nexus does not have a removable SD card? Or is this method supposed to back up the internal storage?
I'm really appreciative of your help, thank you.
"ADB_Pull_/data/media/_SD" You have a space where the underscores are, right? And this is a method to backup the internal storage. It is located in /data/media/. Whenever you "Factory reset", the phone's /data/ partition is wiped, but the media folder is exempt. Always.
And as for ODIN crashing.. that's weird. I haven't had an issue. I'll upload my 4.0.2 images and executable to mediafire and PM it to you.
You'll want to make sure you backup your SD data, because ODIN will erase it.
---------- Post added at 09:36 AM ---------- Previous post was at 09:25 AM ----------
Oh wait. I just remembered there are multiple variants of the phone. What Gnex do you have? Maguro, Toro, or Toroplus? I'm uploaded images for Toro.
Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.
efrant said:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
Click to expand...
Click to collapse
People have bricked with ODIN? I haven't heard of that. Also, I experienced the same issue when I tried going over to JellyBean for the first time. I ****ed my Jellybean up, and my data partition was not functional. There were other users who had the issues too. We were only able to fix it through ODIN.
Edit: Adding that we experienced our issues after flashing the non-AOSP Jellybean.
Ryands991 said:
People have bricked with ODIN? I haven't heard of that.
Click to expand...
Click to collapse
Yup, they have. If you'd like, I can search and post the links.
But if your bootloader is messed up and you can no longer use fastboot, you have no choice but to use Odin.
Nah don't worry about searching for it. I'll take a peak later. I'm interested. Thank you!
---------- Post added at 10:32 AM ---------- Previous post was at 09:57 AM ----------
If you still want to try ODIN, here is a mirror of the Toro 4.0.2 files
http://www.mediafire.com/?31kevti8p2pnb62
Again, this is for Verizon/Toro/SCH i515
Don't use with any other version. If you don't have Verizon, this isn't the file you need.
efrant said:
Looking at this thread is making my head spin.
What are you trying to do exactly? Flash a stock ROM without losing your files stored in /sdcard?
If so, then:
1) If you don't care about losing your files in /sdcard, just follow the steps in this thread.
2) If you DO want to keep the files in /sdcard, then follow the same steps, but skip flashing the userdata partition and the recovery partition. Instead of flashing the stock recovery, flash CWM 5.5.0.x. Once you have flashed all the partitions (except userdata), just reboot into CWM, and wipe data and cache. Done.
Other suggestions:
1) you should not use Odin unless you really need it. You can brick your device with Odin. Fastboot will do everything you need in most cases, and you canNOT brick your device.
2) Use CWM 5.5.0.x instead of the newer ones. The 5.5.0.x recoveries are extremely stable, and won't mess anything up.
3) You should read up a bit on fastboot and ADB. They are not related, as you seem to be implying in your OP (and they also need separate drivers). See here for a little introduction.
Click to expand...
Click to collapse
I didn't manage to save my userdata but I did manage to return my phone to stock w/root using the method described in the thread you directed me too. Thank you efrant for your help
And thank Ryands991; I'll keep the ODIN method in mind if I ever encounter a problem using fastboot. Oh, and with regards to the spaces; I did have them, but it was stuck at 0% and never pushed my userdata. I am fine with losing my userdata however, so I went ahead and did a full wipe.
Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?
chriswcs said:
Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?
Click to expand...
Click to collapse
I tried to take a screen shot, but it won't let me post it as I am noob-status.
Device Manager:
Android USB Devices
MyHTC
.
.
.
Portable Devices
J:/
<!> MTP USB Device
I don't understand why I can't mount or access the phone. Do I not have the right drivers installed?
Is there any way to get around this and put the files on my phone so I can install any old ROM so I can boot it up again??
You need to update the drivers on your PC, there's a few threads on how to do it. You should still be able to use adb push to add files, though.
Drivers are fine ! Go in recovery and mount the sdcard as a usb mass storage device ! In the title you speak of a HTC one......so is it a ONE or a ONE X ?
Thanks for replying!
It is an HTC One X. Should I just install the Android SDK bundle? Or are there other drivers?
Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.
Mr Hofs said:
Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.
Click to expand...
Click to collapse
Hi, so I installed the newest HTC driver (4.2) and all the SDK bundles. When I plug the phone it, it still won't recognize the HTC MTP Device. When I mount from the bootloader, it doesn't let me mount the sdcard (only the system data and cache), and Windows still shows a drive that needs to be formatted.
Do you think it's still a Windows driver I'm missing? If I go Terminal Command on phone it says
E: Unable to mount '/sdcard'
E: Unable to mount storage.
What's the option called you tap inside recovery. And what recovery are you using ?
If it's CWM you go to mounts and storage and tap the last option in that list.....then wait till it pops up on the pc
I'm using TWRP v 2.4.2.0 and I couldn't check the box for mount sdcard.
ADB push worked!
But the ROM failed. Is there anything else I'm missing?
It still says that E: can't mount.
Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ
Mr Hofs said:
Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ
Click to expand...
Click to collapse
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?
chriswcs said:
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?
Click to expand...
Click to collapse
Or how do I try your recover? Should I push it with adb? If so, to where?
I found two other boot.img files on the webs (boot.img and cm10.img), but I don't know how to get the phone to actually boot off them
The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands
Mr Hofs said:
The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands
Click to expand...
Click to collapse
Okay! That's good
I think it flashed correctly, now I am just waiting for the phone to boot up. It's been going for about 25 minutes though. Should it be that long?
Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img
Mr Hofs said:
Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img
Click to expand...
Click to collapse
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.
Lol dude you have the evita go to the HTC one XL forum. You are in the completely wrong forum......sorry !!!
chriswcs said:
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.
Click to expand...
Click to collapse
Stuck yet again.
I relocked the phone to flash new firmware, but I have CID 1111111, so I can't find anything to unlock the bootloader again.
Double sauced. Ahhhhhh
Unlock the bootloader by flashing the unlock_Code.bin file wich you got the first time when it's unlocked.
Fastboot flash token unlock_code.bin
But you really should continue this in the right forum. Flashing stuff from here may brick the phone !
Hi folks,
For some stupid reason, I tried to encrypt my phone from within TouchWiz Security Settings. I entered a password for the encryption, and as soon as I clicked start, the process stopped and an error saying "com.android.systemui has stopped" has appeared. If I click OK it pops up again. Restarting the phone gives the same error, and I can't actually use the phone at all, as the error message keeps popping up even if I try to enter the correct password.
I tried reflashing the rom, wiping data, cache and so on, and the same error message pops up as soon as TouchWiz loads up. I don't know how to transfer another rom from my computer to the phone from within CWM (I don't see my phone's storage from within windows).
I thought I'd do a complete unroot, but the stock firmware available for this device is older than 4.4 (which is what I have because I'm using Enewman's SRx 4.0). Everywhere I read it says "DO NOT DOWNGRADE".
I'm not sure what to do, and I have very limited expertise in this matter.
Thank you for all your help folks!
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
audit13 said:
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
Click to expand...
Click to collapse
Yep, I was rooted and using CWM. The phone still boots to TouchWiz, but then the error comes up and I can't use the phone at all. I tried formatting the system before installing a new rom too...
So I used adb to sideload CyanogenMod, and flashed it. That seems to have helped the problem
So the in call volume in AOSP ROMs (tries carbon, quantum, cm11) is way too high. Tried reflashing any other kitkat based touchwiz ROM but immediately upon first boot I get prompted to insert the encryption password. When I do, it asks it again. Is there any way to somehow get a touchwiz ROM to work on my phone now? I alwaya do clean installs. Thanks guys
It is my understanding that encryption requires stock recovery.
What bootloader is on your phone?
Looks like I'm on the UCUFNE4. every touchwiz ROM I install asks for decryption, and all the other ROMs are installing OK..
Have you tried using Odin to flash a stock ATT KK ROM?
Edit: nevermind, looks like there is no 4.4.2 ATT ROM on sammobile.com. I assume you already tried wiping cache, dalvik, and data.
Yes I have tried to wipe everything. Even internal storage. So then I had to sideload a ROM using adb. I really appreciate your input!
It sounds to me like the data portion is still encrypted. Were you able to use fastboot commands to erase cache, data, and system before flashing a new ROM?
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
tequilaboom said:
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
Click to expand...
Click to collapse
It might be but I have never compared the two methods.
Are you able to issue fastboot commands to your phone?
I have never done fastboot but I could try using it. What should I do with fastboot?
tequilaboom said:
I have never done fastboot but I could try using it. What should I do with fastboot?
Click to expand...
Click to collapse
Boot the phone into download mode, connect the phone to the computer via USD, let it install the Samsung drivers. You will also need the necessary ADB/fastboot files from here: http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Boot to an command prompt in Win7 or Win8. Navigate to the directory where you installed the ADB/fastboot files and type this: fastboot devices and press enter. Hopefully, your device will appear.
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
tequilaboom said:
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
Click to expand...
Click to collapse
Here's a good guide:
http://forum.xda-developers.com/showthread.php?t=2225405
alright I followed the guide, but still no effect
Did the fastboot commands work?
Did you try erasing the userdata partition? Did you try formatting the userdata partition?
I apologize, I should have said that I had no success even after trying to follow the guide. I attempted to use fastboot but when trying to detect my device, nothing showed up in that command window. ADB works no problem (detects device). Again after several tries of formatting the data partition (and everything else), every touchwiz rom asks for the encryption password. However, now when I enter it, the green android with gear appears, and then the device restarts. touchwiz now asks for the decryption password once again....
So typing fastboot devices didn't list anything? Were you in download mode?