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.
Related
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!
Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?
I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.
Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.
If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.
It doesn't boot to recovery. Only fastboot and edl mode work.
You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app
Thanks, but that doesn't work with a locked bootloader (already tried).
It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.
xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?
boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/
Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.
Thanks, but none of these solutions works. Already tried all of them a couple of times....
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...
The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.
Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot
Sorry, but for some reason I never saw your answer... I never found a solution either, though
how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.
Hello, my brother have a nexus 5x and one day after a night his phone stop working, it could only enter to download mode, now sometimes it cant even get there, what can i do, its been like 2 weeks since that
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
berndblb said:
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked into that, but is it normal that the phone go to a bootloader, then to download mode and after that get stuck in the google animation?
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
berndblb said:
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
Click to expand...
Click to collapse
Thank you sooo much, i will try this and the ill tell you how it end up:good:
I have a Pixel 2xl which is factory unlocked, not Verizon unlocked. In order to root it, i believe that i first have to relock the bootloader. I haven't been able to root it, and i believe that this is why. Any info to resolve this issue would be greatly appreciated. Thanks.
grunt0300 said:
I have a Pixel 2xl which is factory unlocked, not Verizon unlocked. In order to root it, i believe that i first have to relock the bootloader. I haven't been able to root it, and i believe that this is why. Any info to resolve this issue would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
No, you do not need to lock the bootloader, and wouldn't recommend it as well! You'll need to install platform-tools on your pc, the twrp.img in your platform-tools folder, the twrp installation zip and magisk on your phone. Then fastboot into twrp, swipe to allow modifications, then flash the twrp installer.zip, then flash the magisk.zip, then boot up and you should have root :good:
Badger50 said:
No, you do not need to lock the bootloader, and wouldn't recommend it as well! You'll need to install platform-tools on your pc, the twrp.img in your platform-tools folder, the twrp installation zip and magisk on your phone. Then fastboot into twrp, swipe to allow modifications, then flash the twrp installer.zip, then flash the magisk.zip, then boot up and you should have root :good:
Click to expand...
Click to collapse
I've got it set up, but how do i "fastboot into twrp"? I can get into fastboot mode, but where is twrp? Sorry, but i'm getting confused.
grunt0300 said:
I've got it set up, but how do i "fastboot into twrp"? I can get into fastboot mode, but where is twrp? Sorry, but i'm getting confused.
Click to expand...
Click to collapse
I think you would do well to read and study this guide for a little bit, then you'll have a better understanding of what to do :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Badger50 said:
I think you would do well to read and study this guide for a little bit, then you'll have a better understanding of what to do :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
grunt0300 said:
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
Click to expand...
Click to collapse
Where are you getting stuck at??
grunt0300 said:
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
Click to expand...
Click to collapse
Don't give up until you try this, I was not able to unlock my Bootloader with fastboot, but the deuces method works. :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Droid_Nut said:
Don't give up until you try this, I was not able to unlock my Bootloader with fastboot, but the deuces method works. :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
grunt0300 said:
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
Click to expand...
Click to collapse
Again, where are you getting stuck at??
Fastbooting twrp??
Phone/pc communication??
Platform-tools up to date??
Tried different 2.0 USB A to USB C cables and ports?
grunt0300 said:
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
Click to expand...
Click to collapse
The title of your thread, led me to believe you wanted to unlock the bootloader, and it was only carrier unlocked?
Actually when I rooted mine, Magisk said it was not rooted, after a reboot it was showing root? Maybe something quirky in Magisk? You may have root, but Magisk is not properly reporting it?
Badger50 said:
Again, where are you getting stuck at??
Fastbooting twrp??
Phone/pc communication??
Platform-tools up to date??
Tried different 2.0 USB A to USB C cables and ports?
Click to expand...
Click to collapse
Not stuck any more. Locked the bootloader, and i'm done. No root, no worries. Maybe someday, in a galaxy far, far away, i'll try again. For now, i'll stay unrooted and keep my sanity. Thanks for trying to help.
grunt0300 said:
Not stuck any more. Locked the bootloader, and i'm done. No root, no worries. Maybe someday, in a galaxy far, far away, i'll try again. For now, i'll stay unrooted and keep my sanity. Thanks for trying to help.
Click to expand...
Click to collapse
Happy trails then my friend. However, if your feeling adventurous in the future, look me up. Bet we could get that sucker rooted! :good::laugh:
Locked my boatloader by mistake now it won't boots I need help ASAP.... I'm losing my mind over here I need someone to help me please for the love of God somebody... Just bought this phone for like $1,000 and now I'm looking at a ****ing brick......
no worries, you technically cant brick it that easily.
Check the MSM thread for your exact model and follow the steps get it back and running again.
^ Yeah an MSM flash will have you right as rain. Just wondering how the you locked the bootloader "by mistake" that seems like a difficult mistake to make.
was trying to restore and forgot how op works lol...i got it fixed now. while your here, how can i flash twrp and flash a rom? having issues with this now..
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
So I'm not sure about YOUR phone, if you have a recovery partition you can just flash recovery, if you don't have a recovery partition then you need to fastboot boot twrp first. And there are a few ways to flash a rom, my recommendation would be Fastboot Enhance I personally haven't tried it yet but it seems to work pretty good and even though it's in the 8T category it should work fine. Now one thing that is noteworthy with Fastboot enhance though is that it flashes the current slot instead of the inactive slot.
this.guy.lol said:
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
Click to expand...
Click to collapse
Didn't reply accidently, not the first time I've done that. Read my previous post.
Brandon.Bissonnette said:
Didn't reply accidently, not the first time I've done that. Read my previous post.
Click to expand...
Click to collapse
thx man