Database Users

Nexus 6P on boot loop after an OTA update

Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?

.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.

Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!

.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.

Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.

.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.

Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!

.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.

So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.

Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.

I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?

bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?

I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.

TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.

Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.

This happened to my wife's phone, sent back to Bell. Will see what happens.

TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?

You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.

bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?

TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.

P9 Lite Update released today (Question)

My question is simple, if i update im gonna lost my root and my custom recovery?

xCoNDex said:
My question is simple, if i update im gonna lost my root and my custom recovery?
Click to expand...
Click to collapse
Which Model have u got? Also i think u might lose ur root and custom recovery by updating.

Usama707 said:
Which Model have u got? Also i think u might lose ur root and custom recovery by updating.
Click to expand...
Click to collapse
VNS-L31, if im gonna lost all my data again repeating the root process i prefer to stay at this version

xCoNDex said:
My question is simple, if i update im gonna lost my root and my custom recovery?
Click to expand...
Click to collapse
I've successfully installed b131 update on my vns-l31 with twrp, and yes, I've lost both twrp and root. But this ca be easily redone because you still have bootloader unlocked. And your data is safe

lzimbrea said:
I've successfully installed b131 update on my vns-l31 with twrp, and yes, I've lost both twrp and root. But this ca be easily redone because you still have bootloader unlocked. And your data is safe
Click to expand...
Click to collapse
Thats nice!, and how about the update?, it is noticeable improvement?

xCoNDex said:
Thats nice!, and how about the update?, it is noticeable improvement?
Click to expand...
Click to collapse
Update changelog doesn't provide many information...
Just some carrier specific things and some system security improvement.
I didn't notice any differences in UI or overall performance.
But anyway my device run smoothly from day one.
What update you received? B131? Or other?

lzimbrea said:
Update changelog doesn't provide many information...
Just some carrier specific things and some system security improvement.
I didn't notice any differences in UI or overall performance.
But anyway my device run smoothly from day one.
What update you received? B131? Or other?
Click to expand...
Click to collapse
B131? , my update says B120
Log: System improvements and visual improvements on the ui text

xCoNDex said:
B131? , my update says B120
Log: System improvements and visual improvements on the ui text
Click to expand...
Click to collapse
Yes b131
Also i think that is is completely software since the update.app from the zip has 2.9 Gb

Please, could someone do this before update?
http://forum.xda-developers.com/mate-7/general/how-to-hicould-stock-firmware-link-ota-t3395467
Thanks

Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yeah, i have root and twrp and i receive a notification update to B120 version yesterday

Guys can someone tell me how HiVoice works?, i dont have any config menu, just the fast calls
BTW the option "Im Here" to find your phone?, could be possible to use it on p9 lite?

lzimbrea said:
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update
Click to expand...
Click to collapse
Thanks for the info.. I'm not worried about bricking it had lots of experience undoing my tinkering..lol and no update out for the middle east region.. though I do find my phone to be quite funny it has all the languages but for locations it covers the US and all of Africa and a few islands thats it..lol

Anyone knowes if is possible to change the system font?
lzimbrea said:
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update
Click to expand...
Click to collapse
how you perform the update?, the automatic process dont work for me

xCoNDex said:
Anyone knowes if is possible to change the system font?
how you perform the update?, the automatic process dont work for me
Click to expand...
Click to collapse
I performed update process automatically, just press install after download has finished.
After some checking device rebooted in twrp and after some installation in twrp ( modem.img and things like this. I don't pay attention to device ), device rebooted second time, this time in stock recovery and finished the installing process.
But as far as I know even the dload method is safe. Your data partition is safe. As long as you update.app is from an update.zip , not from a stock full rom.
Update: I checked received package and didn't see any format or erase command on /data partition
It should be safe to flash even with dload method

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yeah, you still getting update notifications

lzimbrea said:
I performed update process automatically, just press install after download has finished.
After some checking device rebooted in twrp and after some installation in twrp ( modem.img and things like this. I don't pay attention to device ), device rebooted second time, this time in stock recovery and finished the installing process.
But as far as I know even the dload method is safe. Your data partition is safe. As long as you update.app is from an update.zip , not from a stock full rom.
Update: I checked received package and didn't see any format or erase command on /data partition
It should be safe to flash even with dload method
Click to expand...
Click to collapse
Dude i recently update succesfull to B120 and my bootloader gets locked again!, is this normal?
I had to upgrade from Stock recovery, twrp Was not doing anyhting (The phone reboot, twrp stars automatic but dont do anything), now i have to unlock boot loader again wich means format all my data again

xCoNDex said:
Dude i recently update succesfull to B120 and my bootloader gets locked again!, is this normal?
I had to upgrade from Stock recovery, twrp Was not doing anyhting (The phone reboot, twrp stars automatic but dont do anything), now i have to unlock boot loader again wich means format all my data again
Click to expand...
Click to collapse
Probably you're update had a bootloader update also...
My bootloader is still unlocked after update.
I really don't know what contain all updates.
And be aware that any rooted device can get bricked by official updates. So if you need your data partition, you have 2 options
1- stay with stock software and receive updates officially
2- experiment what you want with your device, but do a backup first or prepare yourself for data loss
I had a lot of luck with this update. Is first time when this happens to me

how to remove bootloader unlocked warning

Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds ?

romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.

awsomjgp said:
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.
Click to expand...
Click to collapse
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?

romeoh said:
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?
Click to expand...
Click to collapse
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.

lafester said:
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.
Click to expand...
Click to collapse
Tbh I don't have the courage to try it that's why I'm asking may be one of our good developers knows the right way to do it ?

Saw this in post #496 of Full Updates / Back to Stock Files via TWRP
.......[snip] ......
"EDIT : managed to work fastboot and get rid of the bootscreen as in attachment :
Just refollow the steps in this guide to unlock bootloader (even if you think/thought you were unlocked (you are but has to be 'rewritten"), just do it again to flash the proper aboot...)
https://forum.xda-developers.com/axo...flash-t3517379
I had permission denied in 8) so i retried in twrp recovery.
All went fine.
And also the annoying boot screen ("that your device is corrupted due to unlock state...") is GONE too...."

I actually find the unlocked bootloader convenient. Rather than try to remember which buttons to press to get into recovery/fastboot, I can just do it from that screen so long as one of the volume buttons is depressed during the first 5 seconds of booting. I don't find it intrusive or bothersome at all.
If yours is taking 20 seconds to start booting then there is some other problem. It should start within ~5 seconds.

romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
u can give me the method for unlock bootloader for 7.1.1

mr.mgmg said:
u can give me the method for unlock bootloader for 7.1.1
Click to expand...
Click to collapse
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25

romeoh said:
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25
Click to expand...
Click to collapse
thanks for help
but im a fried if this method brick my phone

A few questions for rooted Sprint users

I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!

williamvito said:
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method

me2151 said:
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
Click to expand...
Click to collapse
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
Click to expand...
Click to collapse
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?

williamvito said:
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
Click to expand...
Click to collapse
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
You're the man, thanks for the quick reply! I will give this another go tomorrow.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?

williamvito said:
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
Click to expand...
Click to collapse
Once youve started the dirtysanta method it installs a new bootloader. you can access bootloader(fastboot) by holding VOL- and plugging iin the phone when powered off

Galaxy S5 Downgrade Failed (Verizon Screen)

Hey guys,
I updated to Marshmellow from NI2, under the assumption that if I manually flashed, I'd be able to downgrade.
I then tried to downgrade, anndd am stuck on the red Verizon screen. I then tried to re-flash back up to Marshmellow (using the same rom that I flashed to upgrade) and am still stuck on the red Verizon screen.
I don't have safestrap or anything (I did, but apparently flashing Marshmellow removed any and all backup/restore software I had, which I also didn't know).
I did a lot of googling around and this looks like a common issue, but there is no "accepted" solution and almost all links to download what people recommend trying are removed/deleted. Is there any way to get this device functional again? I don't care about what version, I just would like the device to be functional again.
Thanks for any help!

Velero said:
Is there any way to get this device functional again? I don't care about what version, I just would like the device to be functional again.
Click to expand...
Click to collapse
1. After flashing MM you still can downgrade but you're limited to BOK3 and above.
2. If you've downgraded the firmware with Odin, you need to boot recovery and perform a factory reset. It will erase all user data but the older firmware may not boot with data from a newer firmware.
3. The first boot after factory reset usually takes 12-15 min. so you need to look at the Verizon Screen patiently. But it never takes more than 20 min.

bbsc said:
1. After flashing MM you still can downgrade but you're limited to BOK3 and above.
2. If you've downgraded the firmware with Odin, you need to boot recovery and perform a factory reset. It will erase all user data but the older firmware may not boot with data from a newer firmware.
3. The first boot after factory reset usually takes 12-15 min. so you need to look at the Verizon Screen patiently. But it never takes more than 20 min.
Click to expand...
Click to collapse
EDIT: I managed to factory reset. We'll see if it'll boot properly now.
EDIT2: Okay, the phone is back to functional, but still on 6.0.1
So is there any way for me to root at this point? If I downgrade to BOK3 is there a root method available? Or am I stuck with a non-rootable phone now?

Velero said:
So is there any way for me to root at this point? If I downgrade to BOK3 is there a root method available? Or am I stuck with a non-rootable phone now?
Click to expand...
Click to collapse
1. No. Not at this point, at least.
2. Yes, BOK3 and BPB1 are LP and they are rootable.
It's said many times already.
Here is a good thread with many things explained about G900V.