Related
Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
quicksilver53 said:
Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
Click to expand...
Click to collapse
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Yes. When I have it in bootloader mode, it had changed from locked to unlocked. Thanks for your help.
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
redpoint73 said:
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
Click to expand...
Click to collapse
That's right. When he said thanks, I thought he figured it out.
Sent from my Carbon-ize Evita using xda-developers app
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
redpoint73 said:
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
Click to expand...
Click to collapse
I am fairly certain that is correct. An RUU won't run with a bootloader unlocked unless you are S-OFF and still would not relock. nothing else would touch the bootloader.
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
quicksilver53 said:
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well i can help you, i recommend going with twrp and flashing a SU zip file. this post is reserved, and will be back to edit...
Edit; Ok, so in this post is two files you need.
http://forum.xda-developers.com/attachment.php?attachmentid=1907931&d=1366808637
and http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Download both of these files.
Put UPDATE-SuperSU-v1.04.zip on the root on your SD card (basically transfer the zip to your phone)
I downloaded the 2.3.3 twrp img file, since that is the most stable for me. If you want to upgrade to 2.5, then be my guess, but others say it is a problem. i have flashed sense roms and aosp roms with no problems. also, pleae read both paragraphs before attempting to do something. if you do not understand, feel free to comment or pm me. i tried to make it as simple as possible.
So first off download the zip, and extract the folder to a simple location (desktop or c:\). i am going to assume you extracted it to c:\. open up a command prompt by going to Start and typing in "cmd" a black window should pop up. type in "cd c:\rootphone." you are already rooted, but it was already the name of my folder. anywho, turn your phone completely off, and go into the bootloader. i assume you know how to do this, since you were able to read off your hboot details. it is the white screen with colorful text. then select fastboot in red. once a usb connection is plugged in, it should turn to fastboot usb. now in the command prompt (black window on the pc), you need to type fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img (hint: you can type open and hit tab, and it will finish it for you). now you have twrp installed. now boot into recovery, and go tap on Install. find the UPDATE-SuperSU-v1.04.zip, tap it, and then slide to flash. your if successful, your phone should be rooted. go ahead hit reboot, and re-run root checker.
To anyone else (i.e. Venomtester or exad) if i have incorrect info, please let me know
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Venomtester said:
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I write guides, I write with assumptions. But I guess you are right.
Sent from my Carbon-ize Evita using xda-developers app
Thanks a lot for the info guys. I will have another go at it when I get home from work tonight.
Sent from my Nexus 4 using xda app-developers app
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Venomtester said:
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
quicksilver53 said:
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
Click to expand...
Click to collapse
Ok I got it into bootloader mode. I forgot to let go of the power buton when the screen went black.
OK just re do it again. Hold down power and volume down (or is it up? I get this confused with Samsung sometimes)
Sent from my Carbon-ize Evita using xda-developers app
Down...
Sent from my HTC One X using xda app-developers app
31ken31 said:
Down...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks. Figured that.
Sent from my Carbon-ize Evita using xda-developers app
Hi all.
Can anyone lend a hand to help me get my phone rooted again? I had originally rooted it when it first turned up, by using the guide on these forums. Since then I (stupidly) did the OTA upgrade not thinking about losing root. I went from 33r to 38r. The first I knew was when Titanium back up wouldn't back up.
My problem is that neither of my computers (desktop - XP) (Laptop - Windows 7) will now see my phone. They will both make a sound when connecting via the USB cable but neither of them show the phone via My Computer. I've un-installed/installed the drivers again and I have tried putting the phone in Fastboot and clicking on Unlock Bootloader, via the Toolbox V3, but the phone will only "reboot" to the home screen. I'm needing a bit of help from someone who knows what they are doing
Thanks in advance for any help... Foz
Once you unlock the bootloader, I don't think you need to unlock it again. If you lose root after an OTA, I think all you need to do is reflash superuser from recovery. And don't touch those toolboxes. They don't help you learn to solve these problems by yourself.
Sent from my A0001 using XDA Free mobile app
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
OKay
reboot system, back to my normal settings/homescreen.
I have SuperSu on my phone BUT get the warning that no binary is installed and I need to re root, hencmy posting here.
adamfoz said:
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
Click to expand...
Click to collapse
If re-downloading the zip doesn't work you should try a newer SuperSU version.
meekrawb said:
If re-downloading the zip doesn't work you should try a newer SuperSU version.
Click to expand...
Click to collapse
I believe I have the latest version from the play store ( 2.14).
adamfoz said:
I believe I have the latest version from the play store ( 2.14).
Click to expand...
Click to collapse
Should have clarified, you should try a newer version of the zip.
download.chainfire.eu/supersu
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
adamfoz said:
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
Click to expand...
Click to collapse
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
sparkdroid said:
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
Click to expand...
Click to collapse
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
adamfoz said:
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
no flash twrp or any custom recovery in adb and then you can flash the root zip.
I'm following this guide for rooting http://forum.xda-developers.com/showthread.php?t=2788632 .
I'm assuming that I'm doing things ok to a point, as the CMD prompt is saying adb version is 1.0.32 but when i put the phone in fast boot, and type "fastboot devices" the phone will show up in the cmd prompt. Its when I "fastboot oem unlock" and"fastboot reboot", the phone will reboot as normal. No setting up of the phone. All my apps and settings are still there, indicating to me that something is wrong :/
I'm assuming that my drivers are ok otherwise I wouldn't be seeing the above in the cmd prompts but...
Can someone tell me if my mobile should show up in "my computer" ? it has in the past, but no longer does. and I'm wondering if this could have someing to do with my problems??
Thanks again..Foz
If your rooted, you have already unlocked the boot loader unless you relocked it. Did you? If not don't worry about unlock and flash custom recovery and flash supersu zip
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
adamfoz said:
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
All you need to do is flash SuperSU again. It's normal to lose root during an OTA update.
EDIT: didn't read properly. Have you gotten TWRP to flash yet?
Transmitted via Bacon
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
adamfoz said:
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
timmaaa said:
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
Click to expand...
Click to collapse
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
adamfoz said:
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader shouldn't lock again unless you do it yourself. The recovery (unnecessarily because you can uncheck the 'update cm recovery' option in Developer Options to keep your custom recovery) and root (no way around it) are lost during the OTA but the bootloader should remain unlocked. What response do you get when issuing the following command?
Code:
fastboot oem device-info
Please paste the results here.
Transmitted via Bacon
As soon as I'm home, I'll let you know.....
Thanks
Sent from my A0001 using XDA Free mobile app
Is there any way to root without using a pc like I did with my G3 using Stumproot?
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
SpitFire727 said:
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
Click to expand...
Click to collapse
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
SpitFire727 said:
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
i removed a bunch of bloatware. mostly sprint junk
SpitFire727 said:
i removed a bunch of bloatware. mostly sprint junk
Click to expand...
Click to collapse
Then an OTA may fail, depending on what the update script checks for. I would flash back to pure stock to be safe.
Sent from my Motorola XT1575 using XDA Labs
i don't have a pre rooted backup :/
SpitFire727 said:
i don't have a pre rooted backup :/
Click to expand...
Click to collapse
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
could you walk me through all the steps i need too take?
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
moving discussion to Q&A..
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so i did all the steps, i updated too 6.1. but now i face a new problem, no devices are found in adb when in boot loader mode. it is detected while the phone is started up though.. in the progress of trying too fix this.
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
SpitFire727 said:
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
Click to expand...
Click to collapse
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
acejavelin said:
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
Click to expand...
Click to collapse
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
SpitFire727 said:
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
Click to expand...
Click to collapse
The TWRP img file needs to be on the computer in the fastboot directory. Start the bootloader and type 'fastboot devices' to make sure the device is recognized, then 'fastboot boot twrp.img' (remember to use the actual filename in place of twrp.img)
Sent from my Motorola XT1575 using XDA Labs
Can the Pixel 3 be rooted? I see the boot loader can be unlocked.
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Can the Pixel 3 be rooted? I see the boot loader can be unlocked.
Click to expand...
Click to collapse
You'll have to wait and see. It seems that @topjohnwu, the creator of magisk, gets his P3 today. So we'll see what he comes up with :good:
Has anyone been able to flash individual partitions, such as boot? I've tried and don't remember the exact error but it was something to the effect that the partition doesn't exist.
Sent from my [device_name] using XDA-Developers Legacy app
Wait, so the bootloader CAN be unlocked?
k.s.deviate said:
Wait, so the bootloader CAN be unlocked?
Click to expand...
Click to collapse
On the google version it can.
Badger50 said:
On the google version it can.
Click to expand...
Click to collapse
Ok, until an RMA is needed.
k.s.deviate said:
Ok, until an RMA is needed.
Click to expand...
Click to collapse
Google doesn't care if the bootloader is unlocked. So no worries there. But if you can't flash partitions it makes me nervous doing anything with the phone.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Google doesn't care if the bootloader is unlocked. So no worries there. But if you can't flash partitions it makes me nervous doing anything with the phone.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, I know that. I meant wait until you get a device back on an RMA and find out it's refurbished. Will not be able to unlock the bootloader... Just like the pixel 2.
k.s.deviate said:
No, I know that. I meant wait until you get a device back on an RMA and find out it's refurbished. Will not be able to unlock the bootloader... Just like the pixel 2.
Click to expand...
Click to collapse
You can unlock bootloader on Pixel 2 and on Pixel 3
Sent from my [device_name] using XDA-Developers Legacy app
Curious.. is the Verizon bootloader locked again this time? Wondering if I can pick one up at Best Buy or if I'll have to order from the Google Store.
EDIT - Nm. Per other threads, Verizon is locked down again.
gvsukids said:
You can unlock bootloader on Pixel 2 and on Pixel 3
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763
Yes it is possible
https://twitter.com/topjohnwu/status/1053488124389720064
topjohnwu got magisk working on Pixel 3
I'm rooted! Thanks to @topjohnwu
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm rooted! Thanks to @topjohnwu
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
how'd you obtain root? I tried canary build this morning and still get bootloops. github looks like its still "down" https://status.github.com/messages
k.s.deviate said:
Wait, so the bootloader CAN be unlocked?
Click to expand...
Click to collapse
Yeah, the usual way for a google device. fastboot flashing unlock. You'll need the beta version of Magisk to root, I used v17.4. I did need to flash the patched boot image to both boot partitions.
jd1639 said:
Yeah, the usual way for a google device. fastboot flashing unlock. You'll need the beta version of Magisk to root, I used v17.4. I did need to flash the patched boot image to both boot partitions.
Click to expand...
Click to collapse
beta is showing as 17.2 for me, im going to try canary with the OTA boot.img
marc.ientilucci said:
beta is showing as 17.2 for me, im going to try canary with the OTA boot.img
Click to expand...
Click to collapse
Use this URL for the custom URL in Magisk, https://bit.ly/2N8UVlq That'll get you to the latest beta.
jd1639 said:
Use this URL for the custom URL in Magisk, https://bit.ly/2N8UVlq That'll get you to the latest beta.
Click to expand...
Click to collapse
using the canary build worked. i removed magisk manager, reinstalled it, used the boot.img from the factory image and all went well.
Please help.. I am stuck with no valid slot to boot and wont be able to reboot at all..
I do have patched_boot.img on my PC where I ran "fastboot flash boot patched_boot.img" and it did not show any error but I still cant reboot it due to no valid slot.
Help me would be greatly appreciated.
it is unlocked and use Sprint carrier.
Thanks,
Adrian
adhusky said:
Please help.. I am stuck with no valid slot to boot and wont be able to reboot at all..
I do have patched_boot.img on my PC where I ran "fastboot flash boot patched_boot.img" and it did not show any error but I still cant reboot it due to no valid slot.
Help me would be greatly appreciated.
it is unlocked and use Sprint carrier.
Thanks,
Adrian
Click to expand...
Click to collapse
You'll have to flash the patched image to both boot partitions. fastboot flash boot_a patched_boot.img. Do the same with boot_b
Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Hey guys, bought a pixel 3 from swappa. Got a good deal because it was bootloader unlocked and the guy didn't know how easy it was to fix. Received it today. I had downloaded the June images a few days ago when I bought it. I fastboot -w it first. I then flashed factory images. Let it reboot. Back to fastboot, set to other slot and repeated factory images and-w. All went well. Back to fastboot and locked bootloader. Everything works including Google pay but when I try to update to July via ota or q beta it fails. Every time. What's up?
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
eldode said:
i have the same issue my phone would not update to july nor Q it gives me no valid operating system
could you please write me the followed steps to recover stock
thnaks
Click to expand...
Click to collapse
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
jmtjr278 said:
Is your bootloader unlocked? If not you need to try and adb an ota.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
jmtjr278 said:
Seems to be sorted after unlocking and re flashing June factory. Downloaded and installed q no problem!
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Did you relock bootloader after updating, cause I need Google pay
eldode said:
bootloader is locked
i need it to install ota automatically from system update
i gives me installation error
could you please help me
Click to expand...
Click to collapse
If bootloader is locked you need to download adb and latest ota images. Boot phone into bootloader, go to recovery, hold volume up and press power until menu appears, apply update from adb, open terminal, give the command to sideload ota, adb sideload file_name.zip. Let it do it's thing. Reboot
Sent from my Pixel 3 using Tapatalk
phuzzeeoyster said:
Did you relock bootloader after updating, cause I need Google pay
Click to expand...
Click to collapse
Yes, I relocked bootloader for the same reason
Sent from my Pixel 3 using Tapatalk