My phone is a Vodafone Smart 4 Turbo which a rebranded Coolpad 8865U.
I am trying to root it using the ro.secure=0 methods as all the other rooting exploits failed.
Fastboot seems to detect my phone well enough. I can run this command for example:
Code:
fastboot oem device-info -i 0x1ebf
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
However if I try to flash recovery it hangs at
Code:
writing 'recovery'...
and if I try to boot from both and original or modified boot.img it hangs at
Code:
booting...
And if I try to erase something it hangs aswell.
Any ideas of what it is going on? I cannot even figure out how to put fastboot in verbose mode to see if there are any errors or anything.
BTW: All troughout this fastboot crap the phone remained perfect functional. The only change was the personal info that got deleted when I unlocked fastboot.
Also these don't work either
Code:
fastboot -i 0x1ebf oem disable-console
fastboot -i 0x1ebf oem enable-console
fastboot -i 0x1ebf oem dmesg
but these do
Code:
fastboot -i 0x1ebf oem disable-charger-screen
fastboot -i 0x1ebf oem enable-charger-screen
And getvar
Code:
fastboot -i 0x1ebf getvar all
all:
finished. total time: 0.002s
returns empty.
This thread looks similar and a method is mentioned briefly http://forum.xda-developers.com/general/help/vodafone-smart-4-turbo-qs-t2852827
However your question may have better luck in this thread http://forum.xda-developers.com/showthread.php?t=2257421
Unfortunately there's next to no support for this device so these methods your trying may not even be legit
Good luck to you
I looked into those thread. The problem I have is not with fastboot not recognizing my phone. It does. It just hangs when it tries to boot/flash/erase.
i am getting this
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot -i 0x2A96 oem devices
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot -i 0x2A96 oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot devices
73face0a fastboot
C:\adb>
any help to fix this or reset everything !
i did this as before it was not detecting at fastboot due to driver issues : https://forum.xda-developers.com/yu-yuphoria/help/flash-twrp-yu-yuphoria-yu5010a-t3628611
but later i fixed driver issue, hope that is not causing any problem
Try . fastboot OEM unlock
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando
velocity86 said:
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando Tapatalk
View attachment 4942543
Click to expand...
Click to collapse
Cannot open the attachment. Anyway, did you resolve - if not, do you remember what was your firmware version and to which version you were trying to upgrade?
Do you have ADB/Fastboot tools installed to PC - if not, you can find on XDA Minimal ADB and Fastboot
Boot the phone to Fastboot (switch the phone off, connect by USB to PC, press and keep pressing Vol- and boot by Pow).
In Fastboot screen, does it show at the bottom that Phone (Bootloader) is locked (in green) or unlocked (red), also does it show that FRP (OEM) is locked or unlocked (you can also attach a photo)
Execute the following Fastboot commands and provide the results back (not from the first command - it's just to check if PC is connected to the phone)
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Thanks for the help. I hope to resolve the problem
C:\ADB>fastboot devices
AHK7N16B02001730 fastboot
C:\ADB>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADB>fastboot oem get-product-model
(bootloader) MHA-L29
OKAY [ 0.017s]
finished. total time: 0.017s
C:\ADB>fastboot oem get-build-number
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
Hi,
I have an XT926 running CM12.1. I would like to automatically power it on when the charger is connected.
I have read that the proper command to accomplish this task is the following: "fastboot oem off-mode-charge 0"
Whenever I try this command, I get the following response:
...
(bootloader) Restricted oem command
FAILED (remote failure)
finished. total time: 0.037s
Any thoughts on how to accomplish this?
Thanks in advance
fastboot flashing get_unlock_ability
fastbootflashing unlock
fastboot flashing lock
fastboot flashing unlock_critical
fastboot flashing lock_critical
fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem off-mode-charge
fastboot oem select-display-panel
fastboot oem device-info
fastboot reboot-fastboot
fastboot reboot-bootloader
fastboot oem gpt-info
fastboot oem adb_enable
fastboot oem shutdown
fastboot oem get-dtid
fastboot oem get-hwid
fastboot oem get-prjid
fastboot oem get-skuid
fastboot oem get-rfid
fastboot oem get-featureid
fastboot oem get-jtagid
fastboot oem get-bcid
fastboot oem get-secdispid
fastboot oem get-cpuidhash
fastboot oem get-toolid
fastboot oem isn-info
fastboot oem ssn-info
fastboot oem system-info
fastboot oem get_build_version
fastboot oem get-batcap
fastboot oem get-batvol
fastboot oem get-bootcount
fastboot oem factory-reset
fastboot oem factory-reset2
fastboot oem reboot-recovery
fastboot oem set-permissive
fastboot oem enter-dload
fastboot oem check-s3
fastboot oem EnterShippingMode
fastboot oem check-nrfuse
fastboot oem check-fuse
fastboot oem fuse-info
fastboot oem show-barcode
fastboot oem checksetupwizard
fastboot oem asus-csc_lk
fastboot oem rsa_test_
fastboot oem crc32_
fastboot oem hash_
fastboot oem gen-random
fastboot oem auth-hash
fastboot oem auth-hash_2
fastboot oem auth-hash_3
fastboot oem get-imeiauth
fastboot oem slot_b_enable
fastboot oem get-verify_vbmeta_ret
fastboot oem update-cmdline_
fastboot oem backup-fac
fastboot oem restore-fac
fastboot oem get-pmic-reg_
fastboot oem write-pmic-reg_
fastboot oem reset-boot_count
fastboot oem reset-lock_count
fastboot oem reset-a_retry_count
fastboot oem reset-a_unbootable_count
fastboot oem reset-b_retry_count
fastboot oem reset-b_unbootable_count
fastboot oem force-hwid_
fastboot oem reset-dev_info
fastboot oem reset-auth2
fastboot oem reset-auth3
fastboot oem disable-verity
fastboot oem enable-verity
fastboot oem enable-vbmeta
fastboot oem read-vbmeta
fastboot oem read-rollback
fastboot oem reset-rollback
hi, which one i can use to unlock my bootloader?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL: Post-CS3-30-ZS673KS-user
(bootloader) ABL: Post-CS3-25-WW-user
(bootloader) CID: ASUS
(bootloader) COUNTRY: WW
(bootloader) Project: ZS673KS
(bootloader) DT ID: 100
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 32
(bootloader) LOCK_COUNT: 1
(bootloader) Check_APDP: 0
(bootloader) rawdump_en: false
(bootloader) Current Slot: b
(bootloader) Slot_b bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) SNAPSHOT-UPDATE-STATUS: none
OKAY [ 0.080s]
finished. total time: 0.080s
Following the answer.
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Your phone is tencent edition or not?
HunterTik said:
Your phone is tencent edition or not?
Click to expand...
Click to collapse
No, its the ROG edition
zvrsd said:
No, its the ROG edition
Click to expand...
Click to collapse
Then use official unlock mathod hope it works for you.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Click to expand...
Click to collapse
You're in userspace fastboot. Reboot to the bootloader
The one you get to by using volume up and power is bootloader
From bootloader `fastboot reboot fastboot` -> userspace fastboot
From userspace fastboot, select reboot bootloader -> bootloader
`adb reboot fastboot` -> userspace fastboot
`adb reboot bootloader` -> bootloader
The bootloader also needs to be unlocked for most commands to work.
Andrologic said:
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
Click to expand...
Click to collapse
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
zvrsd said:
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
Click to expand...
Click to collapse
Thanks. Found it - going to try..