Hi,
I have tried almost every thing to start my asus zenfone 6 (a601cg) which is stuck on fastboot. tools such as xFSTK, Asus Flash tool when ever i run "fastboot oem partition /tmp/partition.tbl" command it gives an error of "FAILED (remote: GPT command failed)". even i have tried some oem commands which failed showing "unknow OEM command". i think its a fastboot issue & i tried to change my fastboot via xFSTK tool which runs properly & status is successful but i think its not updating the fastboot.
Kindly help badly stuck into this.
pratikdoshi4u said:
Hi,
I have tried almost every thing to start my asus zenfone 6 (a601cg) which is stuck on fastboot. tools such as xFSTK, Asus Flash tool when ever i run "fastboot oem partition /tmp/partition.tbl" command it gives an error of "FAILED (remote: GPT command failed)". even i have tried some oem commands which failed showing "unknow OEM command". i think its a fastboot issue & i tried to change my fastboot via xFSTK tool which runs properly & status is successful but i think its not updating the fastboot.
Kindly help badly stuck into this.
Click to expand...
Click to collapse
Hey there same problem here but i got a zenfone 2 ze550ml. I tried an oem token commad and same result. Did you fix your phone?
Related
Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Thanks!
Canuckfan101 said:
Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Click to expand...
Click to collapse
What are the actual files you have downloaded called? It could be: system.img_sparsechunk1 - also flash them in order, system.img_sparsechunk0, system.img_sparsechunk1, system.img_sparsechunk2
Hi! Thanks for the reply! I checked the name and I did not enter it in correctly! It now works! But antoher problem has occured! I managed to lock the device ( i ended the program with fastboot oem lock) and the moto g said locked! in blue. I thought it got stuck so i pressed the power button. The warning unlocked bootloader still shows but the phone is Locked Status 2. The CMD prompt gave me this when I entered fastboot oem lock
Code:
...
FAILED (status read failed (too many links))
There are already numerous threads on the subject of 'fastboot oem lock failed' - I don't know why it fails.
This is one alternative solution:
http://forum.xda-developers.com/showthread.php?t=2548530
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
wiliestseven51 said:
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
Click to expand...
Click to collapse
Edit: Downgrading is not an easy task. My understanding is you will first need to downgrade your firmware, then flash a compatible RUU. I believe this requires you to be s-off.
As far as the backup you mentioned, well that's what TWRP is for. First you'll need to unlock your bootloader which you can do by following the instructions from the htcdev website (understand this will factory reset your phone). Then find the TWRP thread which will have instructions on how to temporarily boot TWRP or permanently install TWRP to your phone's boot partition. Within TWRP you can perform the backup you desire. There is a learning curve to all of this. Good luck.
RUU download here --> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
About backup,if you are rooted, use twrp recovery o titanium backup app,otherwise google drive backup
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Maybe this could help though
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
wiliestseven51 said:
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Click to expand...
Click to collapse
I use HTC windows driver version 4.10 and the fastboot binaries from step 4 of the unlock bootloader process. I've never had to make the choice you are describing.
Sounds like you are basically on the last step of the procedure, no?
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
wiliestseven51 said:
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
Click to expand...
Click to collapse
You have got oem unlock & adb debugging set in developers option sliders on? Try "adb reboot" command, see if your adb has been authorised on yr PC. I had a dodgy lead, using usb3 port, using shell instead of cmd cause similar problems
I have a Nokia 6.2 with bootloader unlocked..
I flashed phone with Nokia-Tool. All working fine..
I wanted to lock bootloader and used command: "fastboot flashing lock" before "lock_critical"
Phone then rebooted into fastboot and is stuck there. No matter what i do, it returns to fastboot mode, except if i choose Power Off. Then it shuts down.. If i try recovery, it reboots into fastboot again.
If i try "fastboot flashing unlock" it returns
" FAILED (remote: 'unknown command')
fastboot: error: Command failed "
I have also tried "fastboot oem-unlock "
When i check status.
"fastboot flashing get_unlock_ability" returns. "(bootloader) get_unlock_ability: 1"
I did not use "fastboot flashing lock_critical" before lock bootloader. So unlock_critical is still open.
Is there a command to unlock bootloader again? Or am i using wrong commands ?
Hello bro same thing happened with me in my 7.2. do you have any solution?
Hello,
I'm trying to bootloader unlock this phone and have encountered the above error. I am using the OEM cable, and basic ADB commands work (adb reboot ______, etc.) The command fastboot oem device-info yields the same error message. I'm thinking I don't have the right USB drivers but the phone is so new I can't find anything for it.
Do you guys have any ideas?
Boyo Synth II said:
Hello,
I'm trying to bootloader unlock this phone and have encountered the above error. I am using the OEM cable, and basic ADB commands work (adb reboot ______, etc.) The command fastboot oem device-info yields the same error message. I'm thinking I don't have the right USB drivers but the phone is so new I can't find anything for it.
Do you guys have any ideas?
Click to expand...
Click to collapse
Getting the same error, OnePlus 10 Pro NE2213
dev options enabled, OEM unlock checked, debugging enabled
device is seen in 'fastboot devices':
c:\adb>fastboot devices
84250aa3 fastboot
c:\adb>fastboot oem unlock
...
FAILED (remote: Unable to open fastboot HAL)
finished. total time: 0.002s
same happens with me.....IQOO Neo 6...
C:\Users\*****\Desktop\A13\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Under developer options set the OEM unlocking ON
Hey all,
Trying to unlock Bootloader on Doogee X95. I've managed to get as far as selecting yes to unlock bootloader from fastboot mode however it fails. When pressing vol up it says "unlock failed" with no further reason then returns to fastboot menu.
In the cmd window the following was printed:
fastboot flashing unlock
<bootloader> start unlock flow
FAILED (remote: '
Unlock operation is not allowed
'>
fastboot: error: Command failed
Any ideas on what might be going on? Is this just one of those phones that do not allow for bootloader to be unlocked?
I've accidentally rebooted into fastboot mode menu rather than bootloader once and the info on bootloader it had was:
Bootloader version - Unknown
Trying to see if I can flash full/original android onto it to replace android go it has from manufacturer to open display over apps feature.