Develop Bugs

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

[Q] Question about warranty when unlocking bootloader and installing custom ROMS

Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!

danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!
Click to expand...
Click to collapse
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.

charesa39 said:
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.
Click to expand...
Click to collapse
Thanks mate for your explanation, I was looking for this.
I have some experience flashing android devices so I probably won't mess up my device I have bought my nexus 7 2013 recently and I don't want to have no warranty when I discover a hardware issue.. But everything seems to be fine actually. I'll install a cm 11 nightly soon.
Sent from my Nexus 7 using xda app-developers app

danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
Click to expand...
Click to collapse
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100

tetakpatak said:
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100
Click to expand...
Click to collapse
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!

danielsinnema said:
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!
Click to expand...
Click to collapse
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7

tetakpatak said:
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Sent from my Nexus 7 using Tapatalk

danielsinnema said:
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Click to expand...
Click to collapse
Hey, great mate!
That's why we have a community here.
Don't hesitate to ask if anything.
tetakpatalked from Nexus 7

Yes thank you for creating this thread because then it helps encourage people like me want to root and learn things I want to learn to be a developer when I grow up!
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Q] Bootloader unlocking for LG G3 D850,D855

Looked at some threads and still wondering if they still works on unlocking bootloader. Seems like it tooks so much time for Devs, have anyone knows whats happening? Is it seems unlockable or not? :/

bdogan1912 said:
Looked at some threads and still wondering if they still works on unlocking bootloader. Seems like it tooks so much time for Devs, have anyone knows whats happening? Is it seems unlockable or not? :/
Click to expand...
Click to collapse
The T-Mobile US version comes unlocked. No one knows yet whether the other G3 versions will be able to be unlocked. The G2 was never unlocked but a work around where you could install custom Roms and kernels was eventually found. Its very much wait and see.

Batfink33 said:
The T-Mobile US version comes unlocked. No one knows yet whether the other G3 versions will be able to be unlocked. The G2 was never unlocked but a work around where you could install custom Roms and kernels was eventually found. Its very much wait and see.
Click to expand...
Click to collapse
Looked at many forums that people opened about 1-2 months ago. It seems like very very difficult to unlock it. I have much respect developers whichones tries to unlock it. Hope they can be successful on this. I'm glad to have stock rom this is very smooth i can admit it not like laggy touchwiz. But want to give a try to CM or PA or any AOSP ROM's like this, because back in time i was used AOSP based rom on my S III I9300 and loved it. Only reason that i want AOSP ROM is i think im loving pure Android it gives me ultra-smooth performance and simple UI.

The Verizon and AT&T threads have a bounty over $5700 and it looks like a few devs are close to having a solution.

what about the sprint ls990
Any word for Tge sprint ls990 at all I know it might be wrong section but might as well post somewhere

i can try
If someone can point me into the direction required to do bootloader unlocking i will give it a shot. Am a developer but have never attempted to do a bootloader unlock.
​

crqzyvonzipper said:
If someone can point me into the direction required to do bootloader unlocking i will give it a shot. Am a developer but have never attempted to do a bootloader unlock.
​
Click to expand...
Click to collapse
Well we have to ask it to developers whichones pro. on this.

bdogan1912 said:
Well we have to ask it to developers whichones pro. on this.
Click to expand...
Click to collapse
If only someone could tell me how to get to debug the software then ill be able to go from there because google isnt your friend when trying to find out.

[email protected] said:
Any word for Tge sprint ls990 at all I know it might be wrong section but might as well post somewhere
Click to expand...
Click to collapse
Devs in the AT&T bounty thread are working on an unlock for ALL variants besides the T-Mobile one.
sent from my LG G3

Yes. I know about that but it seems ike they are tking quite some time and I am not sure if they have given up?
Sent from my LG-D855 using XDA Free mobile app

joeyhdownsouth said:
Devs in the AT&T bounty thread are working on an unlock for ALL variants besides the T-Mobile one.
sent from my LG G3
Click to expand...
Click to collapse
Hope they can unlock soon. Phone was out on May and we're on September. Almost 4 months since released. And i know its hard but we have to wait. I wish i have money to donate/bounty 20 more dollars :/

crqzyvonzipper said:
Yes. I know about that but it seems ike they are tking quite some time and I am not sure if they have given up?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3

joeyhdownsouth said:
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3
Click to expand...
Click to collapse
Locked bootloader is like hot beer. Seems and tastes awfully. I wish companies sends their flagships with unlocked bootloader like T-Mobile did. Without custom recovery we're not able to even do a simple tweak (The tweaks who requires recovery such as modified frameworks and SystemUI's) Otherwise there is another option G3 Tweaksbox. But it shows very limited options if you're poor to buy it.

joeyhdownsouth said:
It's giving them hell, there not sure they are gonna be able to, but there's always Loki to try, which is kinda like going around the boot loader.
sent from my LG G3
Click to expand...
Click to collapse
HMMMM well ill have a look at what i can do tomorrow. Maybe i can find a small window here. I almost want to say that the abswer would be to adjust the bootloader to simply allow multi boot possibilities with partitions (at least in my mind that would be pretty cute).
I dont even really want the money. I just want to be able to do what i need to do. Multi OS's on one device.

bdogan1912 said:
Locked bootloader is like hot beer. Seems and tastes awfully. I wish companies sends their flagships with unlocked bootloader like T-Mobile did. Without custom recovery we're not able to even do a simple tweak (The tweaks who requires recovery such as modified frameworks and SystemUI's) Otherwise there is another option G3 Tweaksbox. But it shows very limited options if you're poor to buy it.
Click to expand...
Click to collapse
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3

crqzyvonzipper said:
If only someone could tell me how to get to debug the software then ill be able to go from there because google isnt your friend when trying to find out.
Click to expand...
Click to collapse
Also it's good to someone has interest about it. But it's ultimately hard job that they cannot solved in past 4 months. I appreciate all the tries/works on this job. Developers, you da real MVP! Well, other than that small joke we're still waiting. Not only international model D855 other models such as AT&T is waiting to unlock bootloader. T-Mobile users lucky that they got unlocked G3. I hope they will find a cure about it. If you can afford http://forum.xda-developers.com/att-lg-g3/general/bounty-att-lg-g3-bootloader-unlock-t2820785 go this thread and give some bounty (You're not have to do that its only suggest and saying thanks to hardwork)

yeeeeeepppp
joeyhdownsouth said:
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3
Click to expand...
Click to collapse
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.

joeyhdownsouth said:
I've tried modifying one line in build prop, ended up softbricking. I won't change a thing until unlock, at least then you can have nandroids.
sent from my LG G3
Click to expand...
Click to collapse
So you can say, i tried to modifiying build prop and ended with softbricking but so i got nandroid which is nice to me. Me neither. On my Note 3 i was tweaking build prop without any problem i've even enabled softkeys (I wondered a bit about how it will look etc.) But not gonna touch until this thing unlocks fully. Using stock rom & root with bloatware removed. With helper programs such as Greenify+Coolify. It's like science it's all about develop, try, fail, develop (or fix/debug),try, fail, develop try, success. It's alla about to hardwork and i appreciate all the efforts that developers given on this topic.

crqzyvonzipper said:
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.
Click to expand...
Click to collapse
Variants have different bootloaders. So we cannot do a copy/paste on it. If it works like this the devices will be unlocked in 10 min. I almost softbricked too but won against my wonder and didn't touched anything. It now works good. I love G3 even its bootloader locked lol

crqzyvonzipper said:
Hehe ive also bricked this baby a few times now but lg has a cool restore tool that fixes all the issues.
Why cant we just copy the unlocked bootloader and overwrite the locked bootloader?
But nontheless. Maybe ill end upnrewriting a boot loader to work. But that might take some more time.
Click to expand...
Click to collapse
Why don't you go to the irc chat room where all the devs hang out and do their work? You can talk to them there and see what they've tried or what they haven't. Believe the channel is: #lg-g3

custom recovery . any source to get development updates?

Hey guys,I was wondering if theres any development blogs ,sites, that may get us an indication about what's going on with the custom recovery?
I'm looking for it now and then but all I get is antique topics about how the phone is just out to market and we should give it a month to see custom roms/recoveries .

subwoffer13 said:
Hey guys,I was wondering if theres any development blogs ,sites, that may get us an indication about what's going on with the custom recovery?
I'm looking for it now and then but all I get is antique topics about how the phone is just out to market and we should give it a month to see custom roms/recoveries .
Click to expand...
Click to collapse
T-Mobile is the only one with the bootloader unlocked so they have full access to using recovery and roms, I don't know if other variants are using a recovery yet since I am a vs985 (verizon) user I don't watch them closely
For vs985 we can't get into fastboot mode because verizon decided to remove or disable it, so we can't use tethered recovery (temporarily booting the recovery from adb shell)
I can tell you that Recovery's aren't hard to make at all. its just we don't have a way to use them right now &
Roms will quickly follow after Recovery's are able to be flashed

bunchies said:
T-Mobile is the only one with the bootloader unlocked so they have full access to using recovery and roms, I don't know if other variants are using a recovery yet since I am a vs985 (verizon) user I don't watch them closely
For vs985 we can't get into fastboot mode because verizon decided to remove or disable it, so we can't use tethered recovery (temporarily booting the recovery from adb shell)
I can tell you that Recovery's aren't hard to make at all. its just we don't have a way to use them right now &
Roms will quickly follow after Recovery's are able to be flashed
Click to expand...
Click to collapse
Any personal thoughts /guesses about how long will it take?
I'm really excited about it , because when I bought my g3 I left my note 2 for experiments, and hell isn't the name for what my oldie note went through.
My point is that I finally learned how to install custom EVERYTHING. from kernel to build.prop,and my hands are itchy to do the same on my g3

Unfortunately and until the bootloader is unlocked, we have to patiently wait for our great devs to unlock this retarded bootloader. It may take a couple of days, it may take a month, it may never happen. We just have to wait. Oh, and friendly advice: never ask for an ETA on xda

Ferindel said:
Unfortunately and until the bootloader is unlocked, we have to patiently wait for ou great devs to unlock this retarded bootloader. It may take a couple of days, it may take a month, it may never happen. We just have to wait. Oh, and friendly advice: never ask for an ETA on xda
Click to expand...
Click to collapse
Very true , I'm going to get a nexus as I'm not completely convinced an unlock will come and even if it may be awhile.

dabug123 said:
Very true , I'm going to get a nexus as I'm not completely convinced an unlock will come and even if it may be awhile.
Click to expand...
Click to collapse
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk

I hope that it wont take long till they find a way to unlock the bootloader. The stock rom is loaded with a lot of bloatware and lg apps that i never intend to use. I want to see how fast the g3 is on a cm 11!

Helloworld294 said:
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Where did you find this out at? If true it's the best news I've heard in months!

katsika said:
I hope that it wont take long till they find a way to unlock the bootloader. The stock rom is loaded with a lot of bloatware and lg apps that i never intend to use. I want to see how fast the g3 is on a cm 11!
Click to expand...
Click to collapse
i just installed some mod ( forgot the name , something liquid 4.4.4 ) on note 2 , and i didnt think that a phone , especially an old one, could be that quick and smooth .
i dying to do the same with my lg

subwoffer13 said:
i just installed some mod ( forgot the name , something liquid 4.4.4 ) on note 2 , and i didnt think that a phone , especially an old one, could be that quick and smooth .
i dying to do the same with my lg
Click to expand...
Click to collapse
Abit old maybe. But its not ainchent...2 MB ram and quad core cpu.. Its pretty good specs still.

Helloworld294 said:
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Please link us to where this was talked about great news, cheers.

skeamznz said:
Please link us to where this was talked about great news, cheers.
Click to expand...
Click to collapse
no news, this are older "news". you can find them in at&t lg3 forum section with forum search.
be patient, the devs don't like to get stressed and the whole xda drama about unlock.
jcase already said he is able to run custom images but time is the problem to release it. when everyone is stressing them, they will lose interest to unlock under pressure.
when it's ready you will know it. until release be quiet please. thanks.

There's the "news"
http://forum.xda-developers.com/showthread.php?p=55238605
Cheers
Sent from my LG-D852 using Tapatalk

The N910V bootloader has been unlocked?

Just saw it on the verizon note 4 forum. How come no one is posting about i? Can it be used on N910A variant?

Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

atx84 said:
Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....

bigbooker455 said:
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....
Click to expand...
Click to collapse
So the N910A still is no go. What a bummer!

Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL

cxyjordan said:
So the N910A still is no go. What a bummer!
Click to expand...
Click to collapse
YUP!

adambomb_13 said:
Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL
Click to expand...
Click to collapse
I was reading note4 AT&T thread and found this, like i said do not take any updates!
AT&T released an update with security enhancements yesterday, any word about this and how this affects us?
I am not sure. I know that I have my OTA blocked; however, I too find it interesting that a sudden security update is released now about two weeks after the Verizon hack is discovered and rolled out. It is stuff like this that tells me that their devs know something that we have yet to discover.

This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.

bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......

giga8547 said:
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......
Click to expand...
Click to collapse
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.

bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
We should be able to change the CID on any Note 4 so I don't see why this wouldn't work. Don't we need root to copy the aboot? My understanding was that the kingroot method doesn't work anymore after an AT&T update. It is now soft bricking phones. I am wondering if the security update could be removed by flashing the original 5.1.1 or maybe even 5.0.1.

dkmac said:
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.
Click to expand...
Click to collapse
I don't own a AT&T version of the Note4, can you roll back?

bigbooker455 said:
I don't own a AT&T version of the Note4, can you roll back?
Click to expand...
Click to collapse
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.

dkmac said:
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.
Click to expand...
Click to collapse
I feel you!

bigbooker455 said:
I feel you!
Click to expand...
Click to collapse
Yea, that's why I have been looking for the info that you were talking about. I want to see what I could do to help breath new life back into our phones.