Database Develop

[Q] phone stuck after update :/ need help

after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.

not a single reply !!??
i should throw the phone from my window then

Is it HTC dev unlocked? You can't do an ota if its not completely stock.

e-zee said:
after i got the OTA update, the phone finished downloading and started the installation process, the phone rebooted into that screen with the 3 green arrows (2 circling and 1 down). i left the phone on that screen for more than an hour or some and that's it it's stuck on that screen.
i tried the pull out the battery and put it in again and when i boot the phone it goes back to that screen.
plus i'm not able to boot into hboot nor doing anything and when i plug the usb to a pc it wont detect it.
i have tried everything i know so far :s and still no luck .... i would be glad if anyone can help me.
Click to expand...
Click to collapse
e-zee said:
not a single reply !!??
i should throw the phone from my window then
Click to expand...
Click to collapse
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?

tpbklake said:
You did not give enough information to even try to help you. As markj338 suggested, if you have modified your phone by unlocking the bootloader, flashing a custom recovery or rooted the phone, it will not apply the OTA successfully.
So what was the state of your phone before you attempted to run the OTA?
Click to expand...
Click to collapse
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended

e-zee said:
it's perfectly stock. i have locked the bootloader and installed a stock RUU before checking any updates, and i told you how my story ended
Click to expand...
Click to collapse
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?

acme anvil said:
So we are clear, your phone was completely stock? Or was your bootloader unlocked and you locked it before checking for updates?
Click to expand...
Click to collapse
the bootloader was unlocked, i relocked it then installed an original RUU after that everything was working normal, i checked for updates so i got the OTA update, then installed it and then my phone stuck on that screen.

What method did you use to lock your bootloader?

thanks guys for everything, i found a store to fix my phone, and they fixed it with jtag box and now it's brand new.

[Q] How do I factory reset my HTC Developer Edition but keep unlocked bootloader?

I have an HTC One Developer Edition (64GB) and it comes with a factory unlocked bootloader.
I flashed some recovery images, new kernels, etc, but I'd like to go back to the factory image with the factory unlocked bootloader.
I've tried using the HTC RUU file and it doesn't work unless you "fastboot oem lock", which I did, and it successfully restored the factory image but now the bootloader is "RELOCKED".
I can unlock using HTCDev.com but it erases a bunch of applications and it's no longer the factory developer edition image...
Can anybody help me?

sofakng said:
I have an HTC One Developer Edition (64GB) and it comes with a factory unlocked bootloader.
I flashed some recovery images, new kernels, etc, but I'd like to go back to the factory image with the factory unlocked bootloader.
I've tried using the HTC RUU file and it doesn't work unless you "fastboot oem lock", which I did, and it successfully restored the factory image but now the bootloader is "RELOCKED".
I can unlock using HTCDev.com but it erases a bunch of applications and it's no longer the factory developer edition image...
Can anybody help me?
Click to expand...
Click to collapse
Unlock it via HTCDev and flash back the data partition from my NANDROID, see my signature.
The issue is that unlocking the bootloader wipes the data partition, which has those apps. That's why they are missing. The NANDROID will fully restore your Dev Edition to the factory state.

Thanks for the information...
However, the NANDROID backup requires a custom recovery image, right?
I'm trying to reset everything (recovery image, boot image, data image, etc) back to factory and have the bootloader unlocked (and not say TAMPERED, etc).

Yes. You can fastboot a recovery without installing it but it will say tampered anyways.

Can I restore everything to stock and remove the tampered warning?

sofakng said:
Can I restore everything to stock and remove the tampered warning?
Click to expand...
Click to collapse
Yes, relock your bootloader, install the RUU. Then TAMPERED is gone but bootloader is locked. Unlock with HTCDev. I'd rather go with TAMPERED than with locked bootloader and the hassle with HTCDev.

Hmmm, maybe I'm doing something wrong.
I've relocked the bootloader and installed the RUU but it still says tampered. What can I be doing wrong?
I wish HTC had an RUU that resets the developer edition to factory unlocked (instead of requiring me to use HTCDev to unlock it again...)

You only need to worry about it saying tampered if you send it in for repair. Which you would flash back to stock anyway.
You don't see tampered when booting, so who cares!

Yeah, sorry... I'm new to Android and just trying to learn how to completely reset the phone.
Also, I'm wondering why the tampered warning is even displayed on the developer edition because isn't the entire purpose of this version to replace the different system images, etc?

sofakng said:
Also, I'm wondering why the tampered warning is even displayed on the developer edition because isn't the entire purpose of this version to replace the different system images, etc?
Click to expand...
Click to collapse
Because it's still the same hboot/bootloader but just sold pre-unlocked by HTC.

Ok, so just to clarify then, I can't really go back to factory unlocked (without the tampered warning), but it doesn't really matter...?

sofakng said:
Thanks for the information...
However, the NANDROID backup requires a custom recovery image, right?
I'm trying to reset everything (recovery image, boot image, data image, etc) back to factory and have the bootloader unlocked (and not say TAMPERED, etc).
Click to expand...
Click to collapse
You should use Helium aka Carbon for your backups in case you cannot root again. It don't require root.
Sent from Galaxy S 3 i747M 32gb

I need to send my dev edition back to get an exchange. I have used the RUU, to get rid of the tampered, but now it says relocked... Will that be a problem?

schn1tt3r said:
I need to send my dev edition back to get an exchange. I have used the RUU, to get rid of the tampered, but now it says relocked... Will that be a problem?
Click to expand...
Click to collapse
hey
did u manage to get back it to stock ?? without the tampered? and get it repaired by HTC? after flashing the RUU?
if so hw?
please some links
Thank You

e1forall said:
hey
did u manage to get back it to stock ?? without the tampered? and get it repaired by HTC? after flashing the RUU?
if so hw?
please some links
Thank You
Click to expand...
Click to collapse
I used command prompt Android ADB to run the RUU. Tampered label went away, but "relocked" was shown instead of "unlocked" and I sent it back just like that no problem.

schn1tt3r said:
I used command prompt Android ADB to run the RUU. Tampered label went away, but "relocked" was shown instead of "unlocked" and I sent it back just like that no problem.
Click to expand...
Click to collapse
is there no way to get back to factory state ?? still?

e1forall said:
is there no way to get back to factory state ?? still?
Click to expand...
Click to collapse
What do you mean? Its easy, HTCdev website provide the RUU file which is basically a one click solution.

schn1tt3r said:
What do you mean? Its easy, HTCdev website provide the RUU file which is basically a one click solution.
Click to expand...
Click to collapse
yeah factory state for the Dev edition i mean stock firmware . without tampered. and bootloader unlocked

e1forall said:
yeah factory state for the Dev edition i mean stock firmware . without tampered. and bootloader unlocked
Click to expand...
Click to collapse
I saved an email an HTC support guy sent me for the Developer One Edition.
The only file you need is an RUU.exe you can download from HTCdev.com click "developer" and download somewhere there. If you bought your developer edition in USA like I did, your filename should be RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe
Get that file and follow the instructions:
The easiest way to do that is to put the device into Fastboot Mode:
1. Boot the device into bootloader (Disable Fastboot, Power off device, Press + hold volume down and power on)
2. Navigate to Fastboot using the volume buttons. Select with power
3. Connect device to PC. “Fastboot” should change to say “Fastboot USB”
4. Execute the RUU (Rom Update Utility)
You can also do it using HTC Sync Manager. I will provide you with the instructions.
1. Download and install HTC Sync Manager from http://www.htc.com/www/software/htc-sync-manager/
2. Once it is installed proceed with step three.
3. Power down the phone
4. Power on the phone by holding volume down + power
5. Fastboot is already highlighted by default, tap power to go into it and plug the phone into the computer.
a. Note: If all drivers installed properly, you should see a change on the screen that says “fastboot usb” in red.
6. Run the RUU that was downloaded from the website and follow the on-screen directions.
a. Note: If done correctly, the screen on the phone will change to solid black and say “HTC” in grey letters and proceed to flash the phone
Click to expand...
Click to collapse
That should remove the "tampered" from hboot and will set your bootloader to "relocked" even though phone ships as unlocked. If you want to do this just for warranty, then you can argue the "relocked" happened from their official RUU and therefore still covered under warranty.
EDIT: There is a guide in xda stickied dont know how you did not see it: http://forum.xda-developers.com/showthread.php?t=2358738

schn1tt3r said:
I saved an email an HTC support guy sent me for the Developer One Edition.
The only file you need is an RUU.exe you can download from HTCdev.com click "developer" and download somewhere there. If you bought your developer edition in USA like I did, your filename should be RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe
Get that file and follow the instructions:
That should remove the "tampered" from hboot and will set your bootloader to "relocked" even though phone ships as unlocked. If you want to do this just for warranty, then you can argue the "relocked" happened from their official RUU and therefore still covered under warranty.
EDIT: There is a guide in xda stickied dont know how you did not see it: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
hello
i have seen the guide
I am in India
So the warranty is not covered in India for the Dev Edition
But i wanted to go stock with bootloader unlocked without tampered
so the question

[Guide?] Returning to factory from S-OFF and need to go back to stock everything.

Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.

did you use htcdev to unlock?
Sent from my 831C using Tapatalk

Zzz73 said:
did you use htcdev to unlock?
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Yes, I initially used the HTCDEV to unlock which voids the warranty. There are ways to revert from that though and that is what I am trying to accomplish by going back to stock everything.
I don't know if I need to flash the full firmware or not after I installed the stock nandroid backup from step 4).
Thank you for the reply.

oh OK. of you know a way around. i thought it registered your serial with HTC...
Sent from my 831C using Tapatalk

murf43143 said:
Is the following going to be what I need to get my phone in for warranty? Do I need to go back to S-ON or does S-OFF not void warranty if everything else is stock?
What I did:
1) Make a full TWRP backup and copy it to my HD from the phone.
2) Remove my “tampered flag” (thank you scotty1223)
3) Do a “Wipe” in TWRP.
4) Downloaded the “1.54.651.8-Stock.zip” and flashed that using TWRP (thank you Rydah805).
5) Downloaded the “Stock Recovery From 1.54.651.8 OTA" from the same thread.
6) Manually flashed the recovery.img above in fastboot using the command “fastboot flash recovery recovery.img”
7) Relock the “lock status flag” to lock my bootloader using this thread (thank you again scotty1223).
At this point I had a completely wiped system on reboot. I don’t know how but SuperSU was still on my device when I powered it back on but everything else was wiped. I then went in to SuperSU “settings” and then did the “Full unroot” to uninstall SuperSU.
Is this all I need to do to send in for warranty on my cracked screen or do I need to remove S-OFF on the bootloader also?
Thank you to all.
Click to expand...
Click to collapse
I would put it back to s-on as well.

FlowingAway said:
I would put it back to s-on as well.
Click to expand...
Click to collapse
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.

murf43143 said:
Thank you for the reply.
I was under the impression that S-OFF did not void warranty on its own and in fact I read on many of the threads I posted that they recommend not to go back to S-ON.
I need to find that out I suppose. Thanks again.
Click to expand...
Click to collapse
The only reason I say that is because I had a bad experience last year with my M7 being sent back to HTC.
If I was confident I could get s-off again when the phone cane back I would do it just to make sure it wouldn't be denied. Of course that's just me. Definitely try and find some more people's experience before you do anything.

I don't think anyone here can give you a definitive answer to your question because people have all had different experiences when it comes to HTC's warranty department. Some get denied for tampering and voiding the warranty while another customer with almost an almost identical issue breezes through without even un-rooting.....
It is very likely they have some other means of telling whether the stock firmware/software has been replaced at some point that we have no clue about. If they wanted to be hardarses about this kind of thing I'm sure they are quite capable of doing so but I do not think it is in their best interest as a company to get that kind of PR when you have Google and Motorola offering warranties (guaranteed or something like that I read somewhere?) despite tampering. 'Power users' like most of the members on XDA, are a huge market who often have multiple devices and a high level of influence with friends, relatives, coworkers etc when it comes time for their upgrades...You can see where that train of thought ends up I hope.^^
Anyway, sorry for the ranting, haha. My point is that you should take every precaution you can including going back to S-On, "Locking" the bootloader again, and ensuring your device is as exactly like it was when you first got it if you want to minimize your chances of getting denied your warranty. You can always look back on it and go, well maybe I didn't have to go through all that trouble but sure glad it got fixed! That's a much better alternative than the regret you'd have if something as simple as S-Off is to fix(or faux fix) resulted in your claim getting denied.^^
Best of luck, whatever you decide!

Htc one boot dead

hello guys, i am new here and if i open this topic wrong sector sorry me
i was trying to update my htc one Verizon fomr 5.5 Sense to 6 and as i see, i put wrong rom and not phone is stuck on htc logo, it came up and then rebooting phone, have not access to recovery mode,phone was keep restarting until battery die,and now it turn off, but if i plug it in pc htc logo comes up and keep restarting pc can not recognise phone, i took it to the technical but they can not fix it, i am living in Georgia and here is not good technician, as they said phone dead boot, and can not help to this phone, any1 know any way to wake up this phone? or i have to pull it out? ty for replay, sorry for my bad english hope u undestand what is my problem and what i want to say ,ty for replay

Install the correct recovery for the Verizon model:
http://teamw.in/project/twrp2/226
Then
fastboot erase cache
Then flash Verizon compatible ROM.

BenPope said:
Install the correct recovery for the Verizon model:
Then
fastboot erase cache
Then flash Verizon compatible ROM.
Click to expand...
Click to collapse
ty u for replay, but problem is that when i click on power and volum button i can not get in boot menu, phone just keep rebooting , there is htc logo and it starting restart so this method can not help , can not do Turn on the device and keep holding volume down until a menu shows up , all button working on phone

miwisdzvra said:
ty u for replay, but problem is that when i click on power and volum button i can not get in boot menu, phone just keep rebooting , there is htc logo and it starting restart so this method can not help , can not do Turn on the device and keep holding volume down until a menu shows up , all button working on phone
Click to expand...
Click to collapse
Keep trying to get in bootloader mode, it will work.

SaHiLzZ said:
Keep trying to get in bootloader mode, it will work.
Click to expand...
Click to collapse
i am trying but when boot menu must show up then phone is rebooting, iam looking if there is any soft using it to write boot or something like that to have access to boot menu

I have the same problem with my international HTC One. Any help would be really appreciatedq. Thanks.

Try shining a bright light on the sensor top left and hold power and volume down. there's no reason why it shouldn't go to bootloader
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
Try shining a bright light on the sensor top left and hold power and volume down. there's no reason why it shouldn't go to bootloader
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i had try it too, but nothing there is no software for this?

miwisdzvra said:
i had try it too, but nothing there is no software for this?
Click to expand...
Click to collapse
lol, what software you have to get past the bootloader first

clsA said:
lol, what software you have to get past the bootloader first
Click to expand...
Click to collapse
i dont know cos i am asking if there is any soft

miwisdzvra said:
i dont know cos i am asking if there is any soft
Click to expand...
Click to collapse
The thing is you have Verizon ... Verizon must be s-off to unlock the bootloader to flash custom recovery and roms. You say you "put wrong rom" on the phone. Do you mean a rom for a different phone (samsung - nexus ? ) or just a rom for a international HTC One ? are you still s-off ? can you post a picture of the bootloader before it reboots?

clsA said:
The thing is you have Verizon ... Verizon must be s-off to unlock the bootloader to flash custom recovery and roms. You say you "put wrong rom" on the phone. Do you mean a rom for a different phone (samsung - nexus ? ) or just a rom for a international HTC One ? are you still s-off ? can you post a picture of the bootloader before it reboots?
Click to expand...
Click to collapse
i have not access to bootloader anymore, last time when i check bootloader there was s-on
first i put costum rom ,it was for verizon htc one, but phone stuck on bootloader, and there was s-on, and "TAMPERED" "RELOCKED".i was trying to make s-off but can not do it, then i upload official rom and phone stuck on htc logo, have not acccess after last upload to bootloader

miwisdzvra said:
i have not access to bootloader anymore, last time when i check bootloader there was s-on
first i put costum rom ,it was for verizon htc one, but phone stuck on bootloader, and there was s-on, and "TAMPERED" "RELOCKED".i was trying to make s-off but can not do it, then i upload official rom and phone stuck on htc logo, have not acccess after last upload to bootloader
Click to expand...
Click to collapse
yeah your stuck in RUU mode till you get the RUU to complete.
Sorry but I'm stumped ...I have no idea what you do now
Maybe @nkk71 or @alray have some ideas

155
clsA said:
yeah your stuck in RUU mode till you get the RUU to complete.
Sorry but I'm stumped ...I have no idea what you do now
Maybe @nkk71 or @alray have some ideas
Click to expand...
Click to collapse
kk, ty u for replay

No ideas from my side:
S-On, relocked and no recovery on Verizon, only thing is a RUU.

If you can't boot in bootloader mode, there is nothing you can do.
you need to boot in bootloader to determine what ruu you need (if one available for your version)
and you also need to start the ruu from bootloader.
looks like the only solution is to send the phone for repair or maybe a JTAG repair...

k, thank guys for replay

clsA said:
The thing is you have Verizon ... Verizon must be s-off to unlock the bootloader to flash custom recovery and roms. You say you "put wrong rom" on the phone. Do you mean a rom for a different phone (samsung - nexus ? ) or just a rom for a international HTC One ? are you still s-off ? can you post a picture of the bootloader before it reboots?
Click to expand...
Click to collapse
it was htc one rom, and i think it was international HTC One rom, now i can not enter bootloader, last time when i checked it, it was s-on

[Q] Can't boot into android, or flash anything

Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)

Welcome to the club!

necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.

wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.

necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.

AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.

Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....

wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.

necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.

the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.

AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.

AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.

rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.

AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.

AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.

the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.

AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.