Code:
/*
[SIZE=1]* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the
app failed. Please
* do some research if you have any concerns about unlocking your bootloader and how it pertains to you.
* before flashing ANYTHING YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The time is finally here, the day you’ve been eagerly anticipating, you can now unlock the bootloader on your Sprint OnePlus 7 Pro 5G (GM1925)!
*NOTE: UNLOCKING THE BOOTLOADER ON THIS PHONE WILL PREVENT YOU FROM INSTALLING FUTURE UPDATES VIA OTA, MEANING THEY'LL NEED TO BE FLASHED WITH FASTBOOT OR YOU'LL NEED TO REFLASH STOCK AND RELOCK THE BOOTLOADER TO UPDATE.*.
THERE IS NOT A FEE FOR UNLOCKING THE BOOTLOADER, THE PART OF THIS THAT COSTS MONEY IS THE SHIPPING, IF YOU WOULD LIKE TO DONATE, THAT IS WELCOME AS WELL.
Starting now, you can place a request for bootloader unlock via this MAIL-IN service:
YOUR DEVICE WILL BE WIPED DURING THE UNLOCK
YOU ARE RESPONSIBLE FOR INSURING YOUR DEVICE DURING TRANSIT, IF YOU DO NOT PAY FOR INSURANCE AND ANYTHING HAPPENS TO YOUR PHONE DURING SHIPMENT, THATS ON YOU, EVEN WHEN INSURED, WE ARE NOT RESPONSIBLE FOR ANY REPLACEMENTS OR REPAIRS!
THIS SERVICE IS MAIL IN ONLY, PROCESS IS AS FOLLOWS:
You (the customer) will pay for shipping to the address of the servicer and will send return postage via PayPal before sending us your phone.
You are responsible for insuring the package, if you do not insure the package, and something happens, you will be out of luck, as it’s not our responsibility to replace or repair your phone if it gets lost in transit.
This is a one-time service, meaning that once your bootloader is unlocked and you have received your device back, if you re-lock the bootloader for ANY reason (THIS INCLUDES FLASHING STOCK FIRMWARE WITH MSMDOWNLOADTOOL), You must submit a new request and re-do the mail in process at your own expenditure.
Request will be processed on an individual basis, once we receive your request we will ask you for your:
Full Name
IMEI
Address for return shipping
Phone Number to contact you if necessary.
After receiving the device, we will flash the latest firmware and unlock the bootloader, requests will be shipped back out at the end of the week we receive the phone, or potentially sooner depending on the volume of requests.
TO MAKE A REQUEST, PLEASE LEAVE A COMMENT ON THIS THREAD AND SEND AN EMAIL TO:
[email protected]
We will then direct you where to ship your device, and give you an estimate of return shipping, which will need to be sent via PayPal BEFORE sending us your device.
We will reply to your request via e-mail and collect your personal information from there as well.
The mail-in method is now discontinued due to a more recent development, we (the group of us who have been testing different ways to unlock) have acquired an MSM tool that will allow unlocking the bootloader on the Sprint model without any need to mail it in or even do a remote session!
HOW-TO UNLOCK:
Make sure you have the latest adb/fastboot binary installed and your driver's are fully up to date.
Download the unlocking MSMDownloadTool from here: View attachment guacamoles_unlock.zip
Reboot to EDL mode (Volume Up+Volume Down+USB)
Allow the MSMTool to run to completion, BUT STAY ALERT!
As soon as the MSMTool finishes, it will reboot the phone, DO NOT ALLOW IT TO BOOT TO THE SYSTEM, INTERRUPT THE REBOOT BY ENTERING FASTBOOT
Immediately run "fastboot flashing unlock"
You should now have an unlocked bootloader!
IF YOU ARE ON SLOT B, YOU MAY GET STUCK IN FASTBOOT, TO FIX THIS FOLLOW THESE INSTRUCTIONS:
fastboot --set-active=other
fastboot reboot-bootloader
fastboot --set-active=other (again)
fastboot boot twrp.img
TWRP for Q (10)
Once in twrp, format data again, and then try to reboot.
Install TWRP/Magisk:
TWRP for Q (10)
TWRP for Pie (9)
TWRP Installer zip
Magisk Installer
* Copy the TWRP img to your adb directory and run:
Code:
fastboot boot twrp-3.3.1-79-guacamole-unified-Q-mauronofrio.img
* Or for Pie:
Code:
fastboot boot twrp-3.3.1-4-guacamole.img
* Copy the installation zips to your storage
* Flash twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip
* Flash Magisk-v20.4.zip
* Reboot
HAPPY FLASHING!
SCREENSHOTS FOR PROOF:
Edit: This reply was made when it was a mail-in service. You can disregard now.
Uhh, I know this is posted by a senior member and all, but this seems super sketchy to me... Why is there any need to send it in? Do you not want your code public as of rn? Do you need specialized hardware to do it? A little explanation in that area would be nice...
Guy50570 said:
Uhh, I know this is posted by a senior member and all, but this seems super sketchy to me... Why is there any need to send it in? Do you not want your code public as of rn? Do you need specialized hardware to do it? A little explanation in that area would be nice...
Click to expand...
Click to collapse
Exactly that, the developer of the tool that is being used does not want the code public as of right now, but has authorized us to perform unlocks for those willing to ship their device.
Whoareyou said:
Exactly that, the developer of the tool that is being used does not want the code public as of right now, but has authorized us to perform unlocks for those willing to ship their device.
Click to expand...
Click to collapse
Hmm... Alright, that's understandable I suppose. As for everyone else I would just proceed with caution till we have a couple confirmed success stories on here. No offense to you @Whoareyou, but I've seen this type of thing before to where many people ended up having their devices stolen because of fake mail-in services. Either way tho, fairly excited to know there's at least some possibility of a bootloader unlock!
Guy50570 said:
Hmm... Alright, that's understandable I suppose. As for everyone else I would just proceed with caution till we have a couple confirmed success stories on here. No offense to you @Whoareyou, but I've seen this type of thing before to where many people ended up having their devices stolen because of fake mail-in services. Either way tho, fairly excited to know there's at least some possibility of a bootloader unlock!
Click to expand...
Click to collapse
Totally understand your hesitation, I'd be wary too, hopefully a few will take the plunge so some trust can be formed here.
I have more proof that this works if you guys would like...
I too can vouch that this works.
Hahaha you still have no proper twrp and roms and I highly doubt this will change that....
xdg4y said:
Hahaha you still have no proper twrp and roms and I highly doubt this will change that....
Click to expand...
Click to collapse
TWRP is already unified for the 5G variant and works fine,
See this post about ROMs:
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-oneplus-7-pro-5g-rom-gsi-t4042583
His method is confirmed working. I have TWRP installed and magisk working correctly. I currently went through his process. It's honestly nice as hell for him to be offering this service for free.
I'm def looking into this next payday.
[BOOTLOADER UNLOCK] Sprint OnePlus 7 Pro 5G [MAIL IN ONLY]
lreyes said:
His method is confirmed working. I have TWRP installed and magisk working correctly. I currently went through his process. It's honestly nice as hell for him to be offering this service for free.
Click to expand...
Click to collapse
Check PM please.
Awesome!
Would it be possible to offer this service remotely with a tool such as USB Redirector? I work with a handful of companies who do all sorts of firmware flashing and unlocks using this tool and I've rarely had issues with it. It might be a bit more hassle given that both you and the "customer" have to be online and connected at the same time (though easily mitigated with Discord or another IM service) but it eliminates the liability of a phone being lost or stolen and people won't be without their phones for days at a time.
coromd said:
Would it be possible to offer this service remotely with a tool such as USB Redirector? I work with a handful of companies who do all sorts of firmware flashing and unlocks using this tool and I've rarely had issues with it. It might be a bit more hassle given that both you and the "customer" have to be online and connected at the same time (though easily mitigated with Discord or another IM service) but it eliminates the liability of a phone being lost or stolen and people won't be without their phones for days at a time.
Click to expand...
Click to collapse
We explored that route, unfortunately the delay is too long for the tool to work, we were able to connect to the phone to the tool but it fails to work with a timeout error from the tool and the phone reboots with no changes.
I can also confirm that this works. I can also confirm that the reason be for the mail in, because the Author of the said tool, does not want it released to public, We are looking for other
avenues to make this process faster and much easier without having to mail in or release said tools.
Bootloader
I am very interested. I'm assuming twrp and magisk will be installed too when you unlock the bootloader.
mirceaanghelescu said:
I am very interested. I'm assuming twrp and magisk will be installed too when you unlock the bootloader.
Click to expand...
Click to collapse
I can certainly do that, though it's very easy to do after the bootloader is unlocked.
yea.. sending phone to a stranger to unlock bl bcuz they dont want to share publicly means they have a business and want to make $$$ lol
its a shame
elliwigy said:
yea.. sending phone to a stranger to unlock bl bcuz they dont want to share publicly means they have a business and want to make $$$ lol
its a shame
Click to expand...
Click to collapse
Not sure where you're getting that implication, but the service is free, you just have to pay for shipping.
Again, I didn't write this tool, I simply have been given permission by the person who did to offer mail in unlocks since I have the free time to dedicate to it.
They have requested it not be made public, therefore it's not my place to release the tool, I can however, offer mail in unlocks, as that doesn't expose the exact method and has been green-lit by the creator.
If you have a problem paying for shipping, or are uncomfortable with your device being mailed to a stranger, I fully understand that, you don't have to take advantage of the service or you can wait until a remote method potentially becomes available, but don't display your discomfort as negativity with unwarranted accusations.
I'm just trying to help people get unlocked and spur some development for this phone.
Related
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Here a Picture of the Device with the Error Message and Software Version
What version of phone do you have 973U? What carrier do you have?
highaltitude said:
What version of phone do you have 973U? What carrier do you have?
Click to expand...
Click to collapse
G973F
A1 Austria
Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
There's another similar post that you may find helpful.also might be try asking unlock io and see what they say. Let us know.
https://www.reddit.com/r/galaxys10/...date/?utm_medium=android_app&utm_source=share
Sent from my SM-G975U using Tapatalk
Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .
i already tried a hard reset, did not solve the problem.
i will try smart switch and let you know
Rexton270 said:
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .
Click to expand...
Click to collapse
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch
Proxolin said:
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch
Click to expand...
Click to collapse
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...
Rexton270 said:
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...
Click to expand...
Click to collapse
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.
AHE_XDA said:
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.
Click to expand...
Click to collapse
thank you for that explanation.
i will first try to update the phone with smart switch as soon as there is a newer version for my phone, atm it says im up to date (i hope that is true) maybe it solves itself when i start an update with smart switch, if not i will follow your steps
thank you very much.
because there was still no update in samsung smart switch i flashed it with odin.
problem solved.
thank you.
for other users: if you want to unlock your phone, use the samsung database instead of the cheaper version.....
Excellent news. Glad to hear it all worked out.
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?
borgqueenx said:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?
Click to expand...
Click to collapse
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.
JazonX said:
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.
Click to expand...
Click to collapse
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.
borgqueenx said:
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.
Click to expand...
Click to collapse
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader
xchatter said:
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?
I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?
JazonX said:
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?
Click to expand...
Click to collapse
Hi there,
I don't have any Huawei device right now. Only one P20 Pro for my wife but I unlocked it with a code back then.
I had a Mate 30 Pro but sold. Waiting for some stable google services solutions and I will buy again.
borgqueenx said:
I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?
Click to expand...
Click to collapse
Yes no problem at all.
ADB reboot bootloader works just fine, the usual white bootloader screen. No FRP lock though, which explains the "missing" switch in Developer Options.
Fastboot reboot, then reboots the phone as normal.
Didn't try any other commands.
Just waiting to get my pro plus to try this. Anyone else?
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Unfortunately not. Although if all data is erased, it should have successfully completed its task and then you have a unlocked bootloader.
If no unlocked bootloader, your data should be kept on the device.
GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Make a backup with HiSuite on PC : Which you can restore later if the operation is successful.
Your data will only be erased if the Bootloader gets unlocked. At the attempt / trying stage It won't trigger a data wipe.
If the bootloader does get unlocked, It will be a massive win which is totally worth doing the google installations again.
Maybe next time onwards you can use Titanium Backup to backup apps and data., Push the Google Apps from the system dump of P30 Pro EMUI 10 to the Mate 30 / P40 Pro devices to have Playstore certified GMS, Host level adblocking and many more life-saving solutions.
Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any other ideas?
That is unfortunate. I dont think we can do more then. Will request a lock for this topic if no one else gives ideas this week.
Thanks for trying!
GabiTM said:
Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
Any other ideas?
Click to expand...
Click to collapse
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?
colthekid said:
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?
Click to expand...
Click to collapse
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.
borgqueenx said:
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.
Click to expand...
Click to collapse
Can we start a gofundme or something similar, money is a good incentive.
GabiTM said:
Can we start a gofundme or something similar, money is a good incentive.
Click to expand...
Click to collapse
Nope, because this is a very well paid job.
It could start to be attractive if you also count the media attention at minimum 50k dollar.
If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit
Gatos7 said:
If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit
Click to expand...
Click to collapse
Just like I thought...
The ban will cost them sure a lot sales off smartphones... And also aocked bootloader ?
To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.
Entry 1 added - nothing really important
Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!
The CPW in the build number is more of a guess than anything else we all could be wrong
alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine
Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm
PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:
The only problem being ... I have no idea idea what this menu says -_-
I guess that is tomorrows episode though, connecting it via ADB+TWRP
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader
just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I wonder if you could flash on the chinese version of the firmware
it seems that the device is really a 'realme gt 5g' .... trying to verify this
PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-
Here's a free How-To on how i successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022 that was carrier locked to Verizon and now fully Unlocked.
DISCLAIMER:
*This does NOT trip Knox or Void your warranty and does NOT require a root or a paid service. **This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.***This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
You can read more on how this method works to force a carrier update to your device, here, on the Official Android dev site.
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here, Stock Firmware and ODIN Flashing Guide (XDA) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•(Optional?) Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process. Link: Android Dev Platform Tools (Official)
Step 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
NOTE:
It Is CRITICAL that we flash the U1 rom BEFORE putting in the desired carriers SIM, then reboot, let phone fully boot, ONLY THEN should we insert the desired carriers SIM.
Step 1b:
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE.
IMPORTANT! MAKE SURE YOU DOWNLOAD BOTH THE "U" ROM FOR THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED (XAA) ROM/Firmware.
IF YOU ALREADY HAVE U1 FIRMWARE
I.e "SM-G998U1xxxxxxx" - you can skip to step 2, but I would recommend reading through the next part.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm the device is now showing the "U1_XAA" in the Service Provider Software Version - it should say something like "SM-G998U1_XAA blah blah blah" - you just want to see the "U1" bit.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device.
! CRITICALLY IMPORTANT STEP !
We will now initiate a reboot, but BEFORE the device fully restarts, we need to force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold them directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery, please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select & Execute.
AGAIN, Very Important step! We MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, we need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in, essentially it should remain plugged in throughout this process.
We should now be back in download mode and be on "U1" as we have verified in the steps above.
STEP 3:
Now it's time to flash the ROM/Firmware from the carrier you wish to use. Make SURE you have the SIM from the same carrier inserted during this process as mentioned at the beginning. It doesn't need to be a working or activated SIM, just simply one from the carrier you wish to have this S21 work on.
Flash all items from the "U" ROM/Firmware as you did earlier, ensuring to use the "U" ROM/Firmware for your desired carrier as described above. Same deal with CSC here, DO NOT use the "Home_CSC", use the other.
BE SURE that you use the USERDATA file that comes with the "U" ROM/Firmware. Its Critical in order to get the phone working properly on the new carrier.
Start the Odin flashing process & wait.
Phone will Auto-Reboot.....
Done!
You should now be on the carrier you wish to use.
This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung.
Please comment your experiences/ issues etc below. Don't be afraid to ask for clarity of something.
PoC, results after doing above process pictured in this screenshot.
Good luck.
-k0mrade
Send me Crypto if I helped?
Before process, this message would appear shortly after inserting a new SIM in testing devices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After preforming above procedures I now find pictured below by running this activity:
com.samsung.ssu.unlock.MainActivity
And verify twice by checking my work in Settings>About>Software Information> Service Provider Software Version & Carrier Configuration Version.
For anyone whos still having trouble, try following the directions on this thread. Maybe they explain it a bit better or their process omits/includes parts ive missed.
Alternative Guide To Carrier Unlocking S21
Good Luck.
-
Have you attempted this on lower bootloader revisions?
iBowToAndroid said:
Have you attempted this on lower bootloader revisions?
Click to expand...
Click to collapse
I have not. But am very interested to see how it goes if you or anyone decides to give it a shot, it SHOULD work on any BL considering the method of attack. But I can't verify it does.
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason CCT remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
xDpakaX said:
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason XAS remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
Click to expand...
Click to collapse
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
What's the Baseband Version?
iBowToAndroid said:
What's the Baseband Version?
Click to expand...
Click to collapse
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
iBowToAndroid said:
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
Click to expand...
Click to collapse
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Yep then you're screwed. It can't done if Knox is tripped
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Is it still unlocked and rooted? That would make life another easier. We can repair the IMEI, baseband etc. It's worth a go if the phones just a paper weight right now imo. But ultimately up to you.
K0mraid3 said:
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Click to expand...
Click to collapse
Thank you! I'll give it a try and report how it goes.
Good luck! Worst case, look up a program called "Samsung TFT Module", just be sure to scan it for viruses and bad code if you have the ability.unless you are able to find the 2022 update of it, you'll have to settle for whatever version is available. It'll likely be old, clunky and out-of-date, half the program defunct, but a few key parts still work, and quite well. Don't forget ADB drivers. Let us know how it goes!
Proverbs2 said:
Thank you! I'll give it a try and report how it goes.
Click to expand...
Click to collapse
Ok, I tried to follow each step carefully, but I had to make one minor change to the procedure: after flashing the U1_XAA firmware, I had to power off the phone in order to insert the SIM card. (In the XCover Pro, the SIM card slot is obstructed by the battery, so there is no way to insert the card without powering off the phone and removing the battery.) After inserting the card, I booted directly into recovery and followed the other steps from there.
Unfortunately, it didn't work for me: the phone is still locked, showing the same message: "Sorry, your device can't be activated on another carrier's network..." Perhaps that's because I wasn't able to perform that one critical step, inserting the sim card while the phone is turned on. Any suggestions for a workaround?
K0mraid3 said:
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Click to expand...
Click to collapse
Yes, I followed the guide. The problem is that when I'm on U1 my phone doesn't ask me to reboot.
Hello. I did all on VZW SQU3AUDB phone. Did all steps.
I have question. But in first start after step 3 (i flash G998U VZW) i see: Sorry, your devic.... verizon message
STEP3: Now it's time to flash the ROM/Firmware from the carrier you wish to use
It min - i need to flash not VZW ROM? some other? I need to use Ukrainia operator sim. Or i need flash G998W or else?
can someone help me?
Does my bootloader need to be unlocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a pixel 5a that was flashed with a custom os the restricted developer options and locked the bootloader is there any way for me to remove the os and go back to stock android?
This is what they sent me
(I was told that I might be able to flash the snapdragon soc directly by putting the phone in edl mode does anyone know if it’s feasible?)
I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no/ drama...
SomeRandomGuy said:
I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no
SomeRandomGuy said:
I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no/ drama...
Click to expand...
Click to collapse
im not even sure that I can access it from fastboot because as I said developer options is restricted on the phone so I can’t enable usb debugging and oem unlocking
Click to expand...
Click to collapse
I need to find someway to flash stock android back onto it
Google's support website for the Pixels lets you do it... directly from any browser that supports WebUSB (e.g. Chrome and its variants, newer FF's, etc).
SomeRandomGuy said:
Google's support website for the Pixels lets you do it... directly from any browser that supports WebUSB (e.g. Chrome and its variants, newer FF's, etc).
Click to expand...
Click to collapse
I dont think it’ll work without enabling usb debugging
CustomOShacks said:
I dont think it’ll work without enabling usb debugging
Click to expand...
Click to collapse
you can flash the stock factory image from here in bootloader mode (power + vol down)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
i use to this site remove non stock keys. at the very bottom of the webpage if i want to return to stock and flashed calyxos or graphenos to my phone.
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
rchris494 said:
you can flash the stock factory image from here in bootloader mode (power + vol down)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
i use to this site remove non stock keys. at the very bottom of the webpage if i want to return to stock and flashed calyxos or graphenos to my phone.
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Click to expand...
Click to collapse
The bootloader is locked
CustomOShacks said:
The bootloader is locked
Click to expand...
Click to collapse
i did run across this. i am not sure how trust worthy the tools this person has are
https://www.youtube.com/c/5MinuteSolutions-DZ
i also did not see anything pixel 5a related.
also maybe there is something on 4pda that can help with the problem
rchris494 said:
i did run across this. i am not sure how trust worthy the tools this person has are
https://www.youtube.com/c/5MinuteSolutions-DZ
i also did not see anything pixel 5a related.
also maybe there is something on https://4pda.to/ that can help with the problem
Click to expand...
Click to collapse
Can you please post something more specific
Do you know if these tools will work without usb debugging enabled because the custom rom that my 5a is running restricts developer options so I don’t know how to enable usb debugging
So, by chance (and my stupidity) I am now in the same boat. This is a very frustrating situation that is close to making me swear off the entire Pixel line, forever.
TL;DR: Is there ANYTHING that works in fastboot mode with a locked bootloader?
Long version:
- I have a properly signed custom OS, and all the images AOSP would build (the factory image, the OTA image, etc).
- When the phone was last booted, "Enable OEM Unlocking" was ON, with the bootloader locked. Everything worked nicely.
- I stupidly let Magisk update itself, which of course borked the boot
- I can no longer get into recovery from fastboot (whines about broken OS) (e.g. to sideload OTA update)
- Despite OEM unlocking being on (or having been on and cursed with somehow it getting turned off), I can't unlock bootloader from fastboot
- I can't flash ANY partition (at least that I tried); all whine about locked bootloader
- I can't flash original Google image either (from Google web installer), whines about unlocking
- I can't use the GrapheneOS web installer to unlock bootloader (just fails)
- I can't fastboot boot <signed_boot_image> (e.g. to get to sideload from recovery), whines about unlocking
Especially with a device that doesn't allow SDCards, I'm far more concerned with something bad happening (like whoops, clicked the wrong button and autoupdated => brick) and me not being able to pull my data (SMS/MMS stuff, pictures, etc) than I am about all the (mostly valid) reasons for verified boot.
I would assume that I could still flash partitions that were properly signed by whatever keys were installed. Guess not. What a stupid restriction.
I'd also assume I could flash partitions signed by Google (if secure boot can tell me I'm running something other than stock, that means it has keys to verify stock, right?). Guess not. What a stupid restriction.
On a OnePlus, a quick EDL flash would unbrick this (would destroy data, of course, but at least I am not out $~500). I understand there are no EDL images published anyway (and I certainly can't find any).
I've read the above posts about overwriting the FBI's version of Android, and didn't find any functional means of unlocking and/or returning to stock (e.g the web installers for GrapheneOS or Google).
Is there maybe something I've missed? A lower level fastboot command I can use to restore the boot partition (again, I've got a properly signed one).