Related
This is not a Rom Manager backup or a 41D upgraded to 41F but an official 41F stock image build by Google obatined from
http://code.google.com/android/nexus/images.html
I have added a batch file to automatically fastboot flash this under windows and restore your phone to stock.
turn the device on with both volume buttons held and enter fastboot mode. connect usb and execute flash-windows.bat (included) you may need to install samsung adb driver and boot unlock the device though (which you can find on this forum)
tested on my galaxy nexus and restored successfully.
https://rapidshare.com/files/352067458/itl41f.zip
mirror
http://www.filesonic.com/file/4075307854
zyo said:
This is not a Rom Manager backup or a 41D upgraded to 41F but an official 41F stock image build by Google obatined from
http://code.google.com/android/nexus/images.html
I have added a batch file to automatically fastboot flash this under windows and restore your phone to stock.
turn the device on with both volume buttons held and enter fastboot mode. connect usb and execute flash-windows.bat (included) you may need to install samsung adb driver and boot unlock the device though (which you can find on this forum)
tested on my galaxy nexus and restored successfully.
https://rapidshare.com/files/352067458/itl41f.zip
mirror
http://www.filesonic.com/file/4075307854
Click to expand...
Click to collapse
Thanks OP worked great!
Why would you upload mirrors when Google themselves are hosting the files? Wouldn't it be more reliable to just download straight from Google?
Also, I'm assuming that they'll be updating the recovery images for each official update as well... Meaning your mirrors would be outdated soon anyway. Just a thought.
Thanks anyway though, these will come in useful!
Google's package is compressed in tgz and comes with sh script, also doesnt include fastboot windows.
I put all necessary utils together with a bat script so user can just double click and restore.
Radio Image
can you change the radio image like this XXIK6? http://forum.xda-developers.com/showthread.php?t=1374077
greetings pittrich
pittrich said:
can you change the radio image like this XXIK6? http://forum.xda-developers.com/showthread.php?t=1374077
greetings pittrich
Click to expand...
Click to collapse
I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it
will OTA updates works if i flash this image (assuming i've also cloclwork mod recovery)?
idan_mo said:
will OTA updates works if i flash this image (assuming i've also cloclwork mod recovery)?
Click to expand...
Click to collapse
Since it's 100% Google image, I don't see why OTAs wouldn't work.
ok, thanks!
qwer23 said:
I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it
Click to expand...
Click to collapse
You could do what my idiot brother did to my Nexus S. Format /boot from Clockwork mod (under the storage options I believe) and then turn the phone off. The only way to unbrick it is to send it to Samsung, or the guy on XDA who runs that company that uses JTAG to fix it (which is what I did)
SphericalPuma said:
You could do what my idiot brother did to my Nexus S. Format /boot from Clockwork mod (under the storage options I believe) and then turn the phone off. The only way to unbrick it is to send it to Samsung, or the guy on XDA who runs that company that uses JTAG to fix it (which is what I did)
Click to expand...
Click to collapse
Why would that brick the device? Can't you still get into the bootloader or recovery and flash a new boot image?
I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it
Click to expand...
Click to collapse
where there is a will, there is a way
Worked great for me. Thanks very much.
Rik.
@ OP
Thank you man, a million times. Now I was able to replace Samsung's screw up Stock.
@ zyo will this factory image also work for lte or is this strictly GSM image? I have an issue where neither cwm or adb will restore my stock nandroid and I want a full stock backup just to be safe
Sent from my Galaxy Nexus using xda premium
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
just execute the scripts for your platform.
psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
If you can read German I can give you the link to my step-by-step guide. However I am not able to post it here directly, yet. Too much of a noob still.
psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
That's a good idea & hopefully someone will.
+1
I wouldnt flash this on LTE model. I have heard it comes with different radio and stuff (obviously)
I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.
I used that toolkit and that update and I can confirm that they both work
That is NOT the ROM for you, you have a GSM device. H+ is not LTE.
The GSM and CDMA devices are markedly different.
Try to read in this thread... as well as efrant posts, you will get your answer !
N.B. most important thing is read and read and read... before doing anything..
http://forum.xda-developers.com/showthread.php?t=1391881
Zackster said:
I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.
Click to expand...
Click to collapse
Argh! Didn't realize CMDA was the LTE version.
Thanks to everyone! Will read through that thread tonight and hopefully all is well.
Zackster said:
[snip]
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
Click to expand...
Click to collapse
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Zackster said:
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Click to expand...
Click to collapse
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.
efrant said:
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
Click to expand...
Click to collapse
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
efrant said:
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Click to expand...
Click to collapse
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
efrant said:
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.
Click to expand...
Click to collapse
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!
Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.
Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Click to expand...
Click to collapse
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
Zackster said:
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
Zackster said:
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk
Zackster said:
[snip]
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I've found that these drivers work the best.
krblake13 said:
http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!
Click to expand...
Click to collapse
Great! I'll look into this! Good to know it's worked for someone else in this situation.
descendency said:
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.
Click to expand...
Click to collapse
Hmm... disappointing, for sure. I had found this MoDaCo ROM, which is why I asked.
efrant said:
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Argh, I keep getting rooting and the bootloader confused. Sorry about that.
efrant said:
I've found that these drivers work the best.
Click to expand...
Click to collapse
Excellent, I'll give these a try.
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Pete720 said:
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Click to expand...
Click to collapse
Unlock the boot loader firstly but beware it will wipe your sdcard.
Use fast boot to unlock it, type oem fastboot unlock and go from there.
Flash cwm using fastboot by typing fastboot flash recovery xxxxxxx.img (xxxxx.img is whatever the filename is)
You are probably familiar with cwm so I won't bother explaining that.
All the rooms here have everything working on them. We'll except sense 4.0 and touchwiz ports etc. But that's obvious.
Ps. All phones have locked bootloaders!
Yeah, you might mean unlocked bootloader. You do have to unlock it first, but it doesn't take an exploit to do so. See here for a starting point:
http://forum.xda-developers.com/showthread.php?t=1400871
As for the best rom, impossible to say, so many . It depends on what exactly you're looking for. aokp is probably the most features-popular, but there are many others. I use cm9 with the reloaded mod, personally.
sent from my Zerg Hatchery.
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Pete720 said:
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Click to expand...
Click to collapse
SDK, Fastboot, ADB
anton2009 said:
SDK, Fastboot, ADB
Click to expand...
Click to collapse
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Pete720 said:
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Click to expand...
Click to collapse
Options 8 (Extract and Flash Google Factory Stock ROM), 10 (Reflash Stock Recovery [just to be safe]), and 11 (Relock bootloader) will return it all to stock. I know, because I just had to do this to 3 GNex's this past week to send them back to Verizon
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Okaay said:
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Click to expand...
Click to collapse
Only if you are stock and rooted.
He is running a custom rom and kernel and has cwm flashed, that method will not revert them to stock.
nodstuff said:
Ps. All phones have locked bootloaders!
Click to expand...
Click to collapse
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
nicholaschum said:
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
Click to expand...
Click to collapse
My apologies, I totally forgot to update my signature. I do not have the GSII anymore.
Can anyone point me int he direction of the box stock rom file I need to work with Toolkit to restore my phone? I followed the directions and got the image from code.google.com but it wont install. ALways says something is missing.
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Pete720 said:
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Click to expand...
Click to collapse
I believe that the toolkit will auto download if you just run the option.
I could use some help so I don't brick my phone. I have done a search or two on how to root this particular build and it's probably me - I don't think I have found any information to my question. On xda there was info on the superboot method from modaco that it only worked on ICS4.0.1. The GNex toolkit v7 does not have build IMM30d included. I purchased the phone from Google play and received it late last week. Is this build supported by any root method mentioned? Or will anyone link me to a method that supports the build?
My signature will get you running in a jiffy, sir.
Are you familiar with the toolkit at all?
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
Don't use toolkits. It's not that there is anything inherently bad with them, but having a program do everything for you without understanding how it is doing it means that you don't know how to fix anything if something goes wrong. It's better to do things manually and learn how everything works before taking the easy way through it.
Haha, alright. This is in the Q&A section and I'm sure as hell no developer. I'm coming from a mytouch4g. Had to use adb to downgrade from gingerbread to froyo to root it. Even after reading it over a couple times the directions were still intimidating. It looked like an easy option. Appreciate the input though.
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Jubakuba said:
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Click to expand...
Click to collapse
Appreciate the link/input you posted. I'll follow it correctly I hope as it doesn't appear to be rocket science.
Zepius said:
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
Click to expand...
Click to collapse
hey thanks for rating this one star. :good:
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
wasnt me that did that. i dont rate threads.
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Jubakuba said:
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Click to expand...
Click to collapse
Zepius said:
wasnt me that did that. i dont rate threads.
Click to expand...
Click to collapse
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Most likely, if you connect you device to Wi-Fi, it will receive an OTA update -- I think IMM76 (blanking on build number).
dirtyreturn said:
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Click to expand...
Click to collapse
The driver needs to install TWICE: once when your device is booted normally, and once when booted into the bootloader.
I'm having a problem using juba's rooting method. It won't go into recovery mode. I'm using the same android and build as the fellow poster. Any help? It's just sticking on the google word with the unlock thing at the bottom when I try to reboot into recovery from the bootloader.
Hold down vol+ and vol- and turn the phone on. When the menu comes up, select recovery.
Hey there,
So I just got my GSM Galaxy Nexus in the mail today and found a couple things to be a bit odd. You see, my package came with 2 Galaxy Nexuses (or nexi?) and my brother's phone seemed completely normal. It had Android 4.0.4 which he instantly got an update for Jellybean. My phone on the other hand was a bit off, as stated previously. My Galaxy Nexus shipped with Android 4.0.1, when i went to the "about phone" tab, there was no option to even check for a system update, my lock screen doesn't work (security settings are on slide yet the power button just wakes my screen and no sliding to unlock required), I have no market or google play store, I can't add a Gmail account under the "accounts and sync" tab, and my home button wasn't working (factory resetting fixed this).
I'm honestly just stuck on what to do about this device. I've factory reset this device 5 times already and nothing else has worked except for fixing the home button which wasn't working on my initial boot up.
Is there any solution to this Nexus or do I just have a defective one?
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
netbuzz said:
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
Click to expand...
Click to collapse
Build Number: full_maguro-eng 4.0.1 ICL23D 347 test-keys
And why couldn't I have picked my brother's? Haha I don't know!
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
airkenada said:
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The problem is that my settings are set to slide yet my phone is acting as if it's set to none
El Daddy said:
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Does this void any warranty?
BrokeEven said:
Does this void any warranty?
Click to expand...
Click to collapse
You won't have a problem with warranty if you are running a stock build.
http://www.blogcdn.com/www.engadget.com/media/2011/11/nexnex20111117103746mat400mat400.jpg
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
Ha yeah! The not-so-normal apps that I have on my phone include "Angry GPS", "Dev Tools", and "SUB PBA Test". I checked with my Brother's Nexus running JB and he's got none of those. I called into Google's hotline for Nexus support and was able to get in touch with one of the supervisors. I was told that the device I received was a Developer's Model and that it was the "strangest thing ever".
El Daddy said:
You won't have a problem with warranty if you are running a stock build.
Click to expand...
Click to collapse
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
BrokeEven said:
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
Click to expand...
Click to collapse
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step. Flashing with fastboot is the safest way to do things and there is a very small chance of you bricking your phone.
Also what did google tell you to do when you called them?
Development Tools
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
I just got another Nexus from Play Store.
It's in developer mode, without Google apps and filled with a bunch of testing tools, like AngryGPS and Screen Test, the same menu in this image from maschiosoosa.
I tried to call Google Support and they give me two options.. One is doing exactly what everybody does.. Flash a stock Google image (but they said: "it's a very difficult way" lol) or the second, they will call Samsung for a replacement.
It's not a defective device, but it's kind of getting a Windows 8 Consumer Preview. A thing that it's not finished yet. Shame on Goole. lol
I'll flash of course.. It seems the bootloader is unlocked and its probably easy to do the flash thing.
Hey BrokeEven, if you got your device from Play Store you can ask for a replacement (if you are not sure of the flash image).
And probably your bootloader is already unlocked (at least if you received this same dev tool device).
El Daddy said:
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step.
Also what did google tell you to do when you called them?
Click to expand...
Click to collapse
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Yep... The same case... The guys on Google are very funny. lol
Reboot your device and check if theres a unlocked locker at the bottom of the Google logo screen.
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Reboot the phone, when it's rebooting (showing google logo) if there's unlocked sign (lock that is unlocked) under the google logo, then it's unlocked Nexus. If you only see Google logo, then it's just locked Nexus
I don't know whether this is a curse or a blessing... I remembered when i ordered this phone I said "meh, I'm not gonna bother with rooting and flashing ROMs. I'll just stick to stock. And so Google sends me a Nexus with an unlocked bootloader and now force me to flash back to stock (or root) in order to get my phone fully functional
One pic is my unlocked bootloader, the other is a picture of my ALL the apps on my phone
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
El Daddy said:
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
BrokeEven said:
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
Click to expand...
Click to collapse
On windows just hold down shift while you right click in the folder. You will see open command prompt here or similar.
Sent from my Nexus 7 using Tapatalk 2