C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
I am having the same problem and it's driving me nuts. Any solution yet?
Which device are you on? lg has locked the fastboot commands. Until we have root you can't flash recovery. That's if installed the official ota marshmallow(6.0.1) from your carrier you lose root and you CANNOT downgrade doing so will BRICK!! your device because there is no (5.1) lollipop kdz for our device . So therefore we are stuck until the developers find a way to root it. So Be patient...
Sent from my LG-H901 using XDA-Developers mobile app
DAMN sent my v10 to lg for repair and got it back with official 6.0 on it. i'm getting the same remote unknown command error when using fastboot. Hopefully a fix soon!
I'm on the official 6.0 - not 6.0.1 referenced above. Any chance I can root? Screenshot shows my software info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using XDA Free mobile app
Same here. Any Solution? Also i read we can get FM Radio in h901. Is that possible? Please let me know. Thanks
Hi,
-Atlas__ said:
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Click to expand...
Click to collapse
disabling the "OEM unlock" option will probably solve your problem. It is only needed to unlock the bootloader and can be disabled afterwards. This did the trick for me.
you need to unlock the bootloader
this is what i did to get past it on my brand new tmobile v10 (H901)
if not in the bootloader pass the command
Code:
adb reboot bootloader
now pass
Code:
fastboot oem unlock
now continue to install twrp
you may need to use [/code]fastboot boot {path to image}[/code]
then transfer the twrp img to the phone via mtp (use mounts >enable mtp to do the transfer) disable mtp when done
and then install it again inside twrp using the install image option, just make sure you install it to recovery and NOT BOOT as that is a 1 way trip to brick ville
Has there been any development on this issue? I just picked up a refurb H901 with MM on it, and I get the same error.
I was able to unlock the bootloader, but I can't boot to the TWRP image (fastboot boot twrp.img), nor can I flash the recovery img to recovery from the stock (unlocked) bootloader (fastboot flash recovery twrp.img).
Thanks! I'm on H90120j
Seconded, I have bootloader unlock but get the same error message when flashing TWRP. Going to try Hünstetten suggestion.
No luck after disabling OEM Unlock and retrying, still get the failed message.
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
plz sand pix on instal recovery,myh901 not instal recovery
krixxux said:
Alright guys i figured it out. Use the command "fastboot boot [recoveryfilename.img]"
then once in twrp, flash twrp again and flash super user. Thats how i solved my problem. Also make sure that the recovery files is in your internal storage as well as the adb file on your computer
remember to open the command prompt from inside the adb folder
Click to expand...
Click to collapse
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
dogfyter said:
I am also getting Failure with both boatloader commands. Is there an update to this fix, or additional info? Thank you.
Click to expand...
Click to collapse
install "Minimal ADB and Fastboot" - search here on the V10 forum or google, and then in V10 section here you find the TWRP for V10, download the zip and extract the img to Minimal ADB and Fastboot main folder.
Then you open Minimal ADB and with USB debbuging on and the phone connected type:
adb reboot bootloader
- hit enter
- wait till the phone ask your permission from adb, for this keep the screen on and check the box in that window, then it will enter bootloader
- when in bootloader type in Minimal ADB:
fastboot flash recovery twrp-3.0.2.0-0-h960a.img
- and you done (note the twrp-3.0.2.0-0-h960a.img is the file of my TWRP img and yours can be different but i assume you download it from V10 section here so it will be the same after extracting it.)
- to enter TWRP just take the battery out after done all commands and put back in, keep your finger in volume down and power at same time, when LG logo appears release and put the finger back in power button.
- then a window will show up to restore defaults - ignore this saying yes to both, use volume rocker and power to confirm twice asked.
and thats it... if you want help see this:
https://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
dogfyter said:
I appreciate the effort. After the "adb reboot bootloader" command I get the "error: no devices/emulators found" response.
Keep in my my phone does reboot after typing the "fastboot reboot" command. I also have usb debugging acknowledged in the MM OS whenever I plug the usb in.
So I proceeded to the next step "fastboot flash recovery twrp... img" anyway and I get the same "Failed... " msg.
I think my V10 days will be short lived.
Click to expand...
Click to collapse
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
sun_is_shinning said:
try: fastboot reboot-bootloader
with " - " between reboot and bootloader.
OR
with your phone powered off put the finger on volume down and then connect usb and they will be in fastboot mode, before that try the command above mentioned.
Click to expand...
Click to collapse
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
dogfyter said:
Thanks again, Sun. I tried both and ways and got the same failure results. My amateur opinion is that when I installed LG Bridge on my PC (looking for drivers) it updated a tamper proof boot loader on my phone. But, who knows. Have a great day.
Click to expand...
Click to collapse
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I just verified the bootloader is unlocked. Since I unlocked it the next boatloader menu only provides the two options for how to exit bootloader. There are no menu options for "quick guidance" (ie, flash, erase, or reboot).
All attempts end with "FAILED (remote: unknown command)".
I do not know what that means so, I can only guess. Thanks again tho.
late response
sun_is_shinning said:
i never read something like that about "tamper proof bootloader", you did some update in LG bridge?
- are u sure you have bootloader unlocked?! this is strange...i never saw something like your problem.
Click to expand...
Click to collapse
I figured out it had nothing to do with lg bridge. I was having driver issues with windows 8.1. So after trying to follow another to install android sdk I had issues with that not installing properly. The thread suggested re-configuring files I could not even find/did not install. So I just gave up and got a different phone. Thanks again for trying.
Related
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Hello, i got this p20 lite 2018 from a friend, basically he told me that the phone was performing a software update during the night while it was charging, but then in the morning he found the device in a bootloop.
All i can do with it is get into fastboot, Recovery mode and download mode do not work (it just keeps bootlooping).
Sadly hisuite does not the recognize the phone, it pops up when i plug it in and that's, it just keeps saying that it doesn't recognize any phone. Also adb doesn't work(i already installed the drivers) and when i try to send fastboot commands i keep getting some kind of error.
Currently my main concern is data recovery, but if it's not possible to recover the data is it possible to at least save this brick?
Fastboot screen:
https://imgur.com/a/s8FBkDn
p.s. now it shows AP_S_ABNORMAL 64 but on other occasions it shows COLDBOOT 16 or AP_S_COOLDBOOT 0
SignoreTNT said:
data recovery
Click to expand...
Click to collapse
Hello,
just to be sure - have you tried boot into eRecovery? (connect the phone to PC or charger, then press and hold Power and Vol. Up for 10 sec).
There's an option on EMUI 9.1 - Emergency backup. It can backup your data to the external SD card.
SignoreTNT said:
save this brick
Click to expand...
Click to collapse
With the locked bootloader/FRP lock you have only a few options. First of all, you need access to Recovery (service firmware & dload mode) or eRecovery ("Download latest version and recovery") .
-Alf- said:
Hello,
just to be sure - have you tried boot into eRecovery? (connect the phone to PC or charger, then press and hold Power and Vol. Up for 10 sec).
There's an option on EMUI 9.1 - Emergency backup. It can backup your data to the external SD card.
With the locked bootloader/FRP lock you have only a few options. First of all, you need access to Recovery (service firmware & dload mode) or eRecovery ("Download latest version and recovery") .
Click to expand...
Click to collapse
Sadly nothing works except fastboot, i also tried eRecovery like 5 times but it just keeps bootlooping.
I tried again to execute some fastboot commands but i always get:
FAILED (remote: 'command not allowed')
Fastboot: error:Command failed
Edit: i forgot to say that i have the google account credentials and the phone password, i hope that might help with frp.
SignoreTNT said:
I tried again to execute some fastboot commands but i always get:
FAILED (remote: 'command not allowed')
Fastboot: error:Command failed
Click to expand...
Click to collapse
With locked FRP and bootloader only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
-Alf- said:
With locked FRP only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
Click to expand...
Click to collapse
Disconneting the battery might help? im not afraid to open up the phone at this point...
SignoreTNT said:
Disconneting the battery might help?
Click to expand...
Click to collapse
Yes.
-Alf- said:
With locked FRP and bootloader only information commands work, e.g. fastboot oem get-build-number, fastboot getvar vendorcountry etc.
Drain the battery completely, IMO last chance...
Click to expand...
Click to collapse
I drained the battery completely but as soon as it gets enough charge it tries to boot and it keeps getting stuck.
Also sometimes i get a weird green background with a blue square and a red square for a split second.
SignoreTNT said:
Also sometimes i get a weird green background with a blue
Click to expand...
Click to collapse
Something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
-Alf- said:
Something like this?
View attachment 5213075
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
Click to expand...
Click to collapse
Yep exactly like that screen.
Btw i guess that it is a software problem because it happened during a software update.
-Alf- said:
Something like this?
View attachment 5213075
Recovery software, at home, on the unit costs $19 (via DC-Phoenix), but if the problem is hardware, (dead memory, damaged motherboard), it won't help you.
Click to expand...
Click to collapse
Can i recover data with DC-Phoenix?
SignoreTNT said:
Can i recover data with DC-Phoenix?
Click to expand...
Click to collapse
Google search - 3 minutes
-Alf- said:
Google search - 3 minutes
Click to expand...
Click to collapse
Hey I am in the same situation but I have bootloader unlocked can you help me?
A little update (finally). i managed to unlock the bootloader so now i *should* be able to load a custom recovery or the stock firmware, if everything works ill make a little guide.
Now i need to flash the new firmware with fastboot but i really have no idea on how to do so, i have already downloaded the stock firmware that i need to load and i opened the update.app with huawei update extractor 0.9.9.5,but now i don't really know what to do (and i don't want to worsen the situation lol).
Can someone help me? any help would be appreciated <3
SignoreTNT said:
A little update (finally). i managed to unlock the bootloader so now i *should* be able to load a custom recovery or the stock firmware, if everything works ill make a little guide.
Now i need to flash the new firmware with fastboot but i really have no idea on how to do so, i have already downloaded the stock firmware that i need to load and i opened the update.app with huawei update extractor 0.9.9.5,but now i don't really know what to do (and i don't want to worsen the situation lol).
Can someone help me? any help would be appreciated <3
Click to expand...
Click to collapse
1. In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results pls.
2. check if your device has been detected and recognized by your computer, type
fastboot devices
If you get a response with your Serial number, it means that your device is properly connected
3.
SignoreTNT said:
i have already downloaded the stock firmware
Click to expand...
Click to collapse
Which firmware?
-Alf- said:
1. In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results pls.
2. check if your device has been detected and recognized by your computer, type
fastboot devices
If you get a response with your Serial number, it means that your device is properly connected
3.
Which firmware?
Click to expand...
Click to collapse
oem get-build-number
ANE-LX1 9.1.0.372(C432E7R1P7)
oem get-product-model
ANE-LX1
getvar vendorcountry
hw/eu
oem oeminforead-CUSTOM_VERSION
ANE-LX1-CUST 9.1.0.7(C432)
oem oeminforead-SYSTEM_VERSION
ANE-LX1 9.1.0.132(C432E5R1P7)
The firmware that i downloaded is C432E7R1P7T8
SignoreTNT said:
The firmware that i downloaded is C432E7R1P7T8
Click to expand...
Click to collapse
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
-Alf- said:
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
Click to expand...
Click to collapse
yea, downloaded it from androidhost.ru, fastboot devices is ok. now ill try to flash the recovery
-Alf- said:
Just to be sure - 9.1.0.370(C432E7R1P7T8) downloaded from androidhost.ru?
And what about command "fastboot devices"? It's okay?
I would suggest the following:
- there is a dload folder in stock firmware, copy it (without unpacking it!) to the SD card
Now try to install stock Recovery , download link
- in fastboot mode run
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
- fastboot reboot
- turn off the phone, then press and hold Power+Vol Up+ Vol Down ('three buttons combo') and try to install Service ROM (aka stock firmware) . Disconnect the phone from the PC before starting the process!
Click to expand...
Click to collapse
C:\Users\Davide\Desktop>fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.209s]
Writing 'recovery_ramdisk' OKAY [ 0.162s]
Finished. Total time: 1.405s
C:\Users\Davide\Desktop>fastboot reboot
Rebooting OKAY [ 11.589s]
Finished. Total time: 11.592s
I still cannot boot into Recovery, if i press that ccombination it goes into the huawei logo screen and then it reboots (and keeps bootlooping)
SignoreTNT said:
C:\Users\Davide\Desktop>fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.209s]
Writing 'recovery_ramdisk' OKAY [ 0.162s]
Finished. Total time: 1.405s
C:\Users\Davide\Desktop>fastboot reboot
Rebooting OKAY [ 11.589s]
Finished. Total time: 11.592s
I still cannot boot into Recovery, if i press that ccombination it goes into the huawei logo screen and then it reboots (and keeps bootlooping)
Click to expand...
Click to collapse
Maybe your emmc memory is dead...
Try command
fastboot erase userdata
then try enter Recovery.
If you want, extract from stock ROM :
CUST, KERNEL, SYSTEM, RECOVERY_RAMDIS , USERDATA.
Flash partitions using commands
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash cust CUST.img
etc.
Note: USERDATA.img can be found in _ANE-L21_hw_eu (second folder in dload).
-Alf- said:
Maybe your emmc memory is dead...
Try command
fastboot erase userdata
then try enter Recovery.
If you want, extract from stock ROM :
CUST, KERNEL, SYSTEM, RECOVERY_RAMDIS , USERDATA.
Flash partitions using commands
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash cust CUST.img
etc.
Note: USERDATA.img can be found in _ANE-L21_hw_eu (second folder in dload).
Click to expand...
Click to collapse
uhh, it's been erasing userdata for the past 20 mins at this point, should i disconnect the phone and try again?
Edit:
Erasing 'userdata' FAILED (remote: 'failed to erase partition')
fastboot: error: Command failed
ill try again
EDIT: I was able to unlock my bootloader by just trying to use the fastboot "unlock bootloader" command several times. Thanks a lot SubwayChamp for helping me through this, I was also able to root my phone. Wasn't able to install a custom recovery, though.
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AlNexus said:
I have a Multilaser H phone. It is a phone from a national brand, "Multilaser" here in Brazil.
For some reason, Multilaser does not want to provide the bootloader "unlock.img" file.
For context, the Multilaser H is just a white label of the Lenovo Z6 Lite/Lenovo K10 Note.
I downloaded the Z6 Lite unlock bootloader file and it has an "unlock_bootloader.img". I tried running the Z6 Bootloader Unlocker on the Multilaser H but it just didn't work. I really want to flash a custom ROM on my phone and I've tried all sorts of things, even trying to sideload another ROM but with the locked bootloader it's impossible. And no, I can't just buy a new phone, unfortunately. This one is more than capable of running Android 10 or even 11 but Multilaser just does not release it so I'm stuck on 9.
Is there any way to make that "unlock_bootloader.img" file that the Z6 Lite tool uses to unlock the phone for MY phone? Like, generate it? Because apparently the company doesn't want to provide it for us. The stock ROM I have here does have the "recovery.img" file.
Can I unlock my bootloader or somehow make a file similar to unlock_bootloader.img that allows me to do that? I have no idea how it works exactly but I'm assuming the "unlock.bootloader.img" is specific for the Z6 Lite and allows it to unlock the bootloader.
Here's how the Z6 Lite Tools folder looks like by the way
View attachment 5457515
Click to expand...
Click to collapse
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
SubwayChamp said:
Do you mean you tried something like this? https://www.gizdev.com/twrp-root-lenovo-z6-youth/ running the bootloader_unlock.bat? What does unlock_bootloader.img do?
Try with these commands apart to know the bootloader status
fastboot oem device-infoor fastboot getvar unlocked
Maybe you can try with simple commands to unlock it, in case you are wrong and the OEM doesn't care bootloader being unlocked:
fastboot oem unlock or fastboot oem unlock-go or
fastboot flashing unlock You should enable USB debugging and OEM unlock toggle must be available under this section, otherwise neither of those will work.
And if this device totattly rebranded from the Z6 Lite, or it has a MediaTek processor?
Click to expand...
Click to collapse
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
AlNexus said:
When I try those commands it just says "Waiting for device..." and there's nothing on my phone. The FastBoot screen is identical to the Z6 Lite one. And the device is totally rebranded apparently, maybe something there and here, but it has the same CPU, RAM and storage.
Click to expand...
Click to collapse
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
SubwayChamp said:
OK, we're just trying to figure it out if your device can be really unlocked or not, so you need to walk through these steps to be sure.
"Waiting for device..." means that your device is not being detected, you need to install properly the fastboot drivers for Lenovo otherwise you can´t do what you need, the first step is this. With your device on, enable USB debugging in developer options, and unlock OEM toggle, when you enabled USB debugging you will see a pop-up message asking for "allow always", then tap on it.
As per to know if the model is identical you should download an app from Google Play, something like Device Info and see the specs, if this device has MediaTek instead of Qualcomm there could be a workaround.
Click to expand...
Click to collapse
I installed the drivers. Here is the output of the 3 commands:
Code:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
AlNexus said:
I installed the drivers. Here is the output of the 3 commands:
PS C:\Users\alnexus> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
PS C:\Users\alnexus> fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.002s
PS C:\Users\alnexus> fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
It says "unlocked: no". Also it is Qualcomm, SDM710.
EDIT: Yeah it's probably impossible to unlock. Damn it, why do companies do this? Lock us in this crappy system and we can't even install another OS? I bought the phone, let me do whatever I want with it.
Click to expand...
Click to collapse
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
SubwayChamp said:
And is there an OEM unlock toggle? If not or even being one, if OEM doesn't want to be unlocked there’s not much to do.
And what happen running the unlock.bat from the Z6 lite now that you installed properly the fastboot drivers?
Also check what is in the unlock.bat script, open it with Notepad++ and see which command is executed.
Click to expand...
Click to collapse
Yes, there is an OEM unlock toggle. I enabled it.
Great idea, I'll try that, but my hopes are absolutely 0.
Here's the UNLOCK BOOTLOADER.bat (unlock.bat) script content:
Code:
@echo off
TITLE Bootloader Unlocker
color 3f
CLS
ECHO. ============================================================================
echo.
echo. Press any key
echo.
echo. ============================================================================
pause >nul
CLS
adb devices
echo.
echo Reboot mode bootloader
echo.
adb reboot bootloader
CLS
echo.
echo Firmware bootloader...
echo.
echo.
fastboot flash unlock unlock_bootloader.img
pause
CLS
echo.
echo Unlocking bootloader...
echo.
echo.
fastboot oem unlock-go
pause
CLS
echo.
echo Unlock complete, wait for reboot
echo.
fastboot %* reboot
pause
Yeah, didn't work ):
AlNexus said:
Yeah, didn't work ):
View attachment 5458091
Click to expand...
Click to collapse
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...
AlNexus said:
WHAT
I TRIED USING THE UNLOCK BOOTLOADER COMMANDQ MULTIPLE TIMES AND IH AVE UNLOCKED THE BOOTLOADER
I hope it doesn't brick my phone now lol. Sorry, I couldn't contain my excitement...View attachment 5458109
Click to expand...
Click to collapse
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
AlNexus said:
View attachment 5458111
When I try using that it just hangs on "downloading 'boot.img"...
Should I wait?
When I tried fastboot flash recovery twrp.img it said sending 'recovery' and said FAILED (remote: Requested download size is more than max allowed)
Click to expand...
Click to collapse
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
and it showed the splash screen with "press any key to shutdown" in the corner
AlNexus said:
it seems that sometimes when I try using "fastboot flash recovery twrp.img" it just "restarts" the phone. The phone goes to a splash screen and it says in the top corner "press any key to shutdown" and disconnects from the computer. "fastboot boot" just hangs on downloading 'boot.img'.
Oops, that just happened with fastboot boot too.
View attachment 5458129 and it showed the splash screen with "press any key to shutdown" in the corner
Click to expand...
Click to collapse
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
SubwayChamp said:
You also could try fastboot flashing unlock_critical
First, be sure to get the firmware at hands, in case something goes wrong.
Regards the TWRP version, are you sure it is for your device?
Maybe you need to port from the Z6 Lite, making minimal changes.
In a different approach, you could patch your boot image with Magisk and flash it to the boot partition.
"Too many links..." error is probably that you have attached to your PC more than one Android device/emulator/USB hub or something, check that, end the process with adb kill-server and restart again with adb start-server or go straight to the command, ADB will start automatically.
Click to expand...
Click to collapse
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
AlNexus said:
I'll try that. I don't know how to port but I don't think it should be too hard. Thanks for the tips, I'll also try to patch my boot image.
Click to expand...
Click to collapse
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
I had a different output on Linux, but Magisk App doesn't say "Installed".
EDIT: I tried to flash "twrp.img" (I know it's dangerous without a backup) and it said the same thing, except the phone doesn't seem to have TWRP installed.
It says finished but nothing actually happens or changes in the phone.
EDIT 2: When I try fastboot boot recovery.img it says FAILED (remote: 'unknown command')
AlNexus said:
View attachment 5458349
Patching the boot image doesn't work either. Stuck on "sending 'recovery' forever. I had also gotten
Code:
fastboot flash recovery magisk_patched.img
Sending 'recovery' (65536 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
before. I'll try with another USB cable. Wonder if it could be the drivers; I have already installed the device drivers from Google and Lenovo.
Click to expand...
Click to collapse
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
SubwayChamp said:
I guess you patched it the boot image from your stock ROM, then it is to flash it to the boot partition, not to the recovery partition, the usage would be fastboot flash boot patchedboot.img this is to achieve root, if rooted you could do more things.
I'm assuming that you opened the fastboot commands from within the directory where there are the images files.
Click to expand...
Click to collapse
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
AlNexus said:
Yes, I did.
You saved my day. Thanks a lot, I got it rooted by using fastboot flash boot magisk_patched.img. Having root is infinitely better than having nothing.
I should mark the whole topic as "solved" now. Thanks so much
Click to expand...
Click to collapse
Good to hear that.
Now you can follow with searching these topics:
- How to back up android partitions. (to get the complete images -firmware- so you can restore it if something goes wrong). This is just an example: https://github.com/for2ando/dump-android-partitions
- How to port TWRP recovery for my device, from the Z6 Lite can be used as base. Something like this: https://forum.hovatek.com/thread-26277.html
And lastly, to change for a different featured ROM:
- How to flash a GSI.
Hello,
As the title says I'm stuck in fastboot mode none of the options (Start, Restart bootloader, Recovery mode, Rescue mode) work.
I get error on the following:
NOS production: error!
Device state: error!
Enter reason: boot failure
The device has been sent to Google service center, and was denied warranty because of a small dent in top right corner.
They did not repair the device either and just sent it back to me.
The device is not listed when running adb devices, but is when running fastboot devices.
I'm trying to flash stock image files downloaded from google, but the problem here is that whatever I try to do I get "error getting device locked state -1".
And what I can find on the internet you need to enable OEM unlock and USB debugging.
Since I can't get the phone to boot that's impossible.
Is there anyway to unlock the device just by using fastboot?
Or is this phone just a very expensive paper weight?
Thank you for any help regarding this.
Have you tried flash.android.com? It might work if it finds fastboot.
superior888 said:
Have you tried flash.android.com? It might work if it finds fastboot.
Click to expand...
Click to collapse
Thank you for the tip, tried but same problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update picture of the dent.
Just so you all know that the dent is not critical.
Red arrow put there by google service center.
What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?
Silly question maybe, but have you tried to hold the power button down until it boots?
A couple things you might try in fastboot (I take no responsibility given I have no idea how you got into the state you are in and this will erase your data):
fastboot -w
Then see if you can boot
fastboot reboot or power button
or
fastboot format userdata
Then see if you can boot
fastboot reboot or power button
However, I fear you may get the same "device is locked" error when trying this.
Another Option:
Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots
Also, have you tried to see if it boots in Safe Mode?
Lughnasadh said:
What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?
Silly question maybe, but have you tried to hold the power button down until it boots?
A couple things you might try in fastboot (I take no responsibility given I have no idea how you got into the state you are in and this will erase your data):
fastboot -w
Then see if you can boot
fastboot reboot or power button
or
fastboot format userdata
Then see if you can boot
fastboot reboot or power button
However, I fear you may get the same "device is locked" error when trying this.
Another Option:
Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots
Also, have you tried to see if it boots in Safe Mode?
Click to expand...
Click to collapse
"What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?"
Answer: I was watching TikToks and noticed that the phone got hotter than usual. So I closed the app and locked the phone. When I was trying to unlock the phone it didn't recognize my fingerprint. And said my PIN code was wrong, so I rebooted the phone and then I was stuck in fastboot mode.
"Silly question maybe, but have you tried to hold the power button down until it boots?"
Answer: Yep, didn't work.
"fastboot -w
Then see if you can boot
fastboot reboot or power button"
Answer: Don't work fastboot -w just gives the device locked state -1 error. Fastboot reboot and power button restarts phone back to fastboot mode.
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
"Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots"
Answer: Boots right back up into fastboot mode.
"Also, have you tried to see if it boots in Safe Mode?"
Answer: Back into fastboot mode.
Thank you for all your help.
I guess
'fastboot format cache' and
'fastboot reboot recovery' doesnt work?
superior888 said:
I guess
'fastboot format cache' and
'fastboot reboot recovery' doesnt work?
Click to expand...
Click to collapse
fastboot format cache give the following error:
FAILED (remote: 'variable (partition-type:cache) not found')
fastboot reboot recovery reboots phone to fastboot mode.
Thank you.
lang0liers said:
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
Click to expand...
Click to collapse
I'm afraid I have bad news for you. There is no software fix for your issue as this is a hardware problem. The flash storage has failed and the clue is in the output of the fastboot command above. A file type of "raw" means there is no master boot record or equivalent in the flash storage. All your attempts at fixing via software fail because a side effect of the flash storage failure is to place the storage into a pemanent read-only state.
In simpler language the phone is a brick with no possibility of recovery short of cracking open the phone and trying to replace the flash storage.
That sucks. I'm a little bit concerned google didn't repair it due to it had been dropped? That shouln't really **** up the phone this much.
It didn't. Google used it however as a reason to void the warranty.
lang0liers said:
"What did you do beforehand that would not allow it to boot now? Anything in particular? Did it boot when you got the phone back?"
Answer: I was watching TikToks and noticed that the phone got hotter than usual. So I closed the app and locked the phone. When I was trying to unlock the phone it didn't recognize my fingerprint. And said my PIN code was wrong, so I rebooted the phone and then I was stuck in fastboot mode.
"Silly question maybe, but have you tried to hold the power button down until it boots?"
Answer: Yep, didn't work.
"fastboot -w
Then see if you can boot
fastboot reboot or power button"
Answer: Don't work fastboot -w just gives the device locked state -1 error. Fastboot reboot and power button restarts phone back to fastboot mode.
"fastboot format userdata
Then see if you can boot
fastboot reboot or power button"
Answer: Fastboot format userdata gives the following error:
fastboot: error: Formatting is not supported for file system with type 'raw'
"Leave in fastboot mode with phone unplugged until battery dies
Let phone sit for a while after battery dies
Hold down power button and plug into charger
Hopefully it boots"
Answer: Boots right back up into fastboot mode.
"Also, have you tried to see if it boots in Safe Mode?"
Answer: Back into fastboot mode.
Thank you for all your help.
Click to expand...
Click to collapse
Not looking good, as others have said. Only other thing I can think of is:
fastboot format:ext4 system
or
fastboot erase system
fastboot format:ext4 system
Not hopeful though...
Thank you all for your help.
I tried once more sending the product under warranty, but since the Pixel phone is not sold in my country and the company I bought it from didn't want to send it one more time to Google I disassembled the phone.
Before that I tried once more to empty the battery and the following commands:
fastboot format:ext4 system
fastboot erase system
fastboot format:ext4 system
But the I just got back that it couldn't find the partition named "system".
Also tried
fastboot format boot
fastboot format userdata
And got back:
fastboot: error: Formatting is not supported for file system with type 'raw'
So I opened the phone and if you look at the attached picture I believe that's where the heat came from.
So if anyone has a spare mother board for a Pixel 6, I'm intrested
lang0liers said:
Thank you all for your help.
I tried once more sending the product under warranty, but since the Pixel phone is not sold in my country and the company I bought it from didn't want to send it one more time to Google I disassembled the phone.
Before that I tried once more to empty the battery and the following commands:
fastboot format:ext4 system
fastboot erase system
fastboot format:ext4 system
But the I just got back that it couldn't find the partition named "system".
Also tried
fastboot format boot
fastboot format userdata
And got back:
fastboot: error: Formatting is not supported for file system with type 'raw'
So I opened the phone and if you look at the attached picture I believe that's where the heat came from.
So if anyone has a spare mother board for a Pixel 6, I'm intrested
View attachment 5531673
Click to expand...
Click to collapse
Oof, that's fried
How can google even deny warranty for that?
superior888 said:
How can google even deny warranty for that?
Click to expand...
Click to collapse
The warranty only covers manufacturer defects. The damage could have been a result of dropping the unit, which isn't covered by warranty. Not to mention the OP's country is not one where the unit is sold, so he has no warranty regardless.
Strephon Alkhalikoi said:
The warranty only covers manufacturer defects. The damage could have been a result of dropping the unit, which isn't covered by warranty. Not to mention the OP's country is not one where the unit is sold, so he has no warranty regardless.
Click to expand...
Click to collapse
Well, the warranty is valid in the whole EU, so if you live in a another country you just need to send it to the country where you bought the phone from.
jnsson said:
Well, the warranty is valid in the whole EU, so if you live in a another country you just need to send it to the country where you bought the phone from.
Click to expand...
Click to collapse
Apparently this is how the OP sought warranty service the first time. Google denied his warranty.
Sorry to read through this thread as my Pixel 6 Pro is exhibiting the same symptoms, after being in my car, in the shade, for 4 hours. Exact same fastboot screen, exact same response to all the helpful suggestions.
How widespread is this problem? I'm gun-shy to get another Pixel 6 Pro after this
finnd1 said:
Sorry to read through this thread as my Pixel 6 Pro is exhibiting the same symptoms, after being in my car, in the shade, for 4 hours. Exact same fastboot screen, exact same response to all the helpful suggestions.
How widespread is this problem? I'm gun-shy to get another Pixel 6 Pro after this
Click to expand...
Click to collapse
Seems to not be an isolated incident as I've had this happen last week with the exact same symptoms about the pin and fingerprint sketchy... Only that I simply turned it off to put a screen protector on it.
Luckily I'm still in warranty but the fact that op opened theirs up and clearly identified a cooked chip is a bit worrying for 'replacements' they send out.
I'm currently using this device: https://www.androidtv-guide.com/pay-tv-provider/myrepublic-stb/
Now I'm using Android 11 and wanna flash to latest firmware. But I'.stucking at step that need booloader unlocked, they showed the error like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moreover, the USB Burning Tool for Amlogic chip did not detect my device before, I've tried connect many times but not success.
boylklk9515 said:
the USB Burning Tool for Amlogic chip did not detect my device before, I've tried connect many times but not success.
Click to expand...
Click to collapse
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
boylklk9515 said:
wanna flash to latest firmware
Click to expand...
Click to collapse
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
boylklk9515 said:
But I'.stucking at step that need booloader unlocked, they showed the error like that:
Click to expand...
Click to collapse
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Functioner said:
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Click to expand...
Click to collapse
thanks for your reply.
Functioner said:
Note that a device running a newer SoC like the Amlogic S905Y4 will not have worldcup burn mode, so such a connection is not possible in any case.
What firmware do you intend to flash? You could easily brick the device by flashing incompatible firmware.
Your image above does not show what commands you are typing, and in what context.
There are multiple types of fastboot connections. Such as a userspace fastbootd connection, and a bootloader fastboot connection. There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
The image you posted is insufficient to determine what type of connection you had, and which commands you entered.
Click to expand...
Click to collapse
thanks for your reply.
But what is "worldcup burn mode".
I've tried connect my device to the UBT, but unsuccessful, then I tried to connect to 'fastbootd' mode and used the adb command to unlock bootloader, and the result shown above.
boylklk9515 said:
But what is "worldcup burn mode".
Click to expand...
Click to collapse
When you said: "the USB Burning Tool for Amlogic chip did not detect my device before".
The type of connection that would have been used to connect to v2 of the "USB Burning Tool for Amlogic chip" would have been a worldcup burn mode connection. The Amlogic S905Y4 chip used in the SDMC DV9135 does not have the ability to make this type of connection.
boylklk9515 said:
I've tried connect my device to the UBT, but unsuccessful, then I tried to connect to 'fastbootd' mode and used the adb command to unlock bootloader, and the result shown above.
Click to expand...
Click to collapse
I'll assume that "UBT" means "USB".
The bootloader cannot be unlocked in fastbootd mode.
It only can be unlocked in bootloader fastboot mode. This mode can be accessed by selecting the "reboot to bootloader" option in the recovery menu. Or, by typing "adb reboot bootloader" from a booted system with adb shell access.
Again, be careful in what firmware you choose to flash to this device. You can easily brick the device if you flash third party firmware. Only versions of the original factory firmware should be used.
Functioner said:
When you said: "the USB Burning Tool for Amlogic chip did not detect my device before".
The type of connection that would have been used to connect to v2 of the "USB Burning Tool for Amlogic chip" would have been a worldcup burn mode connection. The Amlogic S905Y4 chip used in the SDMC DV9135 does not have the ability to make this type of connection.
I'll assume that "UBT" means "USB".
The bootloader cannot be unlocked in fastbootd mode.
It only can be unlocked in bootloader fastboot mode. This mode can be accessed by selecting the "reboot to bootloader" option in the recovery menu. Or, by typing "adb reboot bootloader" from a booted system with adb shell access.
Again, be careful in what firmware you choose to flash to this device. You can easily brick the device if you flash third party firmware. Only versions of the original factory firmware should be used.
Click to expand...
Click to collapse
Thanks, let me try later and feedback you soon.
Do you use whatapps/telegram, can I have your number?
boylklk9515 said:
Do you use whatapps/telegram
Click to expand...
Click to collapse
No, I don't use either of those. I'd rather go down in a plane crash than use those apps.
Functioner said:
There is another type of connection, adnl, that uses the android drivers, so it also can be mistaken for a fastboot connection when really it is not.
Click to expand...
Click to collapse
Do you know any way to enter adnl mode?
Functioner said:
No, I don't use either of those. I'd rather go down in a plane crash than use those apps.
Click to expand...
Click to collapse
Here are some commands that I used on adb to unlock the bootloader
Microsoft Windows [Version 10.0.22000.2057]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
SDMC25112200092660 fastboot
C:\adb>fastboot flashing unlock
...
FAILED (remote: locked device)
finished. total time: 0.003s
C:\adb>fastboot oem unlock
...
FAILED (remote: secure boot device)
finished. total time: 0.004s
C:\adb>
The are two FAILED (in bold lines), said that my device is not accepted to unlock bootloader
My I try unlock bootloader by flashing other "boot.img" ?
boylklk9515 said:
Here are some commands that I used on adb to unlock the bootloader
C:\adb>fastboot devices
SDMC25112200092660 fastboot
Click to expand...
Click to collapse
Enter the fastboot command:
fastboot getvar all
and report what it shows
boylklk9515 said:
My I try unlock bootloader by flashing other "boot.img" ?
Click to expand...
Click to collapse
No. If you somehow manage to install a modified boot partition with the bootloader still locked, the device won't boot at all, and might be more difficult to recover.
Functioner said:
Enter the fastboot command:
fastboot getvar all
and report what it shows
No. If you somehow manage to install a modified boot partition with the bootloader still locked, the device won't boot at all, and might be more difficult to recover.
Click to expand...
Click to collapse
Here are the result
It looks like you are in fastbootD, not the bootloader version of fastboot.
to check, enter the fastboot command:
fastboot reboot bootloader
wait for the device to reboot and connect to fastboot again, and then enter the fastboot command:
fastboot getvar all
(again), and report if the output is any different than what you posted before
Functioner said:
It looks like you are in fastbootD, not the bootloader version of fastboot.
to check, enter the fastboot command:
fastboot reboot bootloader
wait for the device to reboot and connect to fastboot again, and then enter the fastboot command:
fastboot getvar all
(again), and report if the output is any different than what you posted before
Click to expand...
Click to collapse
here is the result like this
further result which the following commands
Code:
fastboot oem unlock
fastboot flashing unlock
boylklk9515 said:
further result which the following commands
Code:
fastboot oem unlock
fastboot flashing unlock
View attachment 5937145
Click to expand...
Click to collapse
The commands you tried usually work.
SDMC must have changed their bootloader some for this particular DV9135 model, since it is an operator tier model.
It's interesting that you have the folder structure:
\DV9135\DV9135_ATV11_RELEASE
on your windows pc.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Functioner said:
The commands you tried usually work.
SDMC must have changed their bootloader some for this particular DV9135 model, since it is an operator tier model.
It's interesting that you have the folder structure:
\DV9135\DV9135_ATV11_RELEASE
on your windows pc.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Click to expand...
Click to collapse
Shared by my friend, but what exactly happened with my device?
What can I do next to unlock the bootloader?
boylklk9515 said:
Shared by my friend
Click to expand...
Click to collapse
Exactly what was shared by your friend. Be precise.
boylklk9515 said:
but what exactly happened with my device?
What can I do next to unlock the bootloader?
Click to expand...
Click to collapse
If you have a copy of the firmware, it would go a long way in understanding what is going on.
Based on what you've posted, the bootloader restricts "oem" commands in fastboot based on the secureboot fuse setting.
And the unlock ability flag is 0, which is why "flashing unlock" doesn't work in fastboot.
You can check the value of the unlock ability setting:
fastboot flashing get_unlock_ability
(be sure to run this fastboot command in the bootloader version of fastboot, not fastbootD)
The result might be something like this:
(bootloader) get_unlock_ability: 0
Functioner said:
Exactly what was shared by your friend. Be precise.
If you have a copy of the firmware, it would go a long way in understanding what is going on.
Based on what you've posted, the bootloader restricts "oem" commands in fastboot based on the secureboot fuse setting.
And the unlock ability flag is 0, which is why "flashing unlock" doesn't work in fastboot.
You can check the value of the unlock ability setting:
fastboot flashing get_unlock_ability
(be sure to run this fastboot command in the bootloader version of fastboot, not fastbootD)
The result might be something like this:
(bootloader) get_unlock_ability: 0
Click to expand...
Click to collapse
I've tried and the result was:
so, my device was locked on fastboot mode and can not do anything
I've read something about ARM by this article: https://review.trustedfirmware.org/...329cabdd6e75c78e81f4e/docs/firmware-design.md
and it said :
Code:
The cold boot path in this implementation of the ARM Trusted Firmware is divided into five steps (in order of execution):
Boot Loader stage 1 (BL1) AP Trusted ROM
Boot Loader stage 2 (BL2) Trusted Boot Firmware
Boot Loader stage 3-1 (BL3-1) EL3 Runtime Firmware
Boot Loader stage 3-2 (BL3-2) Secure-EL1 Payload (optional)
Boot Loader stage 3-3 (BL3-3) Non-trusted Firmware
So, may it have anyway to replace thee "boot.img" and "bootloader.img" on the device to unlock the bootloader?
Do you use telegram?
You've ignored my question about exactly what was shared by "your friend" and whether or not you (or your friend) have a copy of the firmware in that "DV9135_ATV11_RELEASE" folder. I won't reply to this thread anymore if you don't answer these questions.
As I said before, 'android verified boot' (avb) checks the contents of the partition that contains "boot.img".
If you do what you describe as "replace thee "boot.img" with a copy that fails verification (while the device is still locked), it won't boot.
The bootloader is most certainly encrypted. It is unlikely that you could ever find what you describe as "bootloader.img" that could ever even boot on this device.
Flashing a bootloader that won't start results in a bricked device.
Functioner said:
You've ignored my question about exactly what was shared by "your friend" and whether or not you (or your friend) have a copy of the firmware in that "DV9135_ATV11_RELEASE" folder. I won't reply to this thread anymore if you don't answer these questions.
As I said before, 'android verified boot' (avb) checks the contents of the partition that contains "boot.img".
If you do what you describe as "replace thee "boot.img" with a copy that fails verification (while the device is still locked), it won't boot.
The bootloader is most certainly encrypted. It is unlikely that you could ever find what you describe as "bootloader.img" that could ever even boot on this device.
Flashing a bootloader that won't start results in a bricked device.
Click to expand...
Click to collapse
that is the folder has the firmware tool of dv9135, but nothing can be done if the bootloader in not unlocked. And exactly its mine.
Do you have the firmware extracted in the "DV9135_ATV11_RELEASE" folder?
Click to expand...
Click to collapse
Yes, I have