Develop Bugs

Why is this wiping everything on the phone?

So here's the deal. Flash my gnex with the file provided according to this link:
http://forum.xda-developers.com/showthread.php?t=1394051
Now the thread specifically say "NO WIPE". But every time I flash using ODIN its wipes everything on my phone. And yes I have followed instructions to the T. My phone is unlocked and all options that are supposed to be are unchecked/checked.

gmony01 said:
So here's the deal. Flash my gnex with the file provided according to this link:
http://forum.xda-developers.com/showthread.php?t=1394051
Now the thread specifically say "NO WIPE". But every time I flash using ODIN its wipes everything on my phone. And yes I have followed instructions to the T. My phone is unlocked and all options that are supposed to be are unchecked/checked.
Click to expand...
Click to collapse
If your bootloader is locked, ODIN will wipe. Just unlock your bootloader and be done with it. See link in my signature on how to flash a ROM using fastboot instead of ODIN.
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Just unlock your bootloader and be done with it.
Click to expand...
Click to collapse
Yeah. What's up with this wave of modders buying a Galaxy Nexus, wanting to do custom firmwares/ROMs, mods, etc and then out of the blue they are afraid of unlocking their bootloader?
It makes no bloody sense at all.

ODIN flashes always wipe, easier to use fastboot to flash the stock images

EddyOS said:
ODIN flashes always wipe, easier to use fastboot to flash the stock images
Click to expand...
Click to collapse
Only with repartition set.
You can flash kernels, radios etc without wiping just fine. Or at least that used to work fine on my SGS1.
That said, I agree about fastboot being a on overall better tool for most tasks. I see no reason to use Odin if you can do the same thing via fastboot.
Sent from my Galaxy Nexus using Tapatalk

Agreed. But like I said my boot loader/phone is unlocked. I don't mind fast boot was just wondering why this wipe the whole phone when it say it doesn't.

[GUIDE]Factory Images (JB-ICS) [maguro][toro][toroplus]

Hello everyone,
i decide to write this guide and to collect all the future Factory Images for Galaxy Nexus (maguro [GSM/GSPA+], toro[VZW CDMA/LTE], toroplus[Sprint CDMA/LTE])
Once installed them you retourn 100% stock.
This is usefull in case you don't want to wait official OTA or you have to use warranty for some problem or you like a really clean install.
Since Android 4.0 IceCreamSandwich you can't install OTA via update.zip method in stock recovery because is no more possible. If you try via stock recovery you get "error status 7" (this problem is corrected only if you use ClockWorkMod Recovery).
Then is necessary to use Factory Image provided by Google.
Factory Images:​
JDQ39 Android 4.2.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 2fe041ac195086ef09274204c7e265e2
JZO54K Android 4.1.2 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum cc710f1539765c6ab7fbb8f50b69f0d6
IMM76I Android 4.0.4 Factory Image "yakju" for Galaxy Nexus (maguro GSM/HSPA+)
MD5 Checksum 31447212fb4fb00aab4ef8bdc78e7ffb
JDQ39 Android 4.2.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])*
MD5 Checksum 2fae8a6f50016e83f232fbb2d099fd42
JZO54K Android 4.1.2 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 4e79a918a9a366166d0c23f99cc240db
IMM76I Android 4.0.4 Factory Image "takju" for Galaxy Nexus (maguro GSM/HSPA+ with Google Wallet installed [notice, if you live outside US it simply disappears])
MD5 Checksum 26ede55c44b503e4ab02969c22fa16e1
JRO03O Android 4.1.1 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum 1df6a2a7385c4745193fe82bf2a87f78
IMM76K Android 4.0.4 Factory Image "mysid" for Galaxy Nexus (toro VZW CDMA/LTE)
MD5 Checksum e76c6fe7d2bc799e5a6168f9dcb8c4ca
FH05 Android 4.1.1 Factory Image "mysidspr" for Galaxy Nexus (toroplus Sprint CDMA/LTE)
MD5 Checksum 7b3c4c37dd64a664427d3829e2491bee
NOTICE: If you have any GSM Galaxy Nexus (for example european version Yakjuxw, Yakjusc ecc... or other GSM version branded by Samsung) you can ALWAYS safely flash Yakju or Takju images provided by google, in order to get future OTA in time, directly from Google and not from Samsung)​
How to install:​
Requirements:
-Android SDK
-Java JDK
-Platform-Tools
-Unlocked bootloader ("fastboot oem unlock" pay attention, wipes everything, also your data)
-experience with adb and fastboot​
NOTICE: If you never used the sdk, the jdk, fastboot and adb, before installing the factory image YOU HAVE TO FOLLOW some guide here on XDA in order to get sdk and unlocked bootloader.
Now you can proceed to install the Factory Image
On Windows:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
4B) If you are coming from another stock rom (official older OTA unrooted), this doen't wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro or toro or toroplus-********.img
fastboot reboot-bootloader
fastboot update image-********.zip
if you want relock the bootloader (not necessary, only for warranty) do also these two step:
fastboot reboot-bootloader
fastboot oem lock
On Linux, Mac:​
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a terminal and moves in "platform-tools" folder
3) write those command:
chmod +x flash-all.sh
./flash-all.sh
"flash-all.sh" wipes your data (it contains fastboot -w update, if you want to remove/change it edit with notepad++)
"flash-base.sh" flashes only the bootloader and the radio.
NOTICE:
1) Instead of ******** you have to put the name of the files you download.
2) somebody is aking why "adb reboot bootloader" each passages. Is not essential, but some people think it is better because you use the updated bootloader, maybe is only a superstition.​
PLEASE LEAVE ME A THANKS ​
WARNING! DON'T DO THESE THING IF YOU DON'T KNOW WHAT YOU ARE DOING. I'M NOT RESPONSIBLE OF BRICKED GALAXY NEXUS OR SIMILAR​

While it is a nice guide there is one already and its a sticky
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Galaxy Nexus using Tapatalk 2

In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide

D3VI0US said:
In old guide on XDA you needed to unzip the main folder and unzip and unzip the image-takju-jro03c.zip file to to get the boot.img , userdata.img and so on and you flash everything manually
so my question is >> in the old guide when you use Fastboot flash userdata userdata.img << this will wipe everything on the sdcard so is this the case here ? because i can see that useing the command fastboot -w update image-takju-jro03c.zip can avoid erasing everything is that right?
and thanks of course for the great guide
Click to expand...
Click to collapse
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium

Not quite sure how your guide is more transparent or for beginners than efrant's is...
I followed his numerous times with no issues.
Its one thing to provide an alternative guide for those who wish to use it, it's another to knock someone elses work..

What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2

prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Use intuition. Why Google should have done an extra zip to extract when they created the command fast boot update? Why complicate things when they are simple? If you exclude reboot commands you need only 3 commands with same effect!
Sent from my Galaxy Nexus using xda premium

ale.landra91 said:
I never used this guide because is not "transparent", I mean, my passages are the one that Google suggest. That guide is good but there are lots of thing that are a plus and not only using Google factory image. This is the way to use them. The other guide is a plus for advanced users. When you type -w it erases your internal memory (data and apps, this is in theory, I always use stock ROM than I never wiped with fast boot, maybe copy your SD on PC to prevent damage) bye
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
prinzhernan said:
What's the difference with enfant's guide because I've been using his for the longest time. Is the command update image-xxxxxxx.zip recommended by Google? It's much shorter than flashing all the files individually but I dunno.
Click to expand...
Click to collapse
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.

efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
Which I believe is better for beginners...
But what do I know... OH WAIT... I used to be one.
Bottomline, use the one you want... or are more comfortable with.
One thing to remember however... if you end up screwing your device up... efrants procedure will pinpoint exactly where you went wrong or what step it caused issues at.

efrant said:
Not sure what you mean by "not only using Google factory image". Everything I mention in that guide is from Google, except the driver (which is originally from Samsung, but repackaged by 1wayjonny).
The difference between this and my guide is that I have included ALL the steps to flash stock, from installing the drivers and downloading any needed files (the SDK and JDK are not needed by the way) to flashing your device. Additionally, as is stated in the first post of my thread, I have expanded all the steps and eliminated all scripts, so that people can see what is actually happening for the purposes of learning. For example, executing one command which actually flashes four images behind the scenes is not as valuable to learning as executing each command individually.
Included in the factory image is a script that flashes everything at once. Do you learn anything from it? Not really. There is no difference between using the fastboot update command to flash a bunch of images in a zip file, and flashing each image with the fastboot flash command. The difference is for instructional purposes.
Click to expand...
Click to collapse
simply they are different guide. My intention was porting my nexus s guide to galaxy nexus and not writing a poem. Few passages to use the images in the correct and simplest way. Then users choose to use your or mine with same results I never said that you are wrong, is only an alternative of lot of ways

can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad

jamil-m77 said:
can anyone upload the 4.1.1 yakju factory image for the galaxy nexus on any site because google's links aren't working for me please help i need it so bad
Click to expand...
Click to collapse
sorry i dont have it. Does it work now?

OP updated! Sorry for the delay

OP updated with new 4.1.2!

OP updated

Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick. Does the build number matter if a want only stock recovery? Thanks

M4t3s said:
Hi, can someone get me factory image for 4.1.1 maguro? In fact, stock recovery will do the trick.
Click to expand...
Click to collapse
See here, courtesy of oldblue910.
M4t3s said:
Does the build number matter if a want only stock recovery? Thanks
Click to expand...
Click to collapse
Yes it does.

I remove link last week because google deleted it and i havent it stored on PC
Sent from my Galaxy Nexus using xda premium

Took me FOREVER to get this to work because I had to use "./fastboot" instead of just "fastboot", but it saved my ass! Thanks a lot.

op updated!

[Q] Issue with 3G/LTE Connection After ROM Flash

Long time lurker, first (maybe second) time poster.
I'd really like to mess around with my phone's potential, but every time I flash a custom ROM I lose all data connectivity. 2g/voice works fine, but 3G and LTE are out the window.
Here are a few things I've tried AFTER flashing to a customer ROM. I come from years of using HTC phones and software, so I'm definitely fumbling around in the dark here. Please, excuse me if I sound ridiculous.
- I'm on Sprint
- Flashed radio zips in recovery (various ones from reading other threads)
- Used Odin to flash radio files (various ones from reading other threads)
- Repeatedly attempted to update Profile and PRL with error messages saying I couldn't update them and to call customer service
I'm not really sure what else to put up here or to try. I'm hoping the great XDA can help out! Again, I only loose data connectivity after flashing a new ROM. Unlock and root do not effect radios, and I'm able to use the phone just fine on stock software.
Attached is a screenshot of my stock build.
Thanks,
Brandon

I am a little baffled that after 150 views, no one else on this board has shared a similar experience. While its remotely possible, there is just no way I am the only one to have had this issue.
Also... shamless self-bump,.

you are flashing a sprint rom correct?

Zepius said:
you are flashing a sprint rom correct?
Click to expand...
Click to collapse
I'd hope so. I've gotten them all from the Sprint section of the GN forum here on XDA.

i would try flashing the factory images for sprint with fastboot and not odin. this may help more in making sure you have the exact radio/etc you need.
https://developers.google.com/android/nexus/images#mysidspr

Zepius said:
i would try flashing the factory images for sprint with fastboot and not odin. this may help more in making sure you have the exact radio/etc you need.
Click to expand...
Click to collapse
So, here's my order of operations here...
1) flash factory image with fastboot
2) install custom ROM
3) ???
4) Profit?
I mean, if there are other steps, I'm sure I can figure them out. So, I'm assuming that there is typically no need to do anything to the radios after installing a ROM?

after flashing the stock images (all of them, dont leave any out just to be sure) youd need to flash the custom recovery and then you can install the custom rom.

Zepius said:
after flashing the stock images (all of them, dont leave any out just to be sure) youd need to flash the custom recovery and then you can install the custom rom.
Click to expand...
Click to collapse
Sorry, but when you say all of the stock images, what do you mean? What other stock images are there?
And wait, sorry, there's something I didn't mention. I've been using the GN ToolKit for a lot of this. How do I push the stock image you linked me to using fastboot? I'm familiar with using ADB and all that, but I have no idea what to do without a guide. I certainly am not a programmer, just an enthusiast.
Thanks

itsasmallboat said:
Sorry, but when you say all of the stock images, what do you mean? What other stock images are there?
And wait, sorry, there's something I didn't mention. I've been using the GN ToolKit for a lot of this. How do I push the stock image you linked me to using fastboot? I'm familiar with using ADB and all that, but I have no idea what to do without a guide. I certainly am not a programmer, just an enthusiast.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895 - follow the steps similar to the verizon version, except make sure you download the mysidspr image from the google website.
flash every image. bootloader, radios (note there are 2 with the CDMA versions), system, userdata (copy your SD card off before you do this as it will wipe the phone) boot. do not skip anything.

Zepius said:
- follow the steps similar to the verizon version, except make sure you download the mysidspr image from the google website.
flash every image. bootloader, radios (note there are 2 with the CDMA versions), system, userdata (copy your SD card off before you do this as it will wipe the phone) boot. do not skip anything.
Click to expand...
Click to collapse
Alright. Two hours later and after all that... same result. No matter what I do, booting to any custom ROM does not allow me to access 3G/LTE. Should I just give up? lol

Alright, I've been doing some research and apparently I need my phones unique MSL codes to enter in after I flash a new ROM. Any suggestions on how to find my MSL and how to type these codes in after flashing?

Update:
Found a way to get my MSL using a script in terminal w/ root. I can access the data settings menu, but STILL cannot get my MSL for this.
Please help! We've gotten this far!

Can't get 4.2 OTA on Yakju Gnex, help please, going mad!

Hi all,
I'm new here so please go easy on me. I've had my Gnex for about 4 months now, and totally love it. But right now I'm still waiting for 4.2 or 4.2.1 to turn up, and getting increasingly annoyed with it's no show.
I've tries checking for the OTA update, and I've tried deleting the Google Services Framework Data to kick start it, but so far, still no update.
Last night I tried sideloading the update using ADB on Mac OSX and a ROM I downloaded from Google. After slowly figuring out what I was doing I managed to get the update to transfer via ADB but then for some reason I kept getting "Installation Aborted" reported on the Screen of my Gnex.
I'm losing it now. I have 4.2.1 on my Nexus 7 and love it, and I really wish my Gnex was in sync, features wise. But the update just isn't showing up.
It's a Yakju international Gnex, I'm in the UK on O2 network. Previous OS updates have come through as they should (on 4.1.1 now, never got 4.1.2) but I just can't get 4.2 on there.
Any help would be hugely welcomed, thanks a lot.

Download the factory image from here: https://developers.google.com/android/nexus/images#takjujop40d
Just flash that manually and you will be on stock Android 4.2.1 for Galaxy Nexus Yakju.

That's what I said I did and it reported "Installation Aborted" any ideas why that happened? I tried numerous times.

davidpye said:
That's what I said I did and it reported "Installation Aborted" any ideas why that happened? I tried numerous times.
Click to expand...
Click to collapse
No, you tried the OTA update. The link I gave contains the full factory image (system,data,kernel,recovery etc).
You need fastboot to flash it.

Aerys said:
No, you tried the OTA update. The link I gave contains the full factory image (system,data,kernel,recovery etc).
You need fastboot to flash it.
Click to expand...
Click to collapse
No, I downloaded the 4.2.1 ROM you linked to and use ADB to Side load it. Is that the wrong way to do it?

davidpye said:
Is that the wrong way to do it?
Click to expand...
Click to collapse
Yes.
Aerys said:
... You need fastboot to flash it.
Click to expand...
Click to collapse
Follow these instructions to flash the factory image: http://forum.xda-developers.com/showthread.php?t=1626895

Hi,
I followed those instructions to a T, I get to:
"9) Flash the system partition: fastboot flash system system.img"
And the commands no longer do anything, they just report "File Not Found" or words to that effect.
I do appear to have unlocked the Bootloader, but still the update will not install when I sideload with ADB.
What am I doing wrong?
gokpog said:
Yes.
Follow these instructions to flash the factory image: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse

I've just tried sideloading these images from this thread: http://forum.xda-developers.com/showthread.php?t=1419170
yakju JZO54K from JRO03C
yakju JOP40C from JZO54K
and
yakju JOP40D from JOP40C
and all report "Installation Aborted".

what version are you even on?

I said in my first post, 4.1.1.
I think I'm getting somewhere now, I know no one is likely to care that much, but the single thing that makes this so hard for a n00b like me is that there are so many different sites with conflicting or differing information on how to do this, some say use ADB, some say use CWM (which is what I'm doing now). NONE explain even briefly what these things are.
Anyway, I'll let you know how I get on now, using CWM to install the OTA updates in order.

the smartest thing u can do is get galaxy nexus toolkit 10.1.0 for your Mac. It will allow you to flash whichever factory image u want and also unlock your bootloader and root your phone if you want. You can find a thread for the tool kit on xda itself. My friend and I did this to update to 4.2 the day it released. If it helps please press the thanks button.
Sent from my Galaxy Nexus using xda premium

[email protected] said:
the smartest thing u can do is get galaxy nexus toolkit 10.1.0 for your Mac. It will allow you to flash whichever factory image u want and also unlock your bootloader and root your phone if you want. You can find a thread for the tool kit on xda itself. My friend and I did this to update to 4.2 the day it released. If it helps please press the thanks button.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
good. god. no.
dont use a toolkit.

So I just tried using CWM to install the JRO03C -> JZO54K, and I get this error:
asset failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.1.1/JRO03C/398337:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro"4.1.2'JZ054K/485486:user/release-keys"
E: Erros in /sdcard/----- filename.zip ------
(Status 7)
Installation Aborted

Using a toolkit is very inviting when I know nothing about what I'm doing and no one appears to be able to help.
Why should I NOT use a toolkit.

are you sure you're on yakju and downloading the OTA update to yakju?
did you previously root your phone and modify anything?

Zepius said:
are you sure you're on yakju and downloading the OTA update to yakju?
did you previously root your phone and modify anything?
Click to expand...
Click to collapse
No I've never rooted it (I think my lack of knowledge here proves I'd be unlikely to manage that myself) it's a Yakju phone, running JRO03C for sure, its what it says on the screen.
Anyway, I THINK I'm managing to get the Fastbook Flash technique working now. I hadn't fully unzipped the Image for 4.2, now I have and have the system.img files etc to work with.
I'll let you know how I get on.

davidpye said:
No I've never rooted it (I think my lack of knowledge here proves I'd be unlikely to manage that myself) it's a Yakju phone, running JRO03C for sure, its what it says on the screen.
Anyway, I THINK I'm managing to get the Fastbook Flash technique working now. I hadn't fully unzipped the Image for 4.2, now I have and have the system.img files etc to work with.
I'll let you know how I get on.
Click to expand...
Click to collapse
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave

davidpye said:
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave
Click to expand...
Click to collapse
at least you've managed to flash it// i got confused and decided to wait for ota.

Why would you say don't use a toolkit? It is really easy and does everything for you I rooted my phone with it.
Sent from my Galaxy Nexus using xda premium

davidpye said:
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave
Click to expand...
Click to collapse
Now, if you look back on the procedure you did with fastboot... you know how to restore your device to factory state, step by step. No toolkits, no scripts.
Sent from my i9250

Sending in device to Samsung, need to reset to original settings

I'm sending in my galaxy nexus to samsung to get it repaired/fixed and was wondering what I need to do to reset it to factory settings/state. I know I need to unroot, but what else?
Sorry for the beginner question, I just don't want to send it in and get it sent back because of some software thing I forgot.
Thanks, and have a nice day!

any help?

cardboardhome said:
any help?
Click to expand...
Click to collapse
I'd flash a stock rom directly from Google. Their script wipes everything out and goes completely stock. And then you can run `fastboot oem lock` to lock the bootloader. That's about as stock as you can get.

EfemaN said:
I'd flash a stock rom directly from Google. Their script wipes everything out and goes completely stock. And then you can run `fastboot oem lock` to lock the bootloader. That's about as stock as you can get.
Click to expand...
Click to collapse
So if I flash a stock rom with the galaxy nexus toolkit will it unroot my phone or do I still need to do that? And then what do I use to run the "fastboot oem lock"? What about like CWM and like busybox? Will the stock rom get rid of those too?
Thanks for your help btw.

cardboardhome said:
So if I flash a stock rom with the galaxy nexus toolkit will it unroot my phone or do I still need to do that? And then what do I use to run the "fastboot oem lock"? What about like CWM and like busybox? Will the stock rom get rid of those too?
Thanks for your help btw.
Click to expand...
Click to collapse
What part of 'completely stock' is hard to understand?
Stop using toolkits and do it the Google way.
Sent from my Nexus 5

Okay, I just wanted to make sure. Thanks.