Related
i accedently flashed stock recovery as in ramdisk recovery partition in twrp, now there no recovery , please help !
Flash stock recovery again!
In fastboot mode type: fastboot flash recovery_ramdisk recovery.img.
BS4388 said:
Flash stock recovery again!
In fastboot mode type: fastboot flash recovery_ramdisk recovery.img.
Click to expand...
Click to collapse
yeah sir i know , but my frb is locked and even cant enable in settings , oem option is untouchable , it cant be enabled , please help , wht should i do , and also i am on kingvip rom
Snober said:
yeah sir i know , but my frb is locked and even cant enable in settings , oem option is untouchable , it cant be enabled , please help , wht should i do , and also i am on kingvip rom
Click to expand...
Click to collapse
In this case I am unable to help you, but you can use dc-unlocker paid service.
It is here:
https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Sorry I never used it so can't give more information, you have a look and decide.
@Snober
you have now FRP-Lock ?
have you twrp/backup from last state (before install kangvip)
then test twrp/restore and look if phone work FRP=unlock
it is better if you need help - give more info : what is your build ? LLD-xxxxxxxx / what is delivered OS ( first delivered "7.xx", current "8.xx")
JamesBott said:
@Snober
you have now FRP-Lock ?
have you twrp/backup from last state (before install kangvip)
then test twrp/restore and look if phone work FRP=unlock
it is better if you need help - give more info : what is your build ? LLD-xxxxxxxx / what is delivered OS ( first delivered "7.xx", current "8.xx")
Click to expand...
Click to collapse
No sir i don't have backup of last state. And i can't go to twrp as i installed stock recovery
My build is 8.0.0142 c675 indian version
Now there is another problem now. I searched for solutions and got the answer as to relock bootloader. Then i relocked it with fastboot cammand. Now the phone is bricked and restarting to erecovery after honor logo. Currently status is phone relocled and frp lock in fastboot.
Please help
@Snober
sorry, now you have big problem !
Relock Bootloader is the greatest Bull**** by phones ! (my opinion !) if you relock bootloader WITH damage-rom you have a "damage-phone" !!!
please search "repair bootloop with bootlooder relock".
for future if your phone again work
- unlock bootloader AND let it open
- download your build FULL-Update (now you have backup for repair - if needed)
this 2 point's is very important
i think you have 1 chance to self-repair : search "recovery_ramdisk_BKL-L04_nocheck.img"
but - this is no simple. you must read and understand before you do ! I DONT KNOW if this work for you !!!
@JamesBott
Isn't it possible to unlock the bootloader again after relocking?
@BS4388
usually yes, but if you relock bootloader WITH damage-rom you have a "damage-phone" !!!
that's the point. if user install dev-rom and this work not 100% good AND then relock bootloader ...
if now bootloader locked - you need "fastboot flash oem unlock your-unlock-code"
if you have FRP-lock you dont can "fastboot flash xyz"
my friend have many "help me" from other user with this problem
he found the way with "recovery_ramdisk_BKL-L04_nocheck.img" and say - this work only if on phone twrp installed BEFORE error AND boot to twrp work
usually you can bootloder unlock and relock with your-unlock-code many (not once only)
JamesBott said:
@BS4388
usually yes, but if you relock bootloader WITH damage-rom you have a "damage-phone" !!!
that's the point. if user install dev-rom and this work not 100% good AND then relock bootloader ...
if now bootloader locked - you need "fastboot flash oem unlock your-unlock-code"
if you have FRP-lock you dont can "fastboot flash xyz"
my friend have many "help me" from other user with this problem
he found the way with "recovery_ramdisk_BKL-L04_nocheck.img" and say - this work only if on phone twrp installed BEFORE error AND boot to twrp work
usually you can bootloder unlock and relock with your-unlock-code many (not once only)
Click to expand...
Click to collapse
Well, I think @Snober can still revive his H9L by flashing a stock firmware using a paid service such as dc-unlocker bypassing the frp lock.
@BS4388
i dont know if dc-unlocker work with frp lock.
but i think it is a test worth - only it cost 15€ (ca. 15$) (if not work only 15€ lost - new phone cost 230€ [in germany])
i think if it's not work, dc-unlocker rewrite money to user-account. but my last dc-unlocker use a little time before now
I am sending my phone to friend as there is no service center in my location .
Should I send .
Can the phone be warranty as my phone status in fastboot is phone relocked and frp lock .
Will they detect the phone was unlocked or something like that . I mean will any problems comes . ?
Got My phone repaired in service center for free. They didn't see as the phone was in relocked state. So happy ?
this is very very good for you
BEFORE you any things do in future with your phone - YOU NEED FULL-UPDATE on your PC
JamesBott said:
this is very very good for you
BEFORE you any things do in future with your phone - YOU NEED FULL-UPDATE on your PC
Click to expand...
Click to collapse
Yeah, i know now, thats why i will not do anything stupid till then!!,Thanks for the support
Snober said:
my frp is locked, oem option is untouchable
Click to expand...
Click to collapse
Snober said:
Got My phone repaired in service center for free
Click to expand...
Click to collapse
For future reference: Stock ROM appears to require a network connection in order to enable FRP, so, connect with WiFi and it should become touchable.
noobington said:
For future reference: Stock ROM appears to require a network connection in order to enable FRP, so, connect with WiFi and it should become touchable.
Click to expand...
Click to collapse
Nah. Tried that. Not working
Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.
sriram reader said:
Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.
Click to expand...
Click to collapse
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone
2gg1 said:
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone
Click to expand...
Click to collapse
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,
I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone
TG09 said:
I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone
Click to expand...
Click to collapse
read my post above...
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
sad?
For unlock Bootloader, u will need to downgrade to oreo than need bootloader key... minimul adb to unlock it with the key.
Sent from my TA-1054 using Tapatalk
Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
READ MY POST ABOVE...
BTW: i think, this thread not too long
k3dar7 said:
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,
Click to expand...
Click to collapse
Hm...
So what you're saying is that there are no Nokia 7 Plus' that have an unlockable bootloader? Or, to put it another way, do all Nokia 7 Plus' have the option "OEM unlocking" set to off? With no way of switching it on?
Or is there a way to switch it on?
I have booted into download mode, and fastboot flashing unlock, but it returns 0 or failed to unlock.
oh wait... I saw your other post: https://forum.xda-developers.com/showpost.php?p=78764676&postcount=3 In reference to the first item, the website is hikaricalyx?
---------- Post added at 12:18 PM ---------- Previous post was at 11:55 AM ----------
Ok... so... for Nokia 7 Plus...
I need to download ntools, HMD rom for version 8, android 8, adb/fastboot.
Then downgrade to version 8.
Flash HMD version 8 rom. (But how do I flash when it's still locked? Or does downgrading to 8 allow the option oem unlocking to be turned on?)
Unlock bootloader.
Use magisk to get root.
Is that the steps? Or am I missing something?
Search for techmaesto.
techmesto dot com/how-to-downgrade-nokia-7-plus-from-stable-pie-to-stable-oreo/
I'm using that guide, and I get up to the part where I update via SD card. But it says that the update package is older than the current build and downgrade not allowed.
What can be done about this?
Anyone know if Nokia will ever allow the bootloader to be unlocked?
ardvarkmcgark said:
Anyone know if Nokia will ever allow the bootloader to be unlocked?
Click to expand...
Click to collapse
Maybe.. N7+ is almost at his end of updates. So we have a little chance that they will do that like the nokia 8
downgrade android 8, inbox
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
md sabuj said:
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
Click to expand...
Click to collapse
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
zgfg said:
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Click to expand...
Click to collapse
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
md sabuj said:
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
Click to expand...
Click to collapse
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
zgfg said:
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
Click to expand...
Click to collapse
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
md sabuj said:
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
Click to expand...
Click to collapse
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work
Click to expand...
Click to collapse
Thank you?
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
Click to expand...
Click to collapse
How much credits I have to buy from DC Unlocker for bootloader code?
md sabuj said:
How much credits I have to buy from DC Unlocker for bootloader code?
Click to expand...
Click to collapse
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have contact page and ask them directly
zgfg said:
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have a contact page and ask them directly
Click to expand...
Click to collapse
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
md sabuj said:
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
Click to expand...
Click to collapse
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
zgfg said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
Click to expand...
Click to collapse
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
md sabuj said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
Click to expand...
Click to collapse
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I have already applied Network Patch, See my both SIM is working.
Right now I don’t need Root so I'm skipping Magisk.
I just want to disappear the update available Notification, if the update is Safe I'll go for it.
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
md sabuj said:
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
Click to expand...
Click to collapse
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
???
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
md sabuj said:
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
Click to expand...
Click to collapse
It's not possible to remove the warning on booting "Your device has been unlocked and can't be trusted" (IMO, it must have been commented somewhere in the OP) - that's price for the unlocked Bootloader.
But you must not relock Bootloader - it would trigger Hard reset, removing Network patch (even worse, it could also cause soft brick if TWRP or Magisk are installed)
15 credits for unlock in fastboot mode (not pay over sms)
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.
My rog 3 tencent version is not unlocking bootloader, bootloader is failed to unlock your device plz help me
How did you attempt to do it? Steps please.
Same issue here. Previously I was just downloading the Unlock Device app here and running it. (I already had developer options enabled) and the device would reboot but not do anything (I reckon I tried 10+ times). Since then I formatted the device and tried again and got the same results so I set the device backup normally today (running build 18.0410.2108.158) and tried it again (with and without developer options enabled as I forgot to check) and I just get a standard error message saying it couldn't unlock my device and to try again later. Same result multiple times. I don't see any option for OEM unlocking in Dev options which I see some people mention. I'm updating to the latest OS I can see in the link I provided and I will try again after installing that.
I'm updating to the latest OS I can see in the link I provided and I will try again after installing that.
Click to expand...
Click to collapse
Or not as it fails saying System update fails immediately after I select the update file and press go. :/
Qabala said:
My rog 3 tencent version is not unlocking bootloader, bootloader is failed to unlock your device plz help me
Click to expand...
Click to collapse
Hello
Your phone has already been unlocked earlier and has the flag removed. Someone blocked it again for sale.
So you won't do anything with Asus tools.
I recommend the EDL mode
Regards