Hi I was wondering if ANYONE could give be some assistance on my Pixel XL. I JUST bought it from eBay thinking it was like a typical android locked bootloaderwith bootloop. I've tried a lot of options (I believe this one was from Verizon) It's running 8.1 now, I think.
It's booting to the GOOGLE logo then looping from there.
Anyway, whenever anyone has some free time to maybe give me a hand, no rush. I would highly appreciate it.
-wtrgte
wtrgte said:
Hi I was wondering if ANYONE could give be some assistance on my Pixel XL. I JUST bought it from eBay thinking it was like a typical android locked bootloaderwith bootloop. I've tried a lot of options (I believe this one was from Verizon) It's running 8.1 now, I think.
It's booting to the GOOGLE logo then looping from there.
Anyway, whenever anyone has some free time to maybe give me a hand, no rush. I would highly appreciate it.
-wtrgte
Click to expand...
Click to collapse
Hello,
What are those options you have tried to solve your issue?
Did you try to factory reset from stock recovery?
Good luck...
If you do a search for unlocking pixel XL Verizon there is a huge thread on it. If I get a chance I'll link it for you.
Well since the bootloader is locked it's giving the trouble with every type of factory, ota, update I tried. I'm going to keep searching but if someone can link me to something or point me in the right direction, PLEASE DO!
wtrgte said:
Well since the bootloader is locked it's giving the trouble with every type of factory, ota, update I tried. I'm going to keep searching but if someone can link me to something or point me in the right direction, PLEASE DO!
Click to expand...
Click to collapse
He'll,
Describe properly what you tried maybe?
What is the output of the factory reset?
OTA result?
Without proper details, it's hard for people to point you in the right direction...
Cheers...
wtrgte said:
Hi I was wondering if ANYONE could give be some assistance on my Pixel XL. I JUST bought it from eBay thinking it was like a typical android locked bootloaderwith bootloop. I've tried a lot of options (I believe this one was from Verizon) It's running 8.1 now, I think.
It's booting to the GOOGLE logo then looping from there.
Anyway, whenever anyone has some free time to maybe give me a hand, no rush. I would highly appreciate it.
-wtrgte
Click to expand...
Click to collapse
[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Page 1 (OP)
wtrgte said:
...I JUST bought it from eBay thinking it was like a typical android locked bootloaderwith bootloop. I've tried a lot of options (I believe this one was from Verizon) It's running 8.1 now, I think.
It's booting to the GOOGLE logo then looping from there.
Click to expand...
Click to collapse
Sounds like the exact same situation I just experienced some hours ago I ordered a random Pixel XL off eBay, and also assumed it'd be easy to run a fastboot command to unlock the bootloader. Ran into the grayed-out OEM unlock option, and after some reading, I assume this is a VZW/Verizon model.
This thread here worked great for me (had to factory reset twice though); my Pixel was on 8.1 on last year's April security patch, but apparently this still works even up to the latest Pie version: https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030 and basically just involves factory resetting, not signing into Google, removing the Phone app, and then being able to OEM unlock.
Once unlocked like that, you really shouldn't ever re-lock it manually unless you have a very good reason to as there's no guarantee in the future you can still unlock like that. I'm currently on LineageOS 15.1 no problems now.
Related
Hey guys. A few months ago a brought this issue up on another site and I think I only got one response. I ended up getting lazy with it and too frustrated to worry about it, so I gave up. Well, I'm finally ready to try and resolve it again so I wanted to see if anyone here could help me before I screw something up and brick my device lol. I have a Retail Verizon HTC One (M7) that was purchased about 3 months ago. After I bought it, I Rooted, unlocked, S-OFF, installed TWRP, all that good stuff. Everything, from what I can remember, went smoothly when doing all those things. Well, I finally at one point, decided to test out a Rom and have not been able to successfully install one yet and I have no idea why. I have tried a few and TWRP always returns a "Failed". The most recent one I tried was the ViperOne 6.2.0 (May 11). The only exception for that one, was that the aroma installer actually did say "Successful" but when I booted up I was stuck in a boot loop. I'm sure I've done something along the way that has screwed something up but I have no clue what that would have been. I'm attaching a few pictures with some info on my current setup, in hopes that something might catch someone's eye and offer a solution. Thanks a head of time for any help guys.
Radiohead84 said:
Hey guys. A few months ago a brought this issue up on another site and I think I only got one response. I ended up getting lazy with it and too frustrated to worry about it, so I gave up. Well, I'm finally ready to try and resolve it again so I wanted to see if anyone here could help me before I screw something up and brick my device lol. I have a Retail Verizon HTC One (M7) that was purchased about 3 months ago. After I bought it, I Rooted, unlocked, S-OFF, installed TWRP, all that good stuff. Everything, from what I can remember, went smoothly when doing all those things. Well, I finally at one point, decided to test out a Rom and have not been able to successfully install one yet and I have no idea why. I have tried a few and TWRP always returns a "Failed". The most recent one I tried was the ViperOne 6.2.0 (May 11). The only exception for that one, was that the aroma installer actually did say "Successful" but when I booted up I was stuck in a boot loop. I'm sure I've done something along the way that has screwed something up but I have no clue what that would have been. I'm attaching a few pictures with some info on my current setup, in hopes that something might catch someone's eye and offer a solution. Thanks a head of time for any help guys.
Click to expand...
Click to collapse
How about try a different recovery?
Radiohead84 said:
Hey guys. A few months ago a brought this issue up on another site and I think I only got one response. I ended up getting lazy with it and too frustrated to worry about it, so I gave up. Well, I'm finally ready to try and resolve it again so I wanted to see if anyone here could help me before I screw something up and brick my device lol. I have a Retail Verizon HTC One (M7) that was purchased about 3 months ago. After I bought it, I Rooted, unlocked, S-OFF, installed TWRP, all that good stuff. Everything, from what I can remember, went smoothly when doing all those things. Well, I finally at one point, decided to test out a Rom and have not been able to successfully install one yet and I have no idea why. I have tried a few and TWRP always returns a "Failed". The most recent one I tried was the ViperOne 6.2.0 (May 11). The only exception for that one, was that the aroma installer actually did say "Successful" but when I booted up I was stuck in a boot loop. I'm sure I've done something along the way that has screwed something up but I have no clue what that would have been. I'm attaching a few pictures with some info on my current setup, in hopes that something might catch someone's eye and offer a solution. Thanks a head of time for any help guys.
Click to expand...
Click to collapse
You have the m7wlv recovery installed. Flash the current m7vzw and you should be good to go.
Sent from my One using Tapatalk
Ok, thank you both. Trying that now. I'll let you know how it goes.
Yep that did it! Wow...I feel like an idiot. Thank you guys. I really appreciate your help.
Radiohead84 said:
Ok, thank you both. Trying that now. I'll let you know how it goes.
Yep that did it! Wow...I feel like an idiot. Thank you guys. I really appreciate your help.
Click to expand...
Click to collapse
So what exactly did you do that worked?
Can you provide the recovery that worked for you ?
MMR4LIFE said:
So what exactly did you do that worked?
Can you provide the recovery that worked for you ?
Click to expand...
Click to collapse
Last night I just ended up flashing this RUU which worked: http://tinyurl.com/l3j7rhk
Then, after reading the solution offered here, I noticed on that same thread a link to TWRP 2.7.0.8 Decided to flash that and I am now able to successfully flash Rom's again. I tried two separate ones just to be sure. ViperOne and Cyanogen. Everything seems to be working as it should now.
did you installed kit kat ?
Radiohead84 said:
Last night I just ended up flashing this RUU which worked: http://tinyurl.com/l3j7rhk
Then, after reading the solution offered here, I noticed on that same thread a link to TWRP 2.7.0.8 Decided to flash that and I am now able to successfully flash Rom's again. I tried two separate ones just to be sure. ViperOne and Cyanogen. Everything seems to be working as it should now.
Click to expand...
Click to collapse
Hi
Mine Unlocked HTC One (Verizon) brought in US retail store. Now am using my GSM sim everything going well..
Can i install this custom ROM
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=230836252
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
soccerplayer00321 said:
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have an unlocked bootloader (root)? You could try reflashing twrp with odin to get recovery back.
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
soccerplayer00321 said:
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
Click to expand...
Click to collapse
If you don't want to root, you could try flashing the cpd1 firmware with odin and that should overwrite what might be throwing off your battery calibration. Unless it's a hardware problem that is. Are you comfortable using odin? Also if you have no interest in rooting, you could flash the most recent firmware.
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
soccerplayer00321 said:
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
Click to expand...
Click to collapse
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
kevintm78 said:
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
Click to expand...
Click to collapse
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
soccerplayer00321 said:
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
Click to expand...
Click to collapse
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Sent from my SM-N910V using XDA-Developers mobile app
kevintm78 said:
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Click to expand...
Click to collapse
No luck on Kingroot. It usually dies around 25% or so. Sometimes a little before that and sometimes after that. It never even got into the 35% range.
What I think I am going to do is go back to kitkat, original samsung rom. Try Kingoroot and see if that works. If not, I will push lolipop to it and try kingoroot again. If that doesn't work, I will try to push Marshmallow to it and try one more time. Hopefully one of them will be successful.
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
fastjohnson said:
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
Click to expand...
Click to collapse
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
kevintm78 said:
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
Click to expand...
Click to collapse
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
fastjohnson said:
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
Click to expand...
Click to collapse
It may not make a difference, but there is a newer version of Odin here that you could try.
kevintm78 said:
It may not make a difference, but there is a newer version of Odin here that you could try.
Click to expand...
Click to collapse
I'll give it a shot, right now I'm a Lil burned out on trying this because my other phone LG g4 is boot looped for no reason so I'm down to just my N4 and my N3 my gf has it. I forsee a big cup of coffee at 3am and let the flashing begin. Oh FYI I did try I think Odin 3.10 version it failed quicker so I'll try this version in the morning. I appreciate your help very much you'll be the 1st to know if it pushes through. Merry Christmas btw.
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
fz798 said:
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
Click to expand...
Click to collapse
Reflashed and thought the wakelocks were gone, but not so. msm_hsic_host appears to be related to cellular.
flyers00 said:
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Click to expand...
Click to collapse
What I've noticed with this bootloader unlock is, like right now I'm 5.1.1 and my bootloader is unlocked but not rooted. OK if I use the the no A boot 6.0.1 file to flash mm it's stay unlocked and you can be rooted but if you use the normal full firmware 6.0.1 cpd1 file you lose your unlocked BL and back to start. Normally you unlock a BL it's stays unlocked no matter what you do. OK bugs with the no A boot 6.0.1 mm file no WiFi that's it. I really dislike 5.1.1 it sucks so there's not a lot of choices here. Good work on this exploit though.
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.
pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Anyone tried Google's flashing update tool?
Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now
Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.
I got my hands on a Google Pixel 3XL phone modified by TotalSec. It seems like it has LineageOS modified by them and installed but bootloader locked without option to unlock it. Is there a way to force developer options thru OS somehow where I can unlock the bootloader? Tapping 7 times on build does nothing...they sell this phone for €1500 with 6 month service. After 6 months, phone is useless...
I don't know anything about TotalSec. I checked their site and see they offer the Pixel 3 and Pixel 3A. At 1500 euro, for 6 months use (I couldn't find the price for the ongoing subscription) this is clearly not a product intended for the consumer. I didn't see the 3XL.
I'm interested how they accomplished re-locking the bootloader on a Pixel device with a non-stock OS. Having to leave the bootloader unlocked is a security concern. I think many Pixel owners would like to unlock their bootloader, root or make other changes, then re-lock the bootloader.
It seems like they are running LineageOS as a base, modified it and locked it down. You have to literally log in, pay 1500 euros for 6 months of use. There is no option of tap build 7 times to enable developer options so I cant unlock the bootloader. Im currently in fastboot mode and will attempt to load new recovery and bootloader.
Is there a way to unlock a bootloader from fastboot mode?
My friend has one of those coming in. Pixel 4, specifically.
My guess is that they have custom AVB keys installed which allows them to relock the bootloader. Do you get a _yellow_, not orange, warning when you boot the device up?
Regardless, you should be able to flash stock even with a locked bootloader; https://flash.android.com/ should work just fine. I don't recommend you flash the device yet, unless it's your only device, as you might want to grab a copy of the OS just for ... giggles.
{Mod edit: Inappropriate language removed. Oswald Boelcke}
Thank you! Let me try it, it is my extra phone laying around with no use for anything at the moment. I use Pixel 7 Pro as a daily.
No go. It is telling me to enable OEM unlocking
{Mod edit: Inappropriate language removed. Oswald Boelcke}
what happens when you run `fastboot flashing unlock`? im not expecting anything to happen since the developer options are gone but I'm a tad curious. also, see if you can boot it to fastbootd.
there's also an app on fdroid called setedit, try to download it on that phone and search "development_settings_enabled". if it pops up set it to 1 and you should have the developer settings enabled
i won't lie to you i don't think there's anything that can be done. you could try manually installing the stock OS with the fastboot cli but i doubt it would lead to anything.
Yeah I think I tried that. Weird that OS level has triggers that switch on/off the bootloader and not CLI part! CLI should have priority and logically it makes more sense to be done now, not on OS level!
Did you found any solution, I have Pixel 4 with same situation I tried to sideload latest lineage OS flame via recovery to overwrite the existing system done with error !
Mine is stuck in fastboot, cant do anything! I wish I can wipe it and load a fresh OS! No luck so far!
At this point I'm tempted to get one of those devices for myself to experiment on. How much did you all get them for?
I got it for free from a friend of mine but prices are insane, it's $1500-$2000
I got a notification in my email, I dont see that message anymore, setedit app??
Oh yes, I edited the comment to remove it since it doesn't work for writing settings without some permissions that need to be given over ADB.
I'm trying to think what you can do, my friend got theirs and has so far been unable to do anything with it
Are you just trying to find a use for it? You might be able to completely reinstall everything with a firehose. I could try to find one for your pixel 3xl, there probably is one on XDA.
It's certainly a last resort and not something you should do for every device, but I'm running out of ideas and Qualcomm proprietary stuff is fun to mess with imo
pmnlla said:
Are you just trying to find a use for it? You might be able to completely reinstall everything with a firehose. I could try to find one for your pixel 3xl, there probably is one on XDA.
It's certainly a last resort and not something you should do for every device, but I'm running out of ideas and Qualcomm proprietary stuff is fun to mess with imo
Click to expand...
Click to collapse
I can send you a Google Pixel 3XL for free, with the bootloader locked from TotalSec. There are a lot of Google Pixels here in Albania that they have no use anymore because there are a lot of alternatives. But with the bootloader locked, we cannot do anything.
What do you mean by that? many useless phones because of the totalsec OS? shoot me an e-mail at [email protected], I know a few people who could possibly help.