Hi. Would it be possible to relock the bootloader somehow?
Or remove the warning before booting?
I tried the stock images.. but it seems to need a signed boot.img
fattymcdirty said:
Hi. Would it be possible to relock the bootloader somehow?
Or remove the warning before booting?
I tried the stock images.. but it seems to need a signed boot.img
Click to expand...
Click to collapse
"fastboot oem lock" and you're good to go.
Sent from my Moto Z2 Play using Tapatalk
m0yP said:
"fastboot oem lock" and you're good to go.
Sent from my Moto Z2 Play using Tapatalk
Click to expand...
Click to collapse
nope. definitely not. you need a signed boot.img from motorola for this. bootloader locking isn't allowed without it...
fattymcdirty said:
nope. definitely not. you need a signed boot.img from motorola for this. bootloader locking isn't allowed without it...
Click to expand...
Click to collapse
Well, you must be fully stock before locking BL.
Or you could wait for a custom logo to be uploaded.
I haven't rooted my Albus because of the apparently zero development in XDA, hopefully this changes soon.
Sent from my Moto Z2 Play using Tapatalk
i am fully stock. except the root. and since magisk alters boot.img, it's not working. you need a signed boot.img from motorola..
Why do you wish to relock already?
to sell the phone...
fattymcdirty said:
to sell the phone...
Click to expand...
Click to collapse
Don't sell it rooted, then. Just flash stock and you're done.
Warranty is void anyway, though.
Sent from my Moto Z2 Play using Tapatalk
fattymcdirty said:
to sell the phone...
Click to expand...
Click to collapse
What version is it?
How much do you want for it?
pizza_pablo said:
What version is it?
How much do you want for it?
Click to expand...
Click to collapse
xt1710-09.
300eur icl. JBL speaker. but I live in germany
m0yP said:
fattymcdirty said:
nope. definitely not. you need a signed boot.img from motorola for this. bootloader locking isn't allowed without it...
Click to expand...
Click to collapse
Well, you must be fully stock before locking BL.
Click to expand...
Click to collapse
Oh, wait. Are you saying, if you are fully stock, you should be able to relock the bootloader?
I initially unlocked the bootloader, put on TWRP and rooted, but since no development was going on, I went back to "stock", using the images Junior Passos has posted. I'm now receiving OTA updates fine, but obviously can't use Android Pay because my bootloader is unlocked.
TravellingGuy said:
Oh, wait. Are you saying, if you are fully stock, you should be able to relock the bootloader?
I initially unlocked the bootloader, put on TWRP and rooted, but since no development was going on, I went back to "stock", using the images Junior Passos has posted. I'm now receiving OTA updates fine, but obviously can't use Android Pay because my bootloader is unlocked.
Click to expand...
Click to collapse
Yes, just "fastboot oem lock" and profit!
Warranty is still voided, though.
m0yP said:
Yes, just "fastboot oem lock" and profit!
Warranty is still voided, though.
Click to expand...
Click to collapse
Sorry. Still definitely NOT possible. When flashing back to stock, you're NOT able to flash the boot.img, because it's not signed.
Without a proper signed boot.img, the command fastboot oem lock gives you an error, saying that boot.img isn''t valid/properly signed.
fattymcdirty said:
Sorry. Still definitely NOT possible. When flashing back to stock, you're NOT able to flash the boot.img, because it's not signed.
Without a proper signed boot.img, the command fastboot oem lock gives you an error, saying that boot.img isn''t valid/properly signed.
Click to expand...
Click to collapse
Need to be fully stock for this to work. You're still rooted, so no locked BL for you.
Sent from my Moto Z2 Play using Tapatalk
You don't seem to understand what's the problem here: you can NOT go back to FULL stock because you can NOT flash an untouched boot.img, because there DOES NO SIGNED version exist!!!
IF you say it would be possible, please kindly describe ALL the steps to do so!
fattymcdirty said:
IF you say it would be possible, please kindly describe ALL the steps to do so!
Click to expand...
Click to collapse
Did you try Motorola Firmware Team's or Lolinet's files?
Sent from my Moto Z2 Play using Tapatalk
Why questioning a question? I tried both. But since NONE of them are signed, it's not working.. as I said several times before..
See:
C:\adb>mfastboot flash partition gpt.bin
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
Validating 'gpt.default.xml'
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.076s
Re-Locking the Bootloader is easy, only need stock rom..
Related
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Can you boot into bootloader mode what so ever?
Yes only into bootloader. Can't unlock again though. Won't let me.
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
Only can get into bootloader but cannot unlock again. Everything else is gone.
jdubya45 said:
Yes only into bootloader. Can't unlock again though. Won't let me.
Click to expand...
Click to collapse
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
stevew84 said:
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
Click to expand...
Click to collapse
Yes. Fails. Remote fail and not allowed.
jdubya45 said:
Yes. Fails. Remote fail and not allowed.
Click to expand...
Click to collapse
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
stevew84 said:
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
Click to expand...
Click to collapse
I am not sure. I think I need Unlocked bootloader.
Actually i think you just need to reunlock using depixel8. That should unlock your bootloader and allow you to flash new firmware
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Marghost said:
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
You have to be booted in Android for dePixel8 to work.
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
MArtyChubbs said:
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
He said that he tried to unlock the bootloader again and it won't let him. With a locked bootloader, you can't flash the system images.
Sent from my Pixel XL using XDA-Developers mobile app
Moderator warning,
I have cleaned this thread. XDA does not allow users to discuss fraud on this site.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
My mind is blown on how you accomplished this. Did you ERASE the partitions and then plan on flashing stock ones yourself? Why not just run the script (flash-all.bat) that would have automatically done the ENTIRE process for you, except re-locking the bootloader?
If all you did was re-lock the bootloader, it should have done a factory reset on the next boot and used the existing system partition. If you erased the system partition and then re-locked the bootloader, you are almost certainly screwed and had better hope Google has some mercy to let you RMA the phone.
Couple options you could try off the top of my head. The pixel has A/B patitions try adb sideloading an update zip to get it to switch to the backup partition that might still be there.
You could also try downloading the Factory images and extracting the system and go into fastboot and type
Code:
fastboot boot system system.img
and see if that works. Then if it boots on the temp image run deadpixel8 or whatever its called and reflash the stock image with the flash-all.bat.
have the same problem on my pixel after accidentally relocking after root before flashing back to stock.
Does anyone have the stock pixel xl recovery.img? I thinking if I boot into recovery "fast boot boot recovery.img" then I can add side load etc the ota from google.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Insert BRICK emoji here
Atlantian said:
Insert BRICK emoji here
Click to expand...
Click to collapse
I've unlocked my bootloader but now each time i try to use the bootloader it won't do anything !! it keeps showing me FAILED (remote: unknown command) ! does anyone facing the same problem ? because i cannot even stock flash my phone !
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Dielahn said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Click to expand...
Click to collapse
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Did you unlock critical?
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
murphyjasonc said:
Did you unlock critical?
Click to expand...
Click to collapse
No and everytime i try to do that it keeps telling me the same error
Dielahn said:
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
Click to expand...
Click to collapse
i downloaded the latest version
Khalid_am said:
i downloaded the latest version
Click to expand...
Click to collapse
Can you explain exact steps you are taking so we can help you better?
Dielahn said:
Can you explain exact steps you are taking so we can help you better?
Click to expand...
Click to collapse
I downloaded the platform-tools and started the cmd from the platform folder then each time i try to flash anything or interact with the bootloader it just keeps showing me this message (FAILED (remote: unknown command)
Hi to all!
my question is the following: if I unlock the bootloader, only start the custom recovery without flash it, flash magisk, and then re-lock the bootloader, i can have some problems?
Yes. It checks for non-stock data and it wipes the device upon relock. You may end up with a brick if you try to relock with non-stock software.
Gafanhotz said:
Yes. It checks for non-stock data and it wipes the device upon relock. You may end up with a brick if you try to relock with non-stock software.
Click to expand...
Click to collapse
But I'm not going to change the system, magisk does not change the system, or am I wrong?
CarloHD said:
But I'm not going to change the system, magisk does not change the system, or am I wrong?
Click to expand...
Click to collapse
A locked bootloader will not boot a device that has a different signature from the stock one with any partition other than cache or userdata. Since Magisk has to change the boot image it has a different checksum than the stock because only OnePlus can resign an image with their signature.
On another note why do you need the bootloader to be locked? The only difference I can think for would be warranty but if you're that worried it wouldn't be worth it in the first place.
bullet25 said:
A locked bootloader will not boot a device that has a different signature from the stock one with any partition other than cache or userdata. Since Magisk has to change the boot image it has a different checksum than the stock because only OnePlus can resign an image with their signature.
On another note why do you need the bootloader to be locked? The only difference I can think for would be warranty but if you're that worried it wouldn't be worth it in the first place.
Click to expand...
Click to collapse
Actually the reason why I would like to lock the bootloader is to avoid the unlocked bootloader warning screen
CarloHD said:
Actually the reason why I would like to lock the bootloader is to avoid the unlocked bootloader warning screen
Click to expand...
Click to collapse
It's an extra 5 seconds. Learn to deal with it
You can sign images yourself:
Re-locking Bootloader w/ Custom OS
Do this wrong and you will have a bad day..., its easier to live with it. On some devices they have managed to change that image, but not eliminate it.
bullet25 said:
A locked bootloader will not boot a device that has a different signature from the stock one with any partition other than cache or userdata. Since Magisk has to change the boot image it has a different checksum than the stock because only OnePlus can resign an image with their signature.
On another note why do you need the bootloader to be locked? The only difference I can think for would be warranty but if you're that worried it wouldn't be worth it in the first place.
Click to expand...
Click to collapse
c_86 said:
It's an extra 5 seconds. Learn to deal with it
Click to expand...
Click to collapse
It also compromises SECURITY
PHANX0M said:
It also compromises SECURITY
Click to expand...
Click to collapse
why would u root then??????
Hey guys, I just recently got a Google pixel XL.
I played around for a few days a then decided to go back to factory image ....stock everything. Using ADB platform-tools did a flash-all.bat then relocked the bootloader
Now I'm good to go....so I thought. it cant complete the first security update. It says "unable to complete installation”. Any help will be much appreciated.
Have you tried to ADB it back to stock? That's how I do it
yeah my bad.......i wrote TWRP I was meaning ADB platform-tools. But yes I returned to a stock image. I really don't know what to do.
killermankrew said:
Hey guys, I just recently got a Google pixel XL.
I played around for a few days a then decided to go back to factory image ....stock everything. Using ADB platform-tools did a flash-all.bat then relocked the bootloader
Now I'm good to go....so I thought. it cant complete the first security update. It says "unable to complete installation”. Any help will be much appreciated.
Click to expand...
Click to collapse
When you did the flash-all was the -w in the flash-all.bat file?
No w or. -w. Would that matter? I guessing so since you mentioned it. Please elaborate
By
I rooted the phone using TWRP and magjic. <misspelled. Then tried a custom kernel. Something went wrong....had bootloop. So I flashed-all.bat.
I then did a factory reset. .
I think I'ma have to redo everything with all new file downloads(images) and reinstall platform tool too.
Oh also relocked the bootloader.
Be sure to unlock again before messing with anything else.
Sent from my Pixel XL using Tapatalk
killermankrew said:
No w or. -w. Would that matter? I guessing so since you mentioned it. Please elaborate
Click to expand...
Click to collapse
This line in the flash-all.bat file has the -w:
fastboot -w update image-marlin-PQ3A.190605.003.zip
The -w in the flash-all, will erase all data (factory reset).
If you remove the -w from the flash-all, your data and the internal storage are not wiped.
When relocking the bootloader it is, extremely, important the the phone be 100 present stock before relocking it.
Some, have bricked their phone because they relocked the bootloader without returning the phone to stock [No root (magic), Custom ROM or Custom Kernel].
A Factory reset or flash-all with the -w ensures the phone is 'out of the box' stock.
This guide might help: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
It obvious it's not back to 100% stock. I scared now to try and re unlock the bootloader. I don't know what to do.
Is there a chance I could unlock it again without ?
killermankrew said:
It obvious it's not back to 100% stock. I scared now to try and re unlock the bootloader. I don't know what to do.
Is there a chance I could unlock it again without ?
Click to expand...
Click to collapse
I do not know.
Good news I unlocked the bootloader without a problem.
But that's all now I need or want to reroot and get the latest updates. I know there are tutorials on this site or links to other sites. In your opinion which would you prefer?
killermankrew said:
Good news I unlocked the bootloader without a problem.
But that's all now I need or want to reroot and get the latest updates. I know there are tutorials on this site or links to other sites. In your opinion which would you prefer?
Click to expand...
Click to collapse
Is Settings ==> System ==> Advance ==> Developer options ==> OEM unlocking: Allow bootloader to be unlocked on? If yes do #4 'wipe data' to return your phone to 'out of the box' stock condition with the latest factory image. Then do #7 or #8 to root/reroot.
ok....i downloaded all new files and reinstalled adb fastboot.
ive unlocked the bootloader, its in debugging mode, but when i do a flash-all.bat this is what i get.
[FONT="Arial Black"C:\Users\Administrator>"C:\Android fast adb\platform-tools\marlin-pq3a.190605.003\flash-all.bat"
fastboot: error: cannot load 'bootloader-marlin-8996-012001-1904111134.img': No such file or directory
rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.018s
fastboot: error: cannot load 'radio-marlin-8996-130281-1903110834.img': No such file or directory
rebooting into bootloader OKAY [ 0.010s]
Finished. Total time: 0.011s
W/ziparchive( 6416): Unable to open 'image-marlin-pq3a.190605.003.zip': No such file or directory
fastboot: error: failed to open zip file 'image-marlin-pq3a.190605.003.zip': I/O error
Press any key to exit...][/FONT]
HELP
Last post on this thread. I was able to flash-all.bat using powershell only. i coundn't get command-line to work no matter what.
so im up to date now time to root!
Glad to read that.
killermankrew said:
Last post on this thread. I was able to flash-all.bat using powershell only. i coundn't get command-line to work no matter what.
so im up to date now time to root!
Click to expand...
Click to collapse
Good job