BND-L34
My phone is bricked, I lost my drivers, and I lost the unlock code.
I deleted TWRP, and I need BND-L34 drivers to relock the bootloader.
I can't get into fastboot mode without adb drivers.
I plan on using the dload method after I relock the bootloader.
I also need the unlock code back, or a new one because I think my
huawei account was deleted.
I need:
link to BND-L34 drivers adb, fastboot
and a method to relock and reunlock the bootloader.
The goal is to get working fastboot, adb.
And I'm supposed to be fine after I get the drivers.
And the last goal is to get the bootloader relocked,
so I can get the phone unbricked, then unlock it after.
I tried installing the update.zip and other zips in TWRP but it wouldn't work.
Anyways thanks. :good:
tomjfmu said:
BND-L34
My phone is bricked, I lost my drivers, and I lost the unlock code.
I deleted TWRP, and I need BND-L34 drivers to relock the bootloader.
I can't get into fastboot mode without adb drivers.
I plan on using the dload method after I relock the bootloader.
I also need the unlock code back, or a new one because I think my
huawei account was deleted.
I need:
link to BND-L34 drivers adb, fastboot
and a method to relock and reunlock the bootloader.
The goal is to get working fastboot, adb.
And I'm supposed to be fine after I get the drivers.
And the last goal is to get the bootloader relocked,
so I can get the phone unbricked, then unlock it after.
I tried installing the update.zip and other zips in TWRP but it wouldn't work.
Anyways thanks. :good:
Click to expand...
Click to collapse
There was a post on XDA 7X Telegram group by nahil stating he retrieved his unlock code from the bash history on his phone.
adfurgerson said:
There was a post on XDA 7X Telegram group by nahil stating he retrieved his unlock code from the bash history on his phone.
Click to expand...
Click to collapse
Okay thanks, how will i get the drivers? I can't access my phone on my ADB on my PC anymore, I reinstalled my OS on my PC, idk if that has to do with it. Also where is this post? And what is bash history?
tomjfmu said:
Okay thanks, how will i get the drivers? I can't access my phone on my ADB on my PC anymore, I reinstalled my OS on my PC, idk if that has to do with it. Also where is this post? And what is bash history?
Click to expand...
Click to collapse
Also, the splash2 partition is the bootloader log section.
I found , but have not tried yet. A possible way to pull images from device without twrp
"fastboot oem dump emmc "partition name" "save location" "
If you can get that partition out and grep it for "unlock" perhaps you will find your code.
No special drivers are needed. Generic adb/fastboot drivers should be fine.
Search xda for 5 minute minimal adb /fastboot
tomjfmu said:
Okay thanks, how will i get the drivers? I can't access my phone on my ADB on my PC anymore, I reinstalled my OS on my PC, idk if that has to do with it. Also where is this post? And what is bash history?
Click to expand...
Click to collapse
Installing hisuite would probably be an easy way to get the drivers. I don't have a clue how to get to The Bash or search it.
adfurgerson said:
Installing hisuite would probably be an easy way to get the drivers. I don't have a clue how to get to The Bash or search it.
Click to expand...
Click to collapse
Bash history would only be of you are on Linux.
And to top has said he recently reinstalled his whole PC OS, so there would be no history anyway..
My finding of the unlock code on the splash2 partition seems to be possibly a dead end as I think the log file is overwritten
mrmazak said:
Bash history would only be of you are on Linux.
And to top has said he recently reinstalled his whole PC OS, so there would be no history anyway..
My finding of the unlock code on the splash2 partition seems to be possibly a dead end as I think the log file is overwritten
Click to expand...
Click to collapse
Thank you for that, I've never used Linux and Windows only if I must.
adfurgerson said:
Installing hisuite would probably be an easy way to get the drivers. I don't have a clue how to get to The Bash or search it.
Click to expand...
Click to collapse
When I plug the phone in and I have hisuite, I kinda don't have an os on my phone, like I said I was bricked. Is there another way besides the Hisuite?
does huawei have mate se adb drivers or anything on their website? Also is their a way I can re-get the unlock code back without history
if you installed hisuite than you have the drivers.
darkmage1991 said:
if you installed hisuite than you have the drivers.
Click to expand...
Click to collapse
It isn't recognizing it.
And that explains why the adb and fastboot doesn't work.
Update: I sent it in, and it's being fixed for me.
Related
Hi I have a problem with my zenfone2. Not allow me to unlock the bootloader with the asus utility. I said unlock fail. I can do to unlock
Use one click bootloader unlock
Where I can find it. The detail esque me not detect the phone adb. You can install drivers
jufragur said:
Where I can find it. The detail esque me not detect the phone adb. You can install drivers
Click to expand...
Click to collapse
Here One Click Bootloader Unlock
Your usb debugging must enable,and allow when prompted at phone screen.
Dont forget to install minimal adb also,you can search forum.
Also driver dont forget install.
But first please try apk below first.
And I tried out the apk and fail unlock. I'll try again with the xq program I want to install a rom
Yess try unofficial one click unlock instead official one because official one recorded to asus server and void warranty when you relock.
as I can tell if the phone is unlocked. use one click to unlock bootloader. but I can not ride the recovery when I put it in bootloader. I would not dectecta pc with adb devices
Trying to get ADB to find my device but it wont.
I tried a comment to reboot bootloader but it cannot find device.
I have it Rooted and bootloader unlocked.
Here is what I get
Solved: http://forum.xda-developers.com/showpost.php?p=67600314&postcount=142
Jaymie1989 said:
Trying to get ADB to find my device but it wont.
I tried a comment to reboot bootloader but it cannot find device.
I have it Rooted and bootloader unlocked.
Here is what I get
Click to expand...
Click to collapse
You need to install ADB drivers, I had the same issue yesterday. PM
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
I have the unlock bin but it in c drive in fastboot but won't work
Gm, were u able to get unlocked ? Im waiting for my token also
mongonexus said:
Gm, were u able to get unlocked ? Im waiting for my token also
Click to expand...
Click to collapse
Yes I got it I was rushing and copy pasting instead of actually reading it.very simple
rob420p said:
Yes I got it I was rushing and copy pasting instead of actually reading it.very simple
Click to expand...
Click to collapse
How to get it ?
caligood3 said:
How to get it ?
Click to expand...
Click to collapse
I have to apply threw OnePlus after tmoble sim unlocks your device look up OnePlus bootloader unlock I. Your browser
rob420p said:
I have to apply threw OnePlus after tmoble sim unlocks your device look up OnePlus bootloader unlock I. Your browser
Click to expand...
Click to collapse
I've done all this my only problem is when I go into fastboot it doesn't detect my phone I have adb drivers installed it connects to my phone when it's on but in fastboot it doesn't any idea ?
caligood3 said:
I've done all this my only problem is when I go into fastboot it doesn't detect my phone I have adb drivers installed it connects to my phone when it's on but in fastboot it doesn't any idea ?
Click to expand...
Click to collapse
What does "fastboot devices" show when you run that command? Try reinstalling drivers.
R800x_user said:
What does "fastboot devices" show when you run that command? Try reinstalling drivers.
Click to expand...
Click to collapse
Nothing so I try adb devices & it runs but didn't detect my phone when I do it with the phone on it detects my phone
rob420p said:
I have to apply threw OnePlus after tmoble sim unlocks your device look up OnePlus bootloader unlock I. Your browser
Click to expand...
Click to collapse
I just sent in my unlock code to OnePlus yesterday evening, how long do I have to wait for them to respond?
Inous said:
I just sent in my unlock code to OnePlus yesterday evening, how long do I have to wait for them to respond?
Click to expand...
Click to collapse
A entire week, it will be at the same time you sent the request
I figured it out also waiting for my code
caligood3 said:
I've done all this my only problem is when I go into fastboot it doesn't detect my phone I have adb drivers installed it connects to my phone when it's on but in fastboot it doesn't any idea ?
Click to expand...
Click to collapse
ran into the same issues. uninstalled OnePlus drivers via device manager and installed generic Android drivers and my PC was able to recognize my phone via fastboot
jAm-0 said:
ran into the same issues. uninstalled OnePlus drivers via device manager and installed generic Android drivers and my PC was able to recognize my phone via fastboot
Click to expand...
Click to collapse
Yea I got it now you have to enable it in device manager when the phone is in the bootloader then it should work
Hello XDA-Developer-Forum!
I think I have messed up my new phone XQ-BT52.
I followed the instructions on this thread https://forum.xda-developers.com/t/how-to-root-and-pass-safetynet-on-xq-bt52-62-0-a-3-163.4408851/ and all worked fine.
But then I wanted to have R/W on System and started there. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/
I wanted to flash the image with fastboot, but had problems with the drivers.
Somehow I had the bad idea to issue fastboot oem lock
Now my device is locked again. I managed to get into recovery and made a wipe data / factory reset.
I cannot flash with fastboot, because the device seems to be locked.
The same happens with adb sideload.
Can I unlock the bootloader again?
Or can I flash the version of stock android 12 with adb sideload (I read that this would work with locked bootloader too)?
But adb sideload works only with zip-files. How to create a signed zip from XQ-BT52_Customized EEA_62.1.A.0.533?
Any help is really appreciate!
Thankx in advance!
It sounds like maybe your system partitions got messed up? Go into flashboot mode and try using newflasher with just the super.sin file from the downloaded firmware.
Make sure you use a super.sin from the same firmware you had on the phone when this happened.
Flashing official images should work even if the device is locked, because they're signed by Sony.
Thank you for your reply wirespot!
I guess flashing would not be not be possible, because the phone is locked.
However, I managed to repair the phone with Xperia Companion.
Selected "Device not detected" and connected with volume up or down pressed (cannot remember).
And it worked!
I removed unneeded apps with adb shell and pm uninstall -k --user 0 NameOfPackage.
Glad to have my new phone back.
Thankx again.
Please, did you find an answer to your question about unlocking again?
I am going through some issues with my 10III too and I want to try locking the bootloader, and going the Companion way as you did. But, once everything is repaired, I will need an unlocked bootloader again.
marbalf said:
Please, did you find an answer to your question about unlocking again?
I am going through some issues with my 10III too and I want to try locking the bootloader, and going the Companion way as you did. But, once everything is repaired, I will need an unlocked bootloader again.
Click to expand...
Click to collapse
Yes you can unlock BL after
King081 said:
Yes you can unlock BL after
Click to expand...
Click to collapse
Thank you!