Develop Bugs

[Q] Getting 4.0.4 Stock ROM

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.

No lockscreen or Market/Google Play

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

Is jelly bean available in the UK OTA or otherwise

I've searched for an answer for this on google and on here, but can't find one anywhere. apologies if I'm being dim.
I've just bought an unlocked Galaxy nexus of ebay (I9250) and I've put my o2 uk sim into it. I only bought it so I could get my hands on jellybean.
Is it actually available for this handset in the uk ota or otherwise (without rooting)
thanks
currently running 4.0.4

depends on the firmware you are on.
what does the build number say in the about phone section under settings?

Imm76k.i9250xwld2

tomthefear said:
Imm76k.i9250xwld2
Click to expand...
Click to collapse
yakjuxw is the version you have and i'm pretty sure JB is not out for that version.
the best way to get jellybean on your device is to convert to stock yakju. here is a great guide to converting to yakju: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
yakjuxw is the version you have and i'm pretty sure JB is not out for that version.
the best way to get jellybean on your device is to convert to stock yakju. here is a great guide to converting to yakju: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks for the fast reply. I got a nexus because I wanted jellybean without any hassle. This method looks pretty intense.
Was there a way to tell if my device would have an update available before I bought it?
what's the difference between yakjuxw & yakju? is it a regional thing?
if i do convert to yakju, will it be like my handset was always yakju (if you get me?)
EDIT: I think i meant is yakju an official google rom

tomthefear said:
Thanks for the fast reply. I got a nexus because I wanted jellybean without any hassle. This method looks pretty intense.
Was there a way to tell if my device would have an update available before I bought it?
what's the difference between yakjuxw & yakju? is it a regional thing?
if i do convert to yakju, will it be like my handset was always yakju (if you get me?)
Click to expand...
Click to collapse
its a very simple process. if you follow the steps as they are and do not skip anything, you will be fine and if you happen to run into any problems, me or efrant can help you if you post in the thread
the difference is regional and yakju is updated directly from google. anything other than yakju, takju (US play store version) and mysid (verizon variant) is updated by samsung
if you convert to yakju, you will notice no difference. the GSM version's hardware is the same across all variants.

So if i do this process, will it just be like I have a "pure" nexus, and i will receive any future ota updates?
also, do i need to root or anything?
I'm stressing a bit because that is what I thought I was getting

tomthefear said:
So if i do this process, will it just be like I have a "pure" nexus, and i will receive any future ota updates?
also, do i need to root or anything?
I'm stressing a bit because that is what I thought I was getting
Click to expand...
Click to collapse
you will have a pure nexus and will updates as soon as they are available directly from google
the only thing you will be doing is unlocking the bootloader. this is not the same as rooting, and you can always relock the bootloader for a pure stock look, although having it unlocked does nothing really.
just follow the steps and you will be fine.

sorry for bombarding you with questions.
Does it make a difference if I go for the 4.0.4 (IMM76I) 4.1.1 (JRO03C)?
I'm assuming I'd just want to go straight to 4.1.1

tomthefear said:
sorry for bombarding you with questions.
Does it make a difference if I go for the 4.0.4 (IMM76I) 4.1.1 (JRO03C)?
I'm assuming I'd just want to go straight to 4.1.1
Click to expand...
Click to collapse
download the yakju 4.1.1 from google (there's a link in the guide) and flash directly to jelly bean.

I'm on mac and there isnt a version of 7zip available. It seems to have unzipped fine with the native osx unarchiver. is that ok?
Ive got the 6 img files.

tomthefear said:
I'm on mac and there isnt a version of 7zip available. It seems to have unzipped fine with the native osx unarchiver. is that ok?
Ive got the 6 img files.
Click to expand...
Click to collapse
yes there should be 6.
for all the fastboot commands, you will enter them in terminal and instead of just fastboot, you'll need to start the commands with ./
so it'd be like: ./fastboot flash system system.img

tomthefear said:
I'm on mac and there isnt a version of 7zip available. It seems to have unzipped fine with the native osx unarchiver. is that ok?
Ive got the 6 img files.
Click to expand...
Click to collapse
Try 7zX for osx.
Sent from my Galaxy Nexus using Tapatalk 2

Done!! All seems to have worked correctly.
Thanks so much for your help.
is there any way to check that every step worked correctly?
if i want to return the phone (to claim on the warranty etc) would i just have to lock the boot loader?

tomthefear said:
Done!! All seems to have worked correctly.
Thanks so much for your help.
is there any way to check that every step worked correctly?
if i want to return the phone (to claim on the warranty etc) would i just have to lock the boot loader?
Click to expand...
Click to collapse
check the about phone section to look at the build number and android version
yes, and you can do that now if you really want (i dont recommend it unless you really are going to stay 100% stock all the time). the command is: ./fastboot oem lock

am i correct in thinking if i do a factory restore that it wont get rid of jellybean.

tomthefear said:
am i correct in thinking if i do a factory restore that it wont get rid of jellybean.
Click to expand...
Click to collapse
Correct. It only removes all data and apps from the phone, including your sdcard
Sent from my Galaxy Nexus using Tapatalk 2

Last question...(probably)
is it likely that the retailer i bought the device from will be able to tell that i installed a new version of the operating system?
I have been having problems with the phone restarting itself randomly. I have read that this is quite a common problem and the hardware most likely needs replacing. but dont want them to think it was me tinkering that has caused this (they specifically asked if id tried to install a custom os)
cheers

yakjuxw JRO03C from IMM76K update is now available.

[Q] TWRP For 550/551M Zenfones

So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.

mrbubs3 said:
So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.
Click to expand...
Click to collapse
Well for starters, we'd need the bootloader unlocked (as per Asus) and a preferably better rooting method to get started. Other than that, you'll be pleased to know that we may end up receiving OFFICIAL TWRP since DeesTroy is planning to get a Zenfone 2!:thumbup: (as mentioned here: http://forum.xda-developers.com/showthread.php?p=60352547)
Sent from the Ace's MB865 using Tapatalk

I thought the bootloader was already unlocked, as you can push system.img via bootloader. Or does the locked bootloader only prevent the changing of the boot.img file?

mrbubs3 said:
I thought the bootloader was already unlocked, as you can push system.img via bootloader. Or does the locked bootloader only prevent the changing of the boot.img file?
Click to expand...
Click to collapse
I don't really have the details on that, I'm only reiterating what was confirmed by a mod on the Zentalk forums that it is indeed locked. It's rather interesting that we can flash through it, but I'm not really experienced in bootloader unlocking enough to tell what's going on.
Sent from the Ace's MB865 using Tapatalk

mrbubs3 said:
So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.
Click to expand...
Click to collapse
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?

huzgu444 said:
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?
Click to expand...
Click to collapse
I use T-Mobile, so perhaps those limitations do not apply to me. I have not seen anyone reporting on service issues with AT&T at the time of posting.

The difference between a locked and unlocked bootloader is that a locked bootloader only accepts signed packages (packages built with the unique keys from Asus) while an unlocked bootloader will accept packages signed by anyone.
The rooted images are signed by Asus themselves, which lets us flash them through a locked bootloader.
If you push a system.img not signed with Asus' keys your device will not boot.

seshmaru said:
The difference between a locked and unlocked bootloader is that a locked bootloader only accepts signed packages (packages built with the unique keys from Asus) while an unlocked bootloader will accept packages signed by anyone.
The rooted images are signed by Asus themselves, which lets us flash them through a locked bootloader.
If you push a system.img not signed with Asus' keys your device will not boot.
Click to expand...
Click to collapse
That's ^ said by people who never tried it by himself.
Locked bootloader won't boot unsigned kernel images only (you can flash them through fastboot, but won't be able to boot). This includes recovery.img and boot.img. There is no signature in system.img, that's why you can flash pre-rooted system.img an boot.

sorg said:
That's ^ said by people who never tried it by himself.
Locked bootloader won't boot unsigned kernel images only (you can flash them through fastboot, but won't be able to boot). This includes recovery.img and boot.img. There is no signature in system.img, that's why you can flash pre-rooted system.img an boot.
Click to expand...
Click to collapse
Feel free to try and unpack, modify, and pack system.img. Then feel free to attempt to flash it.

Hey, so maybe instead of having a pissing match between superusers/devs, can we perhaps focus on the task of seeing how probable it will be to unlock the bootloader/compile TWRP?

mrbubs3 said:
Hey, so maybe instead of having a pissing match between superusers/devs, can we perhaps focus on the task of seeing how probable it will be to unlock the bootloader/compile TWRP?
Click to expand...
Click to collapse
if asus follows its usual pattern, they'll have a bootloader unlock tool released eventually

seshmaru said:
Feel free to try and unpack, modify, and pack system.img. Then feel free to attempt to flash it.
Click to expand...
Click to collapse
I did it already. Works fine. I've uploaded pre-rooted system.img in this topic: http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
What i'm doing wrong?

lyeith said:
if asus follows its usual pattern, they'll have a bootloader unlock tool released eventually
Click to expand...
Click to collapse
I hope so. I am itching to make this my DD. After that, I would need TWRP, a more robust kernel, and a nifty protective case to make me firmly comfortable. Then I say au revoir to my Moto G 2014.

huzgu444 said:
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?
Click to expand...
Click to collapse
I'm in Dallas on At&t and no complaints here. My girl is in PR at the moment and all good too. So I'd say check your zone and what bands it runs thru.

lordpipa said:
I'm in Dallas on At&t and no complaints here. My girl is in PR at the moment and all good too. So I'd say check your zone and what bands it runs thru.
Click to expand...
Click to collapse
Are you getting 4g or 4gLTE and which firmware are you using. My Z00A is not getting 4gLTE atm on ATT in dallas (plano), only getting 4g. Currently connected on Band 5 not band 17

yeah Im getting 4gLTE but im not running stock firmware.

Not getting MDB08I OTA

Got my 5X earlier last week, but I haven't been able to get the MDB08I OTA update. Anyone else not getting it? Is there anyway to force it?
Thanks!

You can sideload it if you can download the ota file. Google rolls it out based on some algorithm based on IMEI. You'll get it eventually.

Still waiting for my USB-C to A cable to come in. Just wasn't sure if something else was up with my phone. Didn't know the rollout was based on IMEI; the more you know =)
Thanks!

i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.

Mine was telling me there was an update as soon as I unboxed it and turned the WiFi on. Weird that you aren't getting the update.
On another side note. I've had no problem with getting adb to work.

I've had my 5x since last Monday (19th October) and I don't have it yet either. I'm in the UK.

I'm on MDA89E after getting from cpw yestaday and unboxing didn't get any update yet but loving the 5x so far
Sent from my Nexus 5X using Tapatalk

I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.

myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
I thought the point of Nexus range was there was no delay due to carriers?

myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
Nope. I had no SIM installed when I was alerted to the update. Has nothing to do with SIM or carrier.

Does the bootloader have to be locked to get otas?

nyjumpman said:
Does the bootloader have to be locked to get otas?
Click to expand...
Click to collapse
Probably it's OK to be unlocked, but probably it's not OK to have a custom recovery if you want OTA's. (and want them installed). Best bet is to download B08I and install it via the batch file.
To some other poster in this thread asking about being unable to see phone from adb when recovery is booted up: If it's stock recovery, that makes sense, but if it's custom recovery, you should see adb devices having output.

oxfordmark said:
I thought the point of Nexus range was there was no delay due to carriers?
Click to expand...
Click to collapse
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.

myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Like I posted earlier. I was alerted to the update and had no SIM installed.

myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Oh right, must be for things like wifi calling.

manilaboy1vic said:
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Click to expand...
Click to collapse
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.

http://www.droid-life.com/2015/10/21/nexus-5x-receiving-update-today-to-build-mdb08i/
Just followed these instructions and the associated links and 30 minutes later ... updated FTW.
Was having problems, at first, with my phone to being recognized. Either the initial usb 2.0 port was jacked or not, I switched to another port and made sure the cable was seated properly and it was picked up right away.

My N5X on AT&T got this update last Tuesday when I got the phone. My girlfriends N5X on Verizon did not yet get the update OTA. Might have to do with carrier?

I always set my phone up without a SIM. Got the update right away during the set up process.

Jexx11 said:
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
Click to expand...
Click to collapse
thanks.. that cmd worked..
Android is upgrading... (w00t)
was easier for me to get it going on linux ubuntu.. now onto the hotspot tutorial