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] Is it necessary to unlock the bootloader before installing a custom ROM?

Good morning/afternoon everyone,
I have the lovely new Tab Pro 8.4 and would like to update to CM11. However, I cannot unlock the bootloader (multiple computers have been tried, in Odin mode, adb devices sees the unit, but fastboot does not. I did get a TWRP recovering installed).
Is it necessary to unlock the bootloader before installing CM11?
Many thanks in advance for any answers. I have looked around a great deal, and it isn't clear to me from the many overlapping set of instructions if this is really necessary or not.

No need to unlock. Just flash or odin.
Sent from my SM-T320 using Tapatalk

nashton said:
Good morning/afternoon everyone,
I have the lovely new Tab Pro 8.4 and would like to update to CM11. However, I cannot unlock the bootloader (multiple computers have been tried, in Odin mode, adb devices sees the unit, but fastboot does not. I did get a TWRP recovering installed).
Is it necessary to unlock the bootloader before installing CM11?
Many thanks in advance for any answers. I have looked around a great deal, and it isn't clear to me from the many overlapping set of instructions if this is really necessary or not.
Click to expand...
Click to collapse
No, you can just flash. No need to unlock bootloader, because you set the knox bit by flashing recovery by odin.

Rutr said:
No, you can just flash. No need to unlock bootloader, because you set the knox bit by flashing recovery by odin.
Click to expand...
Click to collapse
Does flashing to cm 11 void warranty

superman3486 said:
Does flashing to cm 11 void warranty
Click to expand...
Click to collapse
Yes.

superman3486 said:
Does flashing to cm 11 void warranty
Click to expand...
Click to collapse
Setting knox (by flashing) "may" void your warranty. But in many cases users got repairs by warranty service, even if the device is rooted. My HTC ONE X also rooted has been repaired by warranty service for free. They told me, that my device was rooted, but the issue was hardware failure.

[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

Damn...just made a huge mistake. phone bricked?

My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?

Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square

Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know

well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....

Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.

Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...

Good luck. Will Google not rma it?

Did I brick my device? :(

I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement

i am just curious, how were planning on flashing a rom with locked bootloader?

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.

Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.

gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."

gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?

Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?

ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.

ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.

ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!

I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.

My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?

dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!

Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.

ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs

mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.

ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs

mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.

ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs