i mean its been 10 minutes, but still stuck on bootloop any ideas?
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
Out of date ADB can cause this. I have seen it a few times reported by other people.
Try rebooting PC then reboot phone back to boot loader and use THESE adb and fastboot apps. I copied the from the latest SDK Manager
If that does not resolve then post back
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
You should probably include a screenshot of everything you did in the command prompt... boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Good point!
Scott said:
Good point!
Click to expand...
Click to collapse
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Scott said:
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Click to expand...
Click to collapse
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Agreed! But on the same note, in the OP's defense there is not a very clear Q/A thread that tells you what you need to do. Everything is scattered. However, that is not anyones fault. This device is new to "ALL" of us. The whole SLOT thing, etc. Its all new unless you had a Google Chromebook. So I cant much blame people with issues. The good thing... 99.99% of the issues posted can be fixed with some patients. :good:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Just ignore it, it's due to the unlocked bootloader
Sent from my Pixel XL using Tapatalk
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Nothing you can do about that at this time. I am sure someone will hack the aboot or hboot, which ever on an HTC device to remove it. For now wear it as a badge of pride :highfive:
iKenta said:
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
Click to expand...
Click to collapse
Could have been. I would recommend you not install TWRP at this time. Its finicky but being worked on. I know for fact it will be great soon.
I hope @Chainfire updates his Flash Fire. Easier to use than TWRP!
Related
*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
what is your model H790 or H791
16 or 32 GB?
DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk
Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-
sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better
That thought is also roaming around my head, still Nexus is Nexus!
What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
burnface said:
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
Click to expand...
Click to collapse
Hey man, do you remember which FW built were you on ? NDE63X ?
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
milan187 said:
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
Click to expand...
Click to collapse
Cool man, thanks!
andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
burnface said:
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
Click to expand...
Click to collapse
It's all good man. My heart was pounding as I about to hit 'yes' for locking my bootloader. Did the deed and all is well =) Thanks!
just got my pixel xl today. unlocked the bootloader fine.
next step flash twrp. i fastboot boot twrp img. temp twrp , installed the zip.. i reboot to recovery. that where everything F up.. now i can not get into fastboot.. is there a way for me to get fastboot mode back ??
never mind just had to reboot the phone 3 times..
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
sytayeth said:
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
Click to expand...
Click to collapse
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
5.1 said:
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
Click to expand...
Click to collapse
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
sytayeth said:
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
Click to expand...
Click to collapse
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
5.1 said:
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
Click to expand...
Click to collapse
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
sytayeth said:
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
Click to expand...
Click to collapse
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
toknitup420 said:
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
Click to expand...
Click to collapse
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
sytayeth said:
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
Click to expand...
Click to collapse
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
toknitup420 said:
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks. I'll try.
Heyy all.. it's been awhile since I've been here and I've asked for help a few times and it seems like everytime there's something new to do in the whole updating process..
So I've read https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347 and it looks great.. The thing that's got me confused now is the chainfire bootsigner?
Is it possible to be on the latest version of Android with all the security updates n everything and still have a unlocked bootloader / root etc.. or am I still sticking with the old April 5th security patch? just making sure I get everything right so I don't brick myself etc..
looking forward to the great help I always get.
also how does the chainfire bootsigner thing work? kinda confused with it as well..
My understanding is that you don't need to be on the April security patch--just the April bootloader. You can flash May without boot looping as long as you use the April bootloader. You are right that the changing flashing instructions are confusing.
jhs39 said:
My understanding is that you don't need to be on the April security patch--just the April bootloader. You can flash May without boot looping as long as you use the April bootloader. You are right that the changing flashing instructions are confusing.
Click to expand...
Click to collapse
What about June?? 7.1.2 (NHG47N, Jun 2017, Verizon) or should I just stick with 7.1.2 (NHG47L, May 2017, Verizon)
and how do I find the April bootloader?
Dimmizer said:
What about June?? 7.1.2 (NHG47N, Jun 2017, Verizon) or should I just stick with 7.1.2 (NHG47L, May 2017, Verizon)
and how do I find the April bootloader?
Click to expand...
Click to collapse
You can find the boot loader on Google's website for the pixels factory image, the way the bootsigner works is anything past April you have to flash a bootsigner zip. Will attach a link later in an edit after you install TWRP.
If you downgraded from N you have to have the boot loader on both partitions as O ****s with it.
If you are on the Verizon variant and your boot loader is locked I'd probably suggest O beta. The Beta might be able to find a hole early. No Promise's. I will link up the post in a reply when I get home
EDIT
https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
1. download this boot signer
2. When you boot temp TWRP, flash the TWRP zip and flash the boot signer
3. Profit.
If anyone came from the android O beta please clarify to me so I can help
I agree people are jerks on the forum. I'll be happy to help when I can.
Sent from my Pixel XL using Tapatalk
Dimmizer said:
also how does the chainfire bootsigner thing work? kinda confused with it as well..
Click to expand...
Click to collapse
I'm confused about that as well. I've read that it doesn't need to be flashed anymore and also that it needs to be flashed everytime you flash anything that changes your boot image. Hopefully one of the successful Pixel XL flashers will give you a definite answer on this. The Pixel XL XDA community seems a lot less helpful than other phone communities I have encountered. People are more likely to tell you you're an idiot for not doing your own research than actually answer your question.
bennyboy2120 said:
You can find the boot loader on Google's website for the pixels factory image, the way the bootsigner works is anything past April you have to flash a bootsigner zip. Will attach a link later in an edit after you install TWRP.
If you downgraded from N you have to have the boot loader on both partitions as O ****s with it.
If you are on the Verizon variant and your boot loader is locked I'd probably suggest O beta. The Beta might be able to find a hole early. No Promise's. I will link up the post in a reply when I get home
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No I have a unlocked bootloader.. only thing I'm worried about is it becoming locked again.. if that's possible at all? I remember reading/seeing it somewhere that it is possible for the bootloader to relock itself so I just wanna make sure that doesnt happen cause well.. RIP if so lol.
Dimmizer said:
No I have a unlocked bootloader.. only thing I'm worried about is it becoming locked again.. if that's possible at all? I remember reading/seeing it somewhere that it is possible for the bootloader to relock itself so I just wanna make sure that doesnt happen cause well.. RIP if so lol.
Click to expand...
Click to collapse
Shouldn't. Look at my edit I have shorthand instructions there now
Sent from my Pixel XL using Tapatalk
Starting with May you have to install the boot signer any time you touch boot. You do it as the last step. So a kernel or root requires you to do it.
Its no big deal, just an extra zip to install while you are in TWRP. So yea, stay up to date on the security patches. Besides the security issues, some VZ phones have gone into loops silently re downloading the ota... burning a months data over night.
soo all im doing is flashing the bootsigner? I don't have to run any commands or anything like I saw in Chainfires thread? cause that's what confuses me is when I have to start doing stuff in adb n such lol
Dimmizer said:
soo all im doing is flashing the bootsigner? I don't have to run any commands or anything like I saw in Chainfires thread? cause that's what confuses me is when I have to start doing stuff in adb n such lol
Click to expand...
Click to collapse
The command to first boot twrp
Fastboot boot (twrp.img)
Is the only one needed when installing twrp
After that it's flashing
1.the twrp zip
2. The bootsigner.
Also side note Everytime you flash a room twrp goes away to be sure too install the TWRP zip after the ROM install
Sent from my LG-LS997 using Tapatalk
bennyboy2120 said:
The command to first boot twrp
Fastboot boot (twrp.img)
Is the only one needed when installing twrp
After that it's flashing
1.the twrp zip
2. The bootsigner.
Also side note Everytime you flash a room twrp goes away to be sure too install the TWRP zip after the ROM install
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
TonikJDK said:
Starting with May you have to install the boot signer any time you touch boot. You do it as the last step. So a kernel or root requires you to do it.
Its no big deal, just an extra zip to install while you are in TWRP. So yea, stay up to date on the security patches. Besides the security issues, some VZ phones have gone into loops silently re downloading the ota... burning a months data over night.
Click to expand...
Click to collapse
so I can go right to the 7.1.2 (NHG47N, Jun 2017, Verizon) image and just do what bennyboy2120 said above and it'll work or is that for the april update still?
just confirming before I start the process.
Dimmizer said:
so I can go right to the 7.1.2 (NHG47N, Jun 2017, Verizon) image and just do what bennyboy2120 said above and it'll work or is that for the april update still?
just confirming before I start the process.
Click to expand...
Click to collapse
This process is for people after April update
Sent from my LG-LS997 using Tapatalk
bennyboy2120 said:
This process is for people after April update
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
so i'll download the latest stock rom which would be 7.1.2 (NHG47N, Jun 2017, Verizon) and then just follow everything in https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347 and should be good?
Dimmizer said:
so I can go right to the 7.1.2 (NHG47N, Jun 2017, Verizon) image and just do what bennyboy2120 said above and it'll work or is that for the april update still?
just confirming before I start the process.
Click to expand...
Click to collapse
Yes, same drill for June and probably for a long time to come. I just did it that way myself.
TonikJDK said:
Yes, same drill for June and probably for a long time to come. I just did it that way myself.
Click to expand...
Click to collapse
thanks for all the help once again everyone ****in life savers seriously lol... no joke. <3
rip.. im stuck on
"No Command"
and I can't get into my Pixel now either I'm bootlooped.. ideas??
nvm think I got it??
Dimmizer said:
rip.. im stuck on
"No Command"
and I can't get into my Pixel now either I'm bootlooped.. ideas??
Click to expand...
Click to collapse
This means you still have to stock recovery on your device. To advance past this screen, while you see "no command" press and hold power and quickly tap volume up. This will allow you to enter the rest of the stock recovery.
Besides that, it sounds like you had a bad flash. try getting into fastboot and starting over.
nvm think I got it??
edit.. yep im stuck.. I can get it to where I can apply update via adb or sd card or wipe system cache n stuff but that's it... dunno what to do from here,.
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
applezen said:
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
IDK much about computers much but I learn quick and understand well what I did was set the power-tools as path I didn't do fastboot but fastboot is in the power-tools folder so is this correct?
Sent from my Pixel 2 XL using Tapatalk
Install latest SDK and start the CMD from there
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Ace0spades808 said:
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Click to expand...
Click to collapse
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Click to expand...
Click to collapse
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh ???
Sounds like the same issue as here: https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187/page6 - that's post number 51.
The user resolved it by updating ADB/Fastboot.
Badger50 said:
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh [emoji108][emoji106][emoji41]
Click to expand...
Click to collapse
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Click to expand...
Click to collapse
Hell yeah!!! ???
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Didn't mean to offend you or anything. I just wanted you to be aware that the developer preview isn't meant to be flashed because it is the "latest and greatest". If you want to try it out go for it but you could end up causing yourself more headache than it's worth (you could brick it or render your phone inoperable for days) since you yourself said you aren't sure what you are doing.
non_smoker0922 said:
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
uicnren said:
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
Click to expand...
Click to collapse
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
uicnren said:
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
Click to expand...
Click to collapse
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Click to expand...
Click to collapse
Did you run both bootloader unlocking commands?
Badger50 said:
Did you run both bootloader unlocking commands?
Click to expand...
Click to collapse
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
So the issue is that you can't get the phone unlocked? Do you still have the option to enable ""OEM Unlocking" in Developer Settings? If it is greyed out, you'll have to reset the phone. First backup and then perform "erase all data(factory reset) and then skip through all of the setup on the phone. Once you are in the phone, gain developer settings, enable "OEM Unlocking" and USB Debugging. You should then be able to unlock via fastboot.
non_smoker0922 said:
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Best I can suggest for you now, is to see HERE.
You can ignore the stuff about C:/D: drives.
Twice now you have used the term unlock_critical. Did you actually type in "fastboot flashing unlock_critical"?