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
Hey guys,
I have a Gnex with android 4.2 stock bigxie. Yesterday I installed Purity 1.1 and find out that my storage had now the 0/ problem. So installed the latest cwm and tried everything again. Still had the 0/ problem. I also got messages like the phone's storage is full. And restoring NOVA launcher and TB backups was a pain in the a$$. So now I'm considering al complete wipe. Yes complete. I found this on a android forum. Is this the correct way or will this be harmful for my precious Nexus? I simply can't stand how my storage looks right now haha.
-> Instructions for a bad day: Completely wipe SD, reboot recovery, factory reset, format system, reboot system.
Is this correct or do I need something else? I'm not looking for the bootloader re-unlock way. That's too dangerous for my precious.
Thanks in advance!
Format /data too. So make a backup first
Sent from my Galaxy Nexus using xda premium
So I can do this without any problems? I can go on flashing new roms and kernels?
If everything goes well yes, then your device will be completely blank, you will need to flash a ROM via fastboot
Sent from my Galaxy Nexus using xda premium
When I completely wiped everything, should I do this?
"ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM."
Sent from my Nexus 7
LarsAussems said:
When I completely wiped everything, should I do this?
"ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM."
Sent from my Nexus 7
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
http://forum.xda-developers.com/showthread.php?t=1626895
LarsAussems said:
Hey guys,
I have a Gnex with android 4.2 stock bigxie. Yesterday I installed Purity 1.1 and find out that my storage had now the 0/ problem. So installed the latest cwm and tried everything again. Still had the 0/ problem. I also got messages like the phone's storage is full. And restoring NOVA launcher and TB backups was a pain in the a$$. So now I'm considering al complete wipe. Yes complete. I found this on a android forum. Is this the correct way or will this be harmful for my precious Nexus? I simply can't stand how my storage looks right now haha.
-> Instructions for a bad day: Completely wipe SD, reboot recovery, factory reset, format system, reboot system.
Is this correct or do I need something else? I'm not looking for the bootloader re-unlock way. That's too dangerous for my precious.
Thanks in advance!
Click to expand...
Click to collapse
use the guide linked in my sig to fix the sdcard "problem"
Thanks a lot everybody, will try k786's method.
I got myself in a deep hole - installed latest omni 4.4 and have no access to external sdcard. rebooted, wiped, proceeded to install cm11 only to find it out it's a corrupt file. Installation aborted
Now I don't have access to external
Only CWM is bootable
How do I access internal card to put another rom .zip??
I tried SDK android but running as administrator briefly blinks cmd screen and the whole thing disappears. I'm on win8.
Someone please help!
Bronyr said:
I got myself in a deep hole - installed latest omni 4.4 and have no access to external sdcard. rebooted, wiped, proceeded to install cm11 only to find it out it's a corrupt file. Installation aborted
Now I don't have access to external
Only CWM is bootable
How do I access internal card to put another rom .zip??
I tried SDK android but running as administrator briefly blinks cmd screen and the whole thing disappears. I'm on win8.
Someone please help!
Click to expand...
Click to collapse
Maybe you should reinstall' a Samsung stock ROM by Odin, with your device in download sitched in Download Mode. After that you root your device and reinstall' your custon binary and ROM
Zebra_Cat said:
Maybe you should reinstall' a Samsung stock ROM by Odin, with your device in download sitched in Download Mode. After that you root your device and reinstall' your custon binary and ROM
Click to expand...
Click to collapse
for some reason I can't get into download mode. No matter which buttons (vol up or down, power, home button) it always boots to CWM.
I wonder if I can push twrp as a .zip file through ADB - tried this on win8 - no go - but will use win7 tonight. At least it will give me access to external card I'm home free.
Bronyr said:
for some reason I can't get into download mode. No matter which buttons (vol up or down, power, home button) it always boots to CWM.
I wonder if I can push twrp as a .zip file through ADB - tried this on win8 - no go - but will use win7 tonight. At least it will give me access to external card I'm home free.
Click to expand...
Click to collapse
Try to make a wipe factory reset, wipe data cache and wide dalvik cache. And reinstall the bootloader. Maybe i'll works.
Pushed PhilZ.zip recovery thru 15 sec ADB installer, installed the zip, reboot - it's all good. PhilZ rocks. CWM sucks.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Bronyr said:
Pushed PhilZ.zip recovery thru 15 sec ADB installer, installed the zip, reboot - it's all good. PhilZ rocks. CWM sucks.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So, try with PhilZ
$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)
I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.
starrider1300 said:
I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.
meekrawb said:
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.
Click to expand...
Click to collapse
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.
starrider1300 said:
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.
Click to expand...
Click to collapse
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.
meekrawb said:
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.
Click to expand...
Click to collapse
Thanks for the help. I got into recovery and did a factory reset. Tablet booted and I went through the tablet setup. Same results, no playstore, camera, or gallery. Can't download from the internet, shows no SD card.
I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.
I would highly recommend just staying with the "full" releases of ANY OS on any smart phone, as any x.x.1/x.x.2 etc can have more bugs than what is trying to be fixed in the original (not all cases, but some)
Using NRT I would suggest dropping back to 5.0 and COMPLETELY setting it back to stock (re lock boot loader, stock recovery, no root), then doing it OTA (if thats how you prefer to update) THEN re-root, re-unlock etc
Or just stay on 5.0 until something like 5.1 comes about
fury683 said:
I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.
Click to expand...
Click to collapse
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?
starrider1300 said:
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?
Click to expand...
Click to collapse
Seems like the actual flash storage could have issues... is it still under warranty? May need to send it in..
i have exactly the same problem and still no solution (since september)
I tried to wipe everything, twrp, cwm, factory , CM, omnirom ... something is broken in the storage folder and nothing can repair it. wiping maybe erase the data but doesnt seems to rebuild the tree
starrider1300 said:
I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
neo13oy said:
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
Click to expand...
Click to collapse
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?
starrider1300 said:
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?
Click to expand...
Click to collapse
No , I just suggest it to check if your internal SD card is damaged.
as you say , you can flash your partition with Nexus factory images but your data will be lost !!!