Help Me Unlocking Bootloader Goole Pixel 2 Verizon - Google Pixel 2 XL Questions & Answers

Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root

Yosh2897 said:
Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root
Click to expand...
Click to collapse
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man

Badger50 said:
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man
Click to expand...
Click to collapse
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk

Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Click to expand...
Click to collapse
Sorry man. KA requires root, so that's not a possibility either :fingers-crossed:

Yeah I made the same mistake , grabbed a XL 2 for 200 and realized it was a vzw variant

Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background

Az Biker said:
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background
Click to expand...
Click to collapse
Please tell me configuration on your greenify, i will enable access user from adb, and how to turn off running in background? Cause it's minimal option, maybe 10 app on check background, not at all
Sent from my Pixel 2 using XDA Labs

And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs

Yosh2897 said:
And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.

Yehudah said:
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.
Click to expand...
Click to collapse
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel

Yosh2897 said:
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel
Click to expand...
Click to collapse
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...

CyberpodS2 said:
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...
Click to expand...
Click to collapse
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?

I feel you Cyberpod...but, looking through this specific thread...I don't believe he's actually stated outright or confirmed that it is in actuality a Verizon variant...
I would say that's first and foremost OP...I know you are rather impatient about it, and tried some things, and intend "...not gonna paying attention about this...", but you really should verify (for sure) if you have the proper variant.
Also, merely reading through this specific thread, he may simply want to talk/contact Google Pixel support but didn't know how... Although, even the smallest bit of effort would easily find the answer; I'll "throw you a bone"... you will find it here: https://support.google.com/pixelphone/?hl=en#topic=7078250&contact=1
But, to be blunt, if you are going to ask for help here on XDA, we at the very least expect the bare minimum of effort (without complaint) and not handing everything "on a silver platter"... this is just not that kind of place...
UPDATE: Post #12 seemed to have been input and came in a minute before this one (mine)... but see! Verifying if it's a Verizon variant was never established and needs to be...

bro, why i make this thread and try to ask you all,
i got command like this
C:\adb>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: -0.000s
C:\adb>fastboot --version
fastboot version eac51f2bb6a8-android
C:\adb>fastboot flashing unlock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash unlock
unknown partition 'unlock'
error: cannot determine image filename for 'unlock'
C:\adb>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s

Yosh2897 said:
bro, why i make this thread and try to ask you all,
i got command like this
Click to expand...
Click to collapse
What answer are you expecting? It's not possible. Verizon locks the bootloader and nobody has found away around that. Either live with that or sell your phone and get one that's unlocked.

Yosh2897 said:
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?
Click to expand...
Click to collapse
Constantly repeating a task and expecting the result to change is a sign of insanity. While I don't think you've lost your mind - yet - you're rapidly descending to that level. I've said this before and I'll say it again. If you want root you do not buy a Verizon device!
Since you apparently have a Verizon device, your options are to sell it or live without root, which actually is doable. No exploit has been found to bypass the bootloader encryption, and brute forcing the encryption itself will take a period of time greater than the age of the universe.

I never expect to get bundling device by verizon, but, indonesia doesn't have official store, all of them selling this phone without knowing what type they got and just sell to buyer, to be honest, hard to find a sparepart, warranty for this device, so the option, i just do by myself. I'm sorry if pushing you all, and always ask about this things. Have a nice day mate.

Related

[Q] KitKat Beta and unlocking the bootloader/rooting/installing rom

Hi guys sorry if something i say is incorrect or noobish, a few months ago i rooted my HTC One XL (international/evita) and it was a painful process with alot of hiccups.
I have been reading up alot on how to root/unlock the bootloader of my new huawei p6 and the safest way to do would firstly be to install the kitkat beta right?
I have found 2 issues with this:
1. The DL.huaweinews.com portion of the huawei news website seems to be down or i cant reach it for some reason and i cannot find a mirror on mega.co.nz or on any other file hosting site.
2. there are articles saying that the kitkat official will be/has been released on or around march 30th and i can DL via the normal system update method. I see no such update im currently on B118 and it says there are no further updates.
I also accessed the bootloader already? i did the usual power+vol down and it took me to a bootloader of sorts however it was all in Chinese, this makes sense to me because i ordered it from china (ebay) but when im in system info it just says .....................b118 not ..................b118cn, so does this mean im in a locked bootloader?
any sort of help would be much appreciated as I really hate this UI and hate this non vanilla crap.
Check it first
Raff1234 said:
Hi guys sorry if something i say is incorrect or noobish, a few months ago i rooted my HTC One XL (international/evita) and it was a painful process with alot of hiccups.
I have been reading up alot on how to root/unlock the bootloader of my new huawei p6 and the safest way to do would firstly be to install the kitkat beta right?
I have found 2 issues with this:
1. The DL.huaweinews.com portion of the huawei news website seems to be down or i cant reach it for some reason and i cannot find a mirror on mega.co.nz or on any other file hosting site.
2. there are articles saying that the kitkat official will be/has been released on or around march 30th and i can DL via the normal system update method. I see no such update im currently on B118 and it says there are no further updates.
I also accessed the bootloader already? i did the usual power+vol down and it took me to a bootloader of sorts however it was all in Chinese, this makes sense to me because i ordered it from china (ebay) but when im in system info it just says .....................b118 not ..................b118cn, so does this mean im in a locked bootloader?
any sort of help would be much appreciated as I really hate this UI and hate this non vanilla crap.
Click to expand...
Click to collapse
Since i've already seen a post like this i would suggest that you download an app from play store or whatever store you have and check the phone to see if its the real deal. The apps name is CPUZ, and after you've installed it go in the app and check the version of the board that you have. It should be something like the picture i've uploaded.
This is the problem that you might have with your Chinese version of the phone http://forum.xda-developers.com/showthread.php?t=2671114
tileeq said:
Since i've already seen a post like this i would suggest that you download an app from play store or whatever store you have and check the phone to see if its the real deal. The apps name is CPUZ, and after you've installed it go in the app and check the version of the board that you have. It should be something like the picture i've uploaded.
This is the problem that you might have with your Chinese version of the phone http://forum.xda-developers.com/showthread.php?t=2671114
Click to expand...
Click to collapse
Yeah there are some differences in the cpu-z test, the first one being the 'hardware' its MT6589 and kernel architecture is armv7I, it has less internal memory and ram also and it says i have root access already. I dont have and google apps/GAPPS on my phone either
on B511 locked bootloader, fastboot unlock not working
Any way to unlock the bootloader on B511?
Tried below as per guides found in xda but still locked:
$ sudo fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.657s]
$ sudo fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.054s]
finished. total time: 0.054s
$ sudo fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.657s]
finished. total time: 0.657s
Thanks

T-Mobile OEM unlock

Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
only the EU bootloader has been unlocked, something to do with TMO releasing some keys or something for the secuity, I believe. I know on HTCs I used to have TMO had certain encryption on wifi calling and a few signatures that were broken by touching the security partition needed to gain root and install custom OSs. Once LG updates their bootloader unlock page to include TMO version G7 (I have one, too) then we'll see a KDZ thread and then root
cohan1219 said:
Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
Click to expand...
Click to collapse
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Joe199799 said:
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Click to expand...
Click to collapse
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
sharpknight said:
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
Click to expand...
Click to collapse
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
that one guy is checking the bootloader again and trying to help us ive been taking to him hope he's right about them locking it the same way give it a little time he thought bootloader was unlocked he doesn't have the device there's others we can't give up man adb root is possible prob hacking laf maybe possible and there's a way someone will get it anyone trying to I'll also help to
Joe199799 said:
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
Click to expand...
Click to collapse
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Honestly I just want it for viper4android literally that's it and maybe greenify and adaway other than that I'm good.
Honestly I probably won't switch over I'll just deal with it
20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Greenify was the biggie to me particularly with the Xposed module. Titanium Backup. Disabling system apps that the UI wouldn't let me disable. (Maybe that can be done via adb w/o root. I should try.) BootManager. MinMinGuard. Worthwhile system-wide font replacement w/o bloat. (No apps, no junk, no "apps that don't support <thing> or <favorite font>", just replacing files in /system/fonts.)
Lots of other little things that -- added together -- made my phone just that much nicer to me.
I'm really happy with my G7 all around (except for the WiFi stability, that still sucks). I just wish I had all those little tweaks back.
I made a post about a week ago but never got any replies. Has anyone else ran the "fastboot flash unlock_critical" command? My phone restarts and shows the erasing screen but no actual bootloader unlock.
Any updates?
I'll try out when I make it back home sorry was flooded here we either need to mod kernel or laf aand github has a repo on some I'm checking on I'll be able to check more sorry and package disable pro will freeze apps or use autoprimes way on rooted you can use twrp file manager to delete system apps on moto z2 oem can't be touched but there's ways
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
ecompton59 said:
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
Click to expand...
Click to collapse
What are the different commands?
Okay I've tried the fastboot critical command same went to erase screen with the circle but fastboot flashing get_unlock_ability comes back 1 I've extracted kdz to dz still playing around trying
sign the petition to LG
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
There is an option for the T-Mobile version. Can someone actually try continuing with the progress?
I can't since I don't have the T-Mobile version.
LGM710TM is LG G7 from Italian provider TIM.
It has nothing to do with T-Mobile.
awww
umminkug said:
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
Click to expand...
Click to collapse
There's been petitions for like every locked-down LG device since the beginning of time. Never has it been effective, never will it be. LG doesn't reverse its bootloader locking policy.

Skipsoft unable to unlock my bootloader? Trying to root

Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...

[DEV] Bootloader unlock development

You can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (cheaper but FunkyHuawei is more certain)
As most of you already know, Huawei stopped giving away bootloader unlock codes. So it is up to us, to hack our way to root and custom ROMs.
Following, are a few things we could try,
Also, I own a Nova 3i currently. There are always the possibility that something working for me won't work for you, because of different chipsets, but I guess that this forum is also for the development of Nova 3i.
NOTE THAT SOME OF THE FOLLOWING ARE PAID SERVICES. I'M NOT RELATED WITH ANY OF THEM.
+DC-Unlocker:
I tried the latest version, got an unknown error 375. (This error also goes for the latest versions of P20 Pro, Mate 10, etc.). And the developers said that they won't support any new Huawei phones, and that they'll leave new Huawei phones for HCU-Client, because the two services are related.
+HCU-Client:
You can't try this without buying credits. If you feel generous, go on and try this. They released a couple of new versions in this week.
+Bootloader exploiting:
I really don't know anything about this, feel free to contribute.
+Secret Fastboot backdoors:
There can be a LOT of these, considering that there are a family of commands under <fastboot oem backdoor>. And I discovered quite a lot of secret commands, almost every one of them sounding like that they could seriously brick the device. For example, consider what <fastboot oem djtagtosd> sounds like. (Search Google for JTAG) If you would like to test some of the less-dangerous looking ones, please PM me, even an old Huawei device is okay as long as it has a Kirin chipsets.
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
waltermsalomon said:
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
Click to expand...
Click to collapse
Sorry, did not see this. So, this tool installs TWRP without unlock codes? Still we need to get TWRP compiled.
Huawei nova 3i rom
Dears I need stock firmware and flash tool officially for Huawei Nova 3i ine-lx1
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
jioleight said:
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
Click to expand...
Click to collapse
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
mandated but no one is enforcing it so huawei will just delay the relase of the kernel source until the insterest has died out.
nope, not gonna take that risk :laugh:. $55 seems cheaper until it's converted to my country's currency. haha.
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
Another one source to unlock bootloader - $22
This method has already been tested on 4pda. Working TWRP can be taken from here
And HCU doesn't have NOVA 3 support yet to read the unlock code now
OEM Unlock option
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat? (the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country).
Or do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Jan oatcoal said:
Do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Click to expand...
Click to collapse
Yep. It is like this when you issue the command in fastboot to unlock:
Without code and without enabling the toggle: Gives and error telling to turn on the toggle.
With code and without enabling the toggle: Same as above
Without code and toggle enabled: Error wrong password
With both: Success
I think we are lucky on that side, I think that the toggle is also disabled on Mate 20 series. So we can unlock the bootloader. with external sources for now, so it may be a good idea to block OTA updates.
Ine-lx2 8.2.0.131(c636)
*update*
so i checked using fastboot oem get-bootinfo. lo and behold it's really unlocked.
jioleight said:
does Phone Unlocked mean the bootloader or just the GSM part that is unlocked?
Click to expand...
Click to collapse
I did this then installed titanium backup and it said it wasn't rooted.
meekspace said:
I did this then installed titanium backup and it said it wasn't rooted.
Click to expand...
Click to collapse
you have to root first by installing magisk or supersu. and it needs twrp to root. in case of nova 3i there isnt any existing twrp. only on nova 3 since it has the same soc as p20pro.
was about to test it on my nova 3i. good thing i checked the specs of nova 3 first before proceeding.
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
jioleight said:
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
Click to expand...
Click to collapse
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Supersonic27543 said:
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Click to expand...
Click to collapse
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
jioleight said:
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
Click to expand...
Click to collapse
What if we try obtaining a code by one of the third party methods and try that? Maybe they just forgot or didn't care to set the variables you saw there as this is a new chipset. I think it is not really unlocked, if it was the phone will display the "Your device has been unlocked and cannot be trusted" message on boot.
Looks like what I said before is true. fastboot oem lock-state info returns USER Locked.
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
stevefwt said:
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
Click to expand...
Click to collapse
They are just copy pastes and no longer works as of Huawei stopping providing codes.
Google should try to remove them from coming at top of Google searches, IDK.

How To Guide After Update Bootloop Fix

Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.

Categories

Resources