I've tryed reading other forums but I'm not familiar with some terminology. I seem to have wiped all data on my phone including internal storage and just want to get my phone back into working order. There are no roms I can flash that are on the phone and can't seem to figure out how to mount the SD card to put a rom on the phone. No idea what to do from here. Any and all help would be greatly appreciated!!!
You'll have to fastboot flash a stock Google ROM now.
Sent from my Galaxy Nexus using Tapatalk 2
How does one fastboot flash?
geoffcorey said:
You'll have to fastboot flash a stock Google ROM now.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
uh no. thats an option, but not the only option
OP,
you need to have ADB setup so you can push the rom in CWM.
adb push nameandlocationofzipofromfrompc /data/media/
Okay. How exactly do I go about doing that?
http://forum.xda-developers.com/showthread.php?t=1814266
Sent from my Galaxy Nexus using Tapatalk 2
Okay I've attempted setting up ADB but when I type in adb devices under the directory C:\Andriod\andriod-sdk-windows\platform-tools> it does not find my phone. I've tryed watching and looking at a few tutorials but everything leads me to a dead, confusing end. Please help
is your phone in cwm and do you have the adb driver installed?
temperature omisten
I have Team Win Recovery but yeah when I search for devices its in Recovery. I'm double checking on the drivers
Zepius said:
uh no. thats an option, but not the only option
Click to expand...
Click to collapse
From what the op said, he's fully wiped /data including /data/media. And he'll need to reboot a ROM to rebuild the sdcard stuff (at least that's how it's seemed from my experience) and I'm assuming he's wiped /system. So he's pretty hosed for the adb method.
If he just flashes a system.IMG, he should be able to fix his issue.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
From what the op said, he's fully wiped /data including /data/media. And he'll need to reboot a ROM to rebuild the sdcard stuff (at least that's how it's seemed from my experience) and I'm assuming he's wiped /system. So he's pretty hosed for the adb method.
If he just flashes a system.IMG, he should be able to fix his issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
custom recoveries have ADB built into them, so no he's not hosed for adb.
How exactly do I flash a system.IMG?
Zepius said:
custom recoveries have ADB built into them, so no he's not hosed for adb.
Click to expand...
Click to collapse
But the sdcard structure is erased, and at least from my experience, you need to boot into a ROM to properly fix sdcard. Unless twrp allows you to flash zips not located in /data/media then pushing a zip to /data is useless.
Sent from my Galaxy Nexus using Tapatalk 2
Help please?
geoffcorey said:
But the sdcard structure is erased, and at least from my experience, you need to boot into a ROM to properly fix sdcard. Unless twrp allows you to flash zips not located in /data/media then pushing a zip to /data is useless.
Click to expand...
Click to collapse
That is true IFF the userdata image is completely erased/formated, which I don't think can happen by using a custom recovery.
Regardless, it seems like he lost all his data, so he might as well flash it back to stock entirely.
xAmpharosx said:
Help please?
Click to expand...
Click to collapse
Look here.
Related
is it possible to flash a rom without the actual sd card? because my sd card slot has basically been broken off and ive semi bricked my htc vision. so if somebody can please tell me how or at least some how back to stock it would be very much appreciated. =)
it would be very complicated, becuase you would have to repartition your 4gb ram in 3 mounts.
it would best if you do it through adb commands.
Well im willing to do anything to get it working again and im pretty good with adb so would there be anyway i could get the commands
Sent from my MB300 using XDA App
http://forum.xda-developers.com/showpost.php?p=13336228&postcount=6
You can put a rom in /data and flash it from there using the recovery I posted.
Hey thank u so much! =)
Sent from my MB300 using XDA App
Try putting scotch tape over your sdcard so it stays where its supposed to
Sent From My T-Mobile G2 using XDA App
amazinglarry311 said:
http://forum.xda-developers.com/showpost.php?p=13336228&postcount=6
You can put a rom in /data and flash it from there using the recovery I posted.
Click to expand...
Click to collapse
i was able to get everything working but after pushing the rom via adb to the data partition the actaul rom never showed up so i couldnt flash it ...any ideas
cjhcharlie said:
i was able to get everything working but after pushing the rom via adb to the data partition the actaul rom never showed up so i couldnt flash it ...any ideas
Click to expand...
Click to collapse
Edit: the rom needed to be pushed to /sdcard not /data
thanks again tho!
Hey guys,
I'm looking for some info from a knowledgeable dev on how to create a custom ODIN backup that can be restored using the ODIN executable for Windows? My goal is to create a complete hard image of my entire device (including my apps/personal data) that I can restore at anytime (as if it was never touched since the backup) using ODIN.
If anyone can fill me in on the details I would highly appreciate this.
Thanks in advance.
EDIT: I see some other guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Update #1: Looking for answer to this - Link to post
Update #2: May have found it - Link to post
Info that may help #1
Info that may help #2
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
The Race To Die said:
would also like to know how to backup with odin since my nandroids always fail at restoring data and then im forced to fresh install a rom
Click to expand...
Click to collapse
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
open1your1eyes0 said:
EDIT: I see some outdated guides here, here, and here. But I noticed some of the blocks they reference are nonexistant on the Galaxy Nexus.
Click to expand...
Click to collapse
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
open1your1eyes0 said:
Yes! Thank you! I'm glad I'm not the only one who has this issue. Are you using Touch CWM 5.8.0.2? Or the regular 5.5.0.4?
Click to expand...
Click to collapse
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
imnuts said:
How are these guides outdated? They work just fine for the devices they were written for. The Charge uses a completely different device layout compared to the Nexus. They are meant for completely different phones, hence the reason stuff isn't the same. Someone needs to find the proper names for the items that are dumped, and then an Odin package can be put together, but every device will have it's own guide on how to make the packages.
Click to expand...
Click to collapse
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
The Race To Die said:
Haven't tried koush's touch yet. Doesn't look as good to me as the unstableapps touch recovery, but have no luck with unstable or regular cwm recovery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm assuming you're referring to the first Touch Recovery (Unofficial) that was released? But really? Even the regular CWM doesn't work for you? This is a serious issue if we can't restore backups. How are we the only ones who noticed?
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
The Race To Die said:
Yes that is the one I am talking about. Creating backups works fine, but restoring always fails while restoring data.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
open1your1eyes0 said:
I see, so each device has different blocks allocated. I wonder how people figure out what blocks go to what?
Click to expand...
Click to collapse
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
open1your1eyes0 said:
I can confirm the same on the official Touch CWM 5.8.0.2 however I think I can recall making and restoring backups back when there was only the regular 5.5.0.4. Do you mind flashing that and testing if you can make a backup and restore it again?
Click to expand...
Click to collapse
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'll take a look right now.
The Race To Die said:
sure, will report back in a little. could it have been that i ran out of space? i only had 5 or 6 gigs left, but just erased all my backups and now have about 18gb
Click to expand...
Click to collapse
That is possible actually, I only had about 2-3GB left when I had the failed restores. Now that I redid my phone maybe it won't be an issue.
I am very interested in this topic since the stock image for my phone is not available. I would like to have an option to restore the stock image in case of a warranty issue.
I was exploring using ADB backup. Would it make sense to do a factory reset before creating the backup image?
Stuck on 4.0.1
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
open1your1eyes0 said:
How do you differenciate which one refers to which partition (data, dbdata, system, etc...). I think this is the main issue here.
Click to expand...
Click to collapse
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Not really sure what you are referring to. Each of those is a partition. User data is the data partition, system is the system partition, boot is the boot partition, etc, etc.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
EDIT: Disregard I was looking in the wrong directory.
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
The Race To Die said:
flashed 5.5.0.4 through rom manager
rebooted into recovery
backup completed fine
https://dl-web.dropbox.com/get/Public/IMG_20120208_204435.jpg?w=d80708cb
now making a backup through rom manager just for the hell of it to see if one works over the other
Click to expand...
Click to collapse
Really hope it works.
efrant said:
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name
Those are what you set your "if" path to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ok so I figured out which block goes to what partition (here). Now using this, how can I make a flashable package for ODIN? Also do the filenames of the "of" have to be a specific extension or name or it can be named anything? How does ODIN know which "of" file to treat as which partition in that case?
amazingly it worked! must not have had enough space to restore all of the data or something. now to figure out this odin thing. first samsung ive owned so ive never used it, had an og before my nexus.
The Race To Die said:
amazingly it worked! must not have had enough space to restore all of the data or something.
Click to expand...
Click to collapse
Thank you for testing this! I will stick to 5.5.0.4 for now and make sure I have enough space from now on.
FYI, I found another backup method: Link and More Info. For that you need to have the latest adb.exe from the Android SDK. I am attaching it to this post.
Did this accidentally when updating Roms & now I have no access to any Roms, backups, or files in CWM. Phone will not boot beyond the initial Google screen b/c it is not recognizing any internal files, I believe? Can I transfer files from a PC into CWM during recovery w/o the device actually being booted up? Haven't tried b/c I won't have access to a PC until I am at work tomorrow. I hope there is a fix for this rookie mistake & I greatly appreciate ANY advice - as I have not been able to find a definitive solution for this problem as of yet...
Thanks in advance,
Confounded Verizon Gnex owner
1) yes you can move files over to /sdcard using adb when booted into cwm. Use "adb push file.zip /sdcard/"
2) you could always flash a stock ROM using fastboot (see the "flash" link in my sig).
3) this is a good reason to not use a touch recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the quick response! Questions/Comments:
#1: Not sure I understand how to do this? Will I be able to add the zip files for the rom, etc. & keep root intact as it was?
Can u please simplify it into n00b terms, haha? Sorry, very new to the scene...
#2: The link is not working from my Nexus 7? Edit: Got it - just couldn't access via the xda app - looks extremely comprehensive.
#3: I agree. Step away from touch recoveries!
Sent from my Nexus 7 using xda app-developers app
Stixxbixby said:
Thanks for the quick response! Questions/Comments:
#1: Not sure I understand how to do this? Will I be able to add the zip files for the rom, etc. & keep root intact as it was?
Can u please simplify it into n00b terms, haha? Sorry, very new to the scene...
#2: The link is not working from my Nexus 7? Edit: Got it - just couldn't access via the xda app - looks extremely comprehensive.
#3: I agree. Step away from touch recoveries!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
First off, can you boot to recovery? If so then...
#1 All you have to do is plug in your phone and assuming the drivers are installed, you download the ROM and gapps to the computer and drag them to your phone.
Then boot your phone to recovery and install the zips as normal. You will find the files on the SD card and not in the download folder.
If you lost root then follow a guide to reobtain it.
As for the touch recoveries, I personally like CWM touch better than dealing with the volume buttons. It was a mistake that could happen either way.
Good luck. Hope you get it fixed.
Sent from my Galaxy Nexus using xda app-developers app
Yes. Recovery is good to go. Gonna give it a shot tomorrow. Thanks for taking the time to help. Gratitude
Sent from my Nexus 7 using xda app-developers app
This is why I stick with the non-touch recovery.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Same mistake please help
Zeinzu said:
This is why I stick with the non-touch recovery.
Sent from my AOSP Android 4.1.1 Galaxy Nexus
Click to expand...
Click to collapse
It happened to me, somebody find any solution, I got recovery mode, but I cant do anything because the system cant mount sd card
diegonando22 said:
It happened to me, somebody find any solution, I got recovery mode, but I cant do anything because the system cant mount sd card
Click to expand...
Click to collapse
The trick is to follow these steps in the correct order:
1) flash Google image using fastboot
2)boot into stock android and transfer your files to phone.
3)boot into bootloader
4) flash cwm recovery using fastboot
5) boot into cwm recovery
6)wipe and flash the desired ROM
NB the thing is that cwm does not format your sdcard correctly if I am correct...so any sdcard format...will end up corrupting it.the only way is to flash back Google image and start as stated above.
Sent from my Galaxy Nexus using Tapatalk 2
Are you trying to press Mount sdcard in cwm?
There is no need to do so, just adb push ROM.zip /sdcard/
Beamed from my Maguro
Try:
CMW>mounts and storage
Mount data
adb push NAME OF ROM.zip /sdcard/
unmount data
I accidentally wiped my rom off my Maguro Galaxy Nexus.
Now its stuck on the bootscreen and I need help on how to push a ROM zip file to the phone because i dont have one on it.
use adb to push the zip..
Use wugfresh tool, it will automatically install stock on blank nexus.
Sent from my Galaxy Nexus using xda premium
neevian said:
I accidentally wiped my rom off my Maguro Galaxy Nexus.
Now its stuck on the bootscreen and I need help on how to push a ROM zip file to the phone because i dont have one on it.
Click to expand...
Click to collapse
Use adb to push it through the recovery (I'm assuming you have a custom recovery installed)
Sent from my Galaxy Nexus using xda premium
sliders7 said:
Use wugfresh tool, it will automatically install stock on blank nexus.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ughhhh another toolkit answer...
Just download the fastboot files, extract them. On the bootloader enter this command from the extracted folder with fastboot.exe inside the folder - fastboot flash system system.img
Reboot and your good to go
Sent from my Nexus 7 using Tapatalk HD
neevian said:
I accidentally wiped my rom off my Maguro Galaxy Nexus.
Now its stuck on the bootscreen and I need help on how to push a ROM zip file to the phone because i dont have one on it.
Click to expand...
Click to collapse
How does one "accidentally" wipe the ROM from their device? After purposely wiping mine to ensure clean partitions, accidentally seems like a long shot.
Sent from my Xoom using xda premium
Winesnob said:
How does one "accidentally" wipe the ROM from their device? After purposely wiping mine to ensure clean partitions, accidentally seems like a long shot.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I wiped mine on accident yesterday in TWRP it wiped my rom and i had to revert to stock and start over.
Winesnob said:
How does one "accidentally" wipe the ROM from their device? After purposely wiping mine to ensure clean partitions, accidentally seems like a long shot.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I agree with you there Lol... In guess its like how 'some' people mistake the gas for the brake and crash into a convenience store...
Sent from my Nexus 7 using Tapatalk HD
MartianCeo said:
I wiped mine on accident yesterday in TWRP it wiped my rom and i had to revert to stock and start over.
Click to expand...
Click to collapse
yeah some ppl dont know that wiping data in twrp will also wipe internal storage...
k786 said:
yeah some ppl dont know that wiping data in twrp will also wipe internal storage...
Click to expand...
Click to collapse
huh - no, it won't. twrp has one option to format /data (but not /data/media/), and another one to wipe /sdcard/.
k786 said:
yeah some ppl dont know that wiping data in twrp will also wipe internal storage...
Click to expand...
Click to collapse
Only if you hit "wipe internal data" Lol... Factory reset and wipe system are the only two you want to use
Sent from my Nexus 7 using Tapatalk HD
ADB Side load > ADB push.
If you take the time to learn ADB it will save you time and trouble in the future. Plus, toolkits only cause problems.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Galaxy Nexus displays a red exclamation mark whenever I try to load into stock recovery.
Either the stock img file is corrupt or something else?
Prior to this I couldn't access sdcard, in adb I tried various cmds to rectify this, all to no avail. I keptnrecievong error:closed.
Please help/guide me through this dilemma.
---
smash
s_m_a_s_h said:
Galaxy Nexus displays a red exclamation mark whenever I try to load into stock recovery.
Either the stock img file is corrupt or something else?
Prior to this I couldn't access sdcard, in adb I tried various cmds to rectify this, all to no avail. I keptnrecievong error:closed.
Please help/guide me through this dilemma.
---
smash
Click to expand...
Click to collapse
Red exclamation mark is normal. Welcome to stock recovery. Press up+power to get inside. See this video: http://www.youtube.com/watch?feature=player_detailpage&v=mN1dy_t2K_U#t=68s
Hi thanks for the reply.
I managwd to access the stock recovery though no option to reset phone, just load from usb or adb, or wipe/factory reset.
How do I get the phone back to out of box condition i.e reset phone, clearing all
---
smash'n
s_m_a_s_h said:
Hi thanks for the reply.
I managwd to access the stock recovery though no option to reset phone, just load from usb or adb, or wipe/factory reset.
How do I get the phone back to out of box condition i.e reset phone, clearing all
---
smash'n
Click to expand...
Click to collapse
Wipe data/Factory reset. That will format all the data. But not the sdcard.
Sent from my Galaxy Nexus using XDA Premium HD app
before doing this the adcard was not accessible, hence I read to reset then phone to stock would correct the issue of the sdcard, it doesn't.
The sdcard is still inaccessible.
What I need I think,
format all back to stock with all wipe and reset/restore.
How to accomplish this?
---
smash'n
s_m_a_s_h said:
before doing this the adcard was not accessible, hence I read to reset then phone to stock would correct the issue of the sdcard, it doesn't.
The sdcard is still inaccessible.
What I need I think,
format all back to stock with all wipe and reset/restore.
How to accomplish this?
---
smash'n
Click to expand...
Click to collapse
Do the stickied FAQs or guides not show up for you? Because there is likely 2 or 3 of those that would answer your question(s).
Download stock images, flash them.
mrgnex said:
Wipe data/Factory reset. That will format all the data. But not the sdcard.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Stock recovery will format /sdcard/ on a factory reset.
a manta wrote this.
beekay201 said:
Stock recovery will format /sdcard/ on a factory reset.
a manta wrote this.
Click to expand...
Click to collapse
Oh thats right. Forgot that. Sorry.
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks for all, but I guess I knew that, my situation is I couldn't access the internal storage of the phone and all factory rests and revert back to stock wouldn't give access to the 'internal storage' nor could I mount anything using CWM, TWRP or via adb.
Eventually I used WUGFRESH SW and vola. solved.
---
smash'n
Just so we're clear:
s_m_a_s_h said:
Prior to this I couldn't access sdcard, in adb I tried various cmds to rectify this, all to no avail. I keptnrecievong error:closed.
Click to expand...
Click to collapse
Stock recovery doesn't have ADB acess enabled. You need either to sideload stuff ( 'adb sideload' ) or boot a custom recovery.
That said, dont open 2 threads for the same issue. So many threads are essentially the same and its almost impossible to make sense of duplicates. Reported.
beekay201 said:
Just so we're clear:
Stock recovery doesn't have ADB acess enabled. You need either to sideload stuff ( 'adb sideload' ) or boot a custom recovery.
That said, dont open 2 threads for the same issue. So many threads are essentially the same and its almost impossible to make sense of duplicates. Reported.
Click to expand...
Click to collapse
apologies again, adb sideload! wow...
essentially the same, but not, as they were to seperate issues.
---
smash'n
SGS2 GT-I9100
are you troll'n.. or stalking..
that's rhetorical btw
---
smash'n
SGS2 GT-I9100