Can anyone offer a little assistance please?
I took delivery of my 3rd replacement G4 this afternoon and I'm trying to unlock the bootloader which hasn't been an issue on any of the past 3 devices.
First up, I managed to get the device id, get the unlock.bin from LG but couldn't get the device to respond to any fastboot commands (it was just stuck at "waiting for any device"). After an hour or so of pissing about with drivers, fastboot can now see the phone using the "fastboot devices" command, but when I attempt to flash the unlock.bin file, I receive the below -
Code:
C:\sdk-tools>fastboot flash unlock unlock.bin
target didn't report max-download-size
sending 'unlock' (1 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s
It doesn't appear to respond to other fastboot commands now either. "fastboot oem device-id" returns -
Code:
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
"fastboot reboot" looks to reboot the device and the on screen command prompt claims to have rebooted the phone successfully, but the phone doesn't reboot.
I've tried different cables, different ports to no avail. I could try another PC but it's in my sons room and he's asleep at the moment. Both PC's are running Windows 10.
Any other ideas?
It's an EE Branded device and according to the LG Info app, the serial number begins with 609 if that's important.
Please disregard, after uninstalling LGUP, the associated dll file and using an alternative version of fastboot (specifically the version included in this)., I've just managed to flash the unlock key and my G4 is unlocked.
Same here sir
I am trying to flash recovery in my Asus Zenfone max Pro m1 .this error shows ..plzz help any fix I am using windows 10PC
Chetancm said:
Same here sir
I am trying to flash recovery in my Asus Zenfone max Pro m1 .this error shows ..plzz help any fix I am using windows 10PC
Click to expand...
Click to collapse
Um... This is LG forum.
For your device check this: https://forum.xda-developers.com/asus-zenfone-max-pro-m1
Related
Hi guys,
Basically I'm in a bit of trouble trying to get my one x back to stock. After running the RUU for my phone, it exited with an error saying that the device suddenly could not be found anymore. After this I tried to run the RUU again but now the error message about the battery level being below 30% came up. Anyway, after this I tried unlocking my phone again to go back to a custom rom and at least have a working phone however I can't do anything through fastboot because no matter what command I type in, it keeps telling me the following:
C:\fastboot>fastboot getvar version-main
getvar:version-main FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
C:\fastboot>fastboot oem readcid
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
I checked the usb connection and the device seems to be recognized:
C:\fastboot>fastboot devices
HT24CW105437 fastboot
Could someone help me as to how to move forward? I also can't seem to charge my phone. I left it on AC charging for about an hour in fastboot mode and tried running the RUU again but the same battery level message came up.
Thank you!
uxyyy
For CID command is:
Fastboot getvar cid
For flashing:
Fastboot flash boot boot.img
Fastboot flash recovery recname.img
Cache clearing:
Fastboot erase cache
Sent from my HTC One X using Tapatalk 2
Hey,
Yeah I know the commands but unfortunately I wasn't kidding when I said I can't do anything via fastboot. :/
Even just trying to get the CID or flashing the boot.img returns:
C:\fastboot>fastboot getvar cid
getvar:cid FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4862 KB)...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
So there must be something else that's broken.
Try this..Download fastboot files again,put phone in fastboot..And on fastboot files hold shift and right click and open command prompt here..
Sent from my HTC One X using Tapatalk 2
Still the same problem.
Also, I left my phone to charge overnight and got the green LED to light up however when trying to run the RUU it still tells me that the battery level is below 30%.
Any fastboot commands still return the exact same error message as before. I honestly don't know what I could do atm.
OK I have a problem. Till now:
1. Installed drivers
2. Bootloader unlocked
3. ADB enabled. PC authorised.
4. OEM unlocking permitted confirmed.
5. Command fastboot devices shows phone connected in fastboot mode.
EDIT: Solved. Experimented with different drivers on different laptop.
Now trying to send official twrp with command fastboot flash recovery recovery.img and I get error:
sending 'recovery' (18680 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
Can't seem to get a solution to this
Any help?
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.
I'm having trouble figuring out why I can't unlock in fastboot.
I'm SIM unlocked; I confirmed this in the settings.
I got my unlock token from oneplus' website via email eariler today
OEM unlocking is checked in the developer settings
USB debugging enabled
Running most recent adb/fastboot tools I could find
I boot into fastboot and run the command - fastboot flash cust_unlock unlock_code.bin - and get the following error:
PS C:\Users\juann\Desktop\Root\platform-tools> fastboot flash cust_Unlock unlock_code.bin
target reported max download size of 805306368 bytes
sending 'cust_Unlock' (0 KB)...
OKAY [ -0.000s]
writing 'cust_Unlock'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: -0.000s
Any ideas?
command your using is wrong..
"fastboot flash cust-unlock unlock_code.bin"
Libra420T said:
command your using is wrong..
"fastboot flash cust-unlock unlock_code.bin"
Click to expand...
Click to collapse
…
man I hate myself sometimes. Thank you so much. Fwiw I wear glasses but wasn’t using them last night. Do you have a PayPal so I can send you some dough for looking through this for me?
So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b