Related
Hello all zenfone laser lovers,
As many of you have asked to release working twrp 2.8.7.0 for ze550kl & ze551kl.
I have ze550kl, I have tested this twrp & it s working well.
Rest you have to decide, is it work for you or not ?
Instructions are same as for 2.8.6.0
Do not flash, just boot it first.
Working TWRP 2.8.7.0 for ze550kl
https://drive.google.com/file/d/0Bz46tV6s-sImMmNLWWhZZ0QtN1k/view?usp=sharing
TWRP should work of ze500** series too, but not sure.
TWRP for ze551kl (testing purpose only)
Those who wish to test twrp 2.8.7.0 may download twrp, I am not sure about it will work or not but it should work.
https://drive.google.com/file/d/0Bz46tV6s-sImODJjXzBYVW5XNEU/view?usp=sharing
This post will be updated for ze551kl, if it s not working.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
{
"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"
}
If you have any issue then please verify md5 checksum
File: ze550kl_287.img
File size: 29.9 MB (31,334,400 bytes)
MD5 checksum: 7060B27AA5C4AB199915CBFBE889C4C4
SHA1 checksum: C0F33B8F398B4A5D5F1F410B671890476EF2711E
Warning
Use this at your own risk, I & xda-developer will not responsible for any loss.
Hit thanks, if my posts helps you.
Please reply so that, I may know, it is working or not.
Reserved.
rajlko said:
.
Click to expand...
Click to collapse
Awesome dude, thanks for it will try to it soon and revert to you
Are you planning to make it official??
And i have read somewhere that someone is making CM for our device, is that you who is porting CM?
rajlko said:
Hello all zenfone laser lovers,
As many of you have asked to release working twrp 2.8.7.0 for ze550kl & ze551kl.
I have ze550kl, I have tested this twrp & it s working well.
Rest you have to decide, is it work for you or not ?
Instructions are same as for 2.8.6.0
Do not flash, just boot it first.
Working TWRP 2.8.7.0 for ze550kl
https://drive.google.com/file/d/0Bz46tV6s-sImMmNLWWhZZ0QtN1k/view?usp=sharing
TWRP should work of ze500** series too, but not sure.
TWRP for ze551kl (testing purpose only)
Those who wish to test twrp 2.8.7.0 may download twrp, I am not sure about it will work or not but it should work.
https://drive.google.com/file/d/0Bz46tV6s-sImODJjXzBYVW5XNEU/view?usp=sharing
This post will be updated for ze551kl, if it s not working.
Warning
Use this at your own risk, I & xda-developer will not responsible for any loss.
Hit thanks, if my posts helps you.
Please reply so that, I may know, it is working or not.
Click to expand...
Click to collapse
Not working for me ZE550KL
:\Prakash\files me\FlashTools(1)\FlashTools>fastboot boot ze550kl_287.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.008s
eugineprakash said:
Not working for me ZE550KL
:\Prakash\files me\FlashTools(1)\FlashTools>fastboot boot ze550kl_287.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.008s
Click to expand...
Click to collapse
working well
C:\ADB>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\ADB>fastboot boot ze550kl_287.img
downloading 'boot.img'...
OKAY [ 1.077s]
booting...
OKAY [ 0.236s]
finished. total time: 1.314s
C:\ADB>
I'll try this out on my ZE551KL tomorrow and report back. Thanks!
eugineprakash said:
Not working for me ZE550KL
:\Prakash\files me\FlashTools(1)\FlashTools>fastboot boot ze550kl_287.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.008s
Click to expand...
Click to collapse
Try a newer version of ADB and flashboot
heywheelie said:
Try a newer version of ADB and flashboot
Click to expand...
Click to collapse
@heywheelie Still not working can u plz send the latest version of ADB and flashboot downloadable link.Tks
eugineprakash said:
@heywheelie Still not working can u plz send the latest version of ADB and flashboot downloadable link.Tks
Click to expand...
Click to collapse
Available here http://forum.xda-developers.com/showthread.php?p=42407269
heywheelie said:
Available here http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
@heywheelie Thanks but stil not working for me.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot ze550kl_287.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.003s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.014s
eugineprakash said:
@heywheelie Thanks but stil not working for me.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot ze550kl_287.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 0.003s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.014s
Click to expand...
Click to collapse
Never seen those two lines, while using commands.
rajlko said:
Never seen those two lines, while using commands.
Click to expand...
Click to collapse
@ rajlko yes but when i try to boot earlier twrp_ze550kl.img version is working.
only the latest twrp ze550kl_287.img is not working and also seen those two lines.
Hi @rajlko Sorry Now its working
The image file of latest twrp recovery which i downloaded earlier image is corrupted file size does not match.So i re-downloaded the latest twrp image and i tried its working now.Thanks a lot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot ze550kl_287.img
downloading 'boot.img'...
OKAY [ 1.012s]
booting...
OKAY [ 0.229s]
finished. total time: 1.245s
C:\Program Files (x86)\Minimal ADB and Fastboot>
match md5 sum and see
MD5 & SHA1 checksum added.
Happy to know, it works for you.
blueandro said:
match md5 sum and see
Click to expand...
Click to collapse
yes. now only i verified that the earlier twrp image file size does not match.so i re-downloaded the latest twrp image and i tried its working now.
eugineprakash said:
yes. now only verified the twrp image file size does not match.so i re-downloaded the latest twrp image and i tried its working now.
Click to expand...
Click to collapse
Glad it's working
Has anyone tried the 2.8.7.0 ZE551KL version yet?
Sent from my Zenfone 2 Laser ZE551KL
TWRP 2.8.7.0 boots fine here on ZE551KL / Z00T. Not sure if it flashes normally via fastboot or still needs flashify, haven't tried it yet.
whats up with message to keep system partition read only now? have never seen that before, allowed modifications for now.
Also, does anybody know of any custom ROM like CM-13.0 being made for Z00T model yet?
@rajlko I can be tester in ZE551KL (Z00TD) model.
Thanks in advance for your work friend.
guys do you have any idea why my stock firmware not listed on asus website..my firmware version is ww 1.15.40.703
---------- Post added at 03:30 PM ---------- Previous post was at 03:22 PM ----------
im in trouble i need to reflash my stock boot.img!help pls...
So I have been trying to unlock my bootloader for four months, and have failed literally every time at the same step.
The step being, fastboot oem get_identifier_token
Waiting for device
Unknown command
Time taken 0.003 seconds.
If anyone can help me unlock my bootloader, that would be great.
Also, I am unable to enter into 'hboot', it directly goes to recovery mode. (volume down + home button). All my device drivers are installed (HTC sync manager recognised my phone once, but after it recognised all the music, it immediately showed no device found).
This is my current situation, please help me out here!
xxxCrimeDogxxx said:
So I have been trying to unlock my bootloader for four months, and have failed literally every time at the same step.
The step being, fastboot oem get_identifier_token
Waiting for device
Unknown command
Time taken 0.003 seconds.
If anyone can help me unlock my bootloader, that would be great.
Also, I am unable to enter into 'hboot', it directly goes to recovery mode. (volume down + home button). I am rooted right now, so I am able to enter into fastboot directly. All my device drivers are installed (HTC sync manager recognised my phone once, but after it recognised all the music, it immediately showed no device found).
This is my current situation, please help me out here!
Click to expand...
Click to collapse
1. Which page your device is in when you issue the command "fastboot oem get_identifier_token"? Are you in FASTBOOT USB?
2. Are you using HTCDev.com to unlock your bootloader?
3. Upload a picture of the display of your device; and a picture of cmd page.
Dr.Ghobar said:
1. Which page your device is in when you issue the command "fastboot oem get_identifier_token"? Are you in FASTBOOT USB?
2. Are you using HTCDev.com to unlock your bootloader?
3. Upload a picture of the display of your device; and a picture of cmd page.
Click to expand...
Click to collapse
1) Yes, I am in the fastboot page..
{
"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"
}
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3)
This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
xxxCrimeDogxxx said:
1) Yes, I am in the fastboot page..
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3)
This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
Click to expand...
Click to collapse
1. My FASTBOOT USB page looks like the picture I attach for you.
2. If you cannot get the Identifier Token of your device, as you said, you cannot proceed to Step 7 and submit the Identifier Token to htcdev. And so they cannot email you the "Unlock_code.bin" file.
3. Can you upload a clear picture of the page you enter by pressing vol down+power?
4. Are you sure your device is supported by htcdev? (your exact model is not listed on their to be selected. Ask htc.com via online chat whether your device is supported or not.)
Unlock Bootloader HTC Desire 816G Dual Sim Tutorial
xxxCrimeDogxxx said:
1) Yes, I am in the fastboot page..
2) Yes, the HTCdev website..just past the step where they tell you to download the fastboot binaries and execute them..
3) This <----
My phone is unrooted, obviously not bootlocker, flashed with stock firmware. I am also unable to enter into the hboot page. I never could do that, I tried it two months into buying the phone, yet I never could enter the hboot. Does HTC Desire 816G Dual Sim (d816h) even have a hboot page? All HTC phones have a hboot page right?
These are all my phone features - https://androiddevice.info/submission/21306/show (Have a look if necessary)
Thanks!!
Click to expand...
Click to collapse
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
I will try that now and post the results.
Thanks and regards
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
so im apparently unable to retrieve the modaco superboot file. stupid surveys. though there are many other superboots out there. is each superboot different for each phone?
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
okay so now, ive almost got it...i have a screen where my phone says, press volume up to unlock bootloader and press volume down to NOT unlock bootloader...im stuck at the screen where it gives this option, ive already pressed volume up and nothing's happened..ill still be waiting..
BUT A HUGE DARN THANKS TO YOU FOR MAKING ME REACH THIS STEP
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
okay, so it seems ive 'waited too long' according to my phone ...
this is what happened after my phone said that while in fastboot mode
Dr.Ghobar said:
Have you tried this tutorial:
http://unlock-bootloader.net/how-to/unlock-bootloader-htc-desire-816g-dual-sim/
?
Click to expand...
Click to collapse
so now ive figured out that my volume down button works pretty well (since it stops unlocking and goes back to another screen), but when i press volume up, nothing happens.. there is the " ... " on my cmd which waits indefinitely, but when i press volume down, the screen says unlock failed, and goes back to another screen which is supposed to let me choose whether to reboot, reboott bootloader or anyything, again there i cant use my col up button.... im pretty sure it isnt broken
xxxCrimeDogxxx said:
so now ive figured out that my volume down button works pretty well (since it stops unlocking and goes back to another screen), but when i press volume up, nothing happens.. there is the " ... " on my cmd which waits indefinitely, but when i press volume down, the screen says unlock failed, and goes back to another screen which is supposed to let me choose whether to reboot, reboott bootloader or anyything, again there i cant use my col up button.... im pretty sure it isnt broken
Click to expand...
Click to collapse
Look at this too:
How To unlock htc bootloader using one click method (all HTC devices)
http://www.bestandroidrootedapps.com/how-to-unlock-htc-bootloader/
Dr.Ghobar said:
Look at this too:
How To unlock htc bootloader using one click method (all HTC devices)
http://www.bestandroidrootedapps.com/how-to-unlock-htc-bootloader/
Click to expand...
Click to collapse
Tried this long back, got the same result...
Log below....Thanks!
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out:
fastboot: devices
fastboot out:
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno:
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: LCSH92_CWET_KK
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.002s
get_device_info_failed
xxxCrimeDogxxx said:
Tried this long back, got the same result...
Log below....Thanks!
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out:
fastboot: devices
fastboot out:
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno:
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: LCSH92_CWET_KK
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.002s
get_device_info_failed
Click to expand...
Click to collapse
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Dr.Ghobar said:
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Click to expand...
Click to collapse
I've gone through this before, I have only USB Debugging, and yes, that is always enabled for me.
Dr.Ghobar said:
I guess that the problem is the mode where the device is in.
1. In your device's "Developers options" is there two following options?
USB Debugging
OEM Unlocking
2. If yes, are both enabled?
Click to expand...
Click to collapse
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
nukaru said:
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
Click to expand...
Click to collapse
What about unlocking his device's bootloader?
nukaru said:
His device is the Indian dual sim version (HTC Desire 816G / MT6592). The only way to flash any os on this device is using flashtool and this rom.
Click to expand...
Click to collapse
Really? But why? And btw I have a d816h, not a d816g, as stated in the ROM you linked me to. I flashed this rom: http://www.needrom.com/download/htc-d816h/
Dr.Ghobar said:
What about unlocking his device's bootloader?
Click to expand...
Click to collapse
Precisely my question. Why am I unable to unlock my bootloader?
xxxCrimeDogxxx said:
Really? But why? And btw I have a d816h, not a d816g, as stated in the ROM you linked me to. I flashed this rom: http://www.needrom.com/download/htc-d816h/
Click to expand...
Click to collapse
What is the relation between these two specifications of your device: 816g and D816h?
(What is your getvar all information?)
Dr.Ghobar said:
What is the relation between these two specifications of your device: 816g and D816h?
(What is your getvar all information?)
Click to expand...
Click to collapse
my getvar all never seems to work like the others...it just shows partitions/permissions or some other word..
yes there is a difference i cant ye seem to find, but i know mine is a d816h because of the box which i received my phone in
Hi Everyone,
I recently purchased an AT&T branded Z2 force. I SIM unlocked the device through the AT&T unlock portal, and subsequently OTA updated the phone to 7.1.1 (Ver. NCXS26.122-59-8-6, security level Sept. 1 2017). The phone thinks it is up to date but we all know Android 8 is available for this device.
I downloaded the latest update zip from android file host (NASH_ATT_OCXS27.109-47-14_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip).
I tried installing it in recovery mode but both ADB sideload and local installation types fail.
I tried Moto Smart Assistant but it says my device is unsupported. Screenshots:
{
"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"
}
Even the flashall.bat from the Return to stock thread didn't work. The fastboot commands simply hang when trying to transfer files to the phone (which is in bootloader mode).
The phone seems to be recognized correctly in the Windows Device Manager, and I already installed the Motorola Device Manager drivers.
I am stumped. I've rooted/installed custom roms on several android devices in the past, but I've never encountered one as stubborn as this.
Any input would be greatly appreciated. Thank you
Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.
The update ZIP file from Android Host is for the Moto Z2 Play (not Force)
HKSpeed said:
The update ZIP file from Android Host is for the Moto Z2 Play (not Force)
Click to expand...
Click to collapse
Incorrect. Nash refers to the Z2 Force. It just happens to share a folder with the Z2 Play. You'd need to contact the folder's owner for a separate one to be made, but that's not necessary.
More importantly, attempts to flash these on the Play will likely result in bricks.
Smart Assistant didn't recognize that file I downloaded form Android Host. Instead Smart Assistant downloaded a different file and flashed it.
Android Host file: OCXS27.109-47-14
Smart Assistant (build # on my Z2 Force): OCXS27.109-47-17 (Nov 1, 2018 patch level date)
I have one as well and I just used the flshall but that did not work, it soft bricked. So then I used LSMA restore and now I have oreo.
41rw4lk said:
Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.
Click to expand...
Click to collapse
Thanks for your help. I am not allowed to post screenshots as a new user. Here's a copy-paste of my command prompt (serial redacted):
Code:
Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Temp\FlashAllUtils>fastboot devices
ZY224BCXXX fastboot
C:\Temp\FlashAllUtils>flashall.bat
C:\Temp\FlashAllUtils>fastboot oem fb_mode_set
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Temp\FlashAllUtils>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Temp\FlashAllUtils>fastboot flash partition gpt.bin
(bootloader) slot-cou: not found
(bootloader) slot-suffi: not found
(bootloader) max-downlo: not found
target didn't report max-download-size
sending 'partition' (206 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Temp\FlashAllUtils>fastboot flash bootloader bootloader.img
(bootloader) current-slott: not found
error: Failed to identify current slot
C:\Temp\FlashAllUtils>fastboot flash modem NON-HLOS.bin
(bootloader) slot-countott: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'modem' (97411 KB)...
"Sending Modem" hangs indefinitely. Doesn't seem like anything is actually being sent to the device.
Your firmware.zip and utilities.zip should both be unzipped into one folder, see attached. The only thing that might be causing a problem, maybe not though, is the fact that everything is coming out of a Temp folder in your root directory. Whether that is an actual temp folder or just a folder you made called temp it's not a good choice to work out of. Certain namespaces and paths are subject to environmental variables and permissions; a folder named Temp in your root directory would definitely qualify. Try renaming the folder and make sure everything is unzipped in there.
Just a quick update: it looks like there was a hardware issue with the device; no laptop I tried (of 3) could properly communicate with the phone in both adb and fastboot modes.
I received my replacement from Motorola, and it was immediately identified by Lenovo Moto Smart Assistant
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Hey,
I have the same issue, did you ever find a solution?
You must unlock first
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"
bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working
Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.
For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK
Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)
josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?
Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.
Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.
{
"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"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151
So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?
No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool
Hi Folks,
I'm having issues where the linked account in Miui wont be detected when using the Mi Unlock Tool. The error I am getting is "Please add your Miui Account in Settings etc" however this is already done and is 100% the same account (I've checked more times than I can count). Just so you know, I have also enabled developer settings and debugging (works fine with ADB commands), I have also enabled OEM Unlocking in the developer menu.
At no point do I get a message telling me to wait 168 hours etc, I did wait a week just in case, no dice. All I get is the "please add your account etc" which is already done!
Steps taken
Different cables
Different ports
Different accounts (before and after the week timer)
Different login methods, ie - password, QR code etc
VPN used incase it was something regional (based in UK)
Updated firmware (currently on MIUI Global 12.5.8)
Turning find my phone on and off etc
Reset device
Tried using my desktop, laptop and work machine (same result)
Information
The only other thing I can tell you is that I am having the exact same issue on my Mi Pad 5. I figured this would mean it's something account based, but no, still no dice. I have tried 4 different accounts now and none of them work, they all give me the "Please add you miui account in settings etc" when trying to unlock.
The crazy thing is, I have a Redmi Note 10 Pro which I have unlocked fine no issues (last year). The last thing I want to do however is relock the bootloader and try unlocking it again.
Any ideas here would be much appreciated!
I've just tried using windows 10 instead of 11 and the issue persists.
Okay I went ahead and tried using a 3rd party tool, this is the error I get now
{
"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"
}
DEBUG <12:10:42.666,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:10:42.710,T:24320> : tokenversion=0
DEBUG <12:10:42.712,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
INFO <12:10:42.754,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.003s
DEBUG <12:10:42.754,T:24320> : getvar token -s 499cc3ff
DEBUG <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
INFO <12:10:42.802,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.006s
DEBUG <12:10:42.802,T:24320> : to check erase feature for 499cc3ff
DEBUG <12:10:43.831,T:24320> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG <12:10:44.658,T:23820> : User click unlock button!
DEBUG <12:10:55.740,T:24320> : -s 499cc3ff oem device-info
DEBUG <12:10:55.789,T:24320> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
finished. total time: 0.006s
DEBUG <12:11:00.745,T:24320> : VerifyDeviceInfo
INFO <12:11:00.745,T:24320> : product:nabu
DEBUG <12:11:00.745,T:24320> : getvar tokenversion -s 499cc3ff
DEBUG <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : getvar:tokenversion FAILED (remote: GetVar Variable Not found)
finished. total time: 0.004s
INFO <12:11:00.789,T:24320> : tokenversion=0
DEBUG <12:11:00.789,T:24320> : oem get_token -s 499cc3ff
DEBUG <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
INFO <12:11:00.832,T:24320> : ...
FAILED (remote: unknown command)
finished. total time: 0.002s
DEBUG <12:11:00.832,T:24320> : getvar token -s 499cc3ff
DEBUG <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
INFO <12:11:00.874,T:24320> : token: VQEBHgEQuZBLqLkTiHcTiSenDHQLEgMEbmFidQIEWKeUng
finished. total time: 0.003s
DEBUG <12:11:00.874,T:24320> : to sign token with key for device:nabu
DEBUG <12:11:02.465,T:24320> : sign result:{
"code" : 20031,
"descCN" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"descEN" : "Please add your account in MIUI's Settings > Developer options > Mi Unlock status.",
"description" : "请在MIUI上绑定账号后解锁：开发者模式下打开设置，搜索设备解锁状态，然后进行绑定",
"uid" : "6351847669"
}
DEBUG <12:11:02.465,T:24320> : unlock return:11111 msglease add your account in MIUI's Settings > Developer options > Mi Unlock status.
Download official Mi Flash Tool and Mi Unlock Tool.
Open Mi Flash Tool and install drivers (For Android bootloader interface).
Download and install mtk drivers.
Turn off Wifi and turn on 3g/4g.
Add account in Developer settings.
Boot in Fastboot and check by Mi Unlock Tool (check if it show 168h or not).
If it shows 168h, DON'T EVER touch Developer option, don't add or remove account, don't update or format rom.
Just wait & countdown by boot in Fastboot and use Mi Unlock Tool.
Or else just unlock instantly by unofficial tool without data lost
None of this worked, I am on 12.5.8.0 RGGMIXM.
It DOES NOT show any sort of timer let alone the 168h countdown.
vannblackwings said:
None of this worked, I am on 12.5.8.0 RGGMIXM.
It DOES NOT show any sort of timer let alone the 168h countdown.
Click to expand...
Click to collapse
Kirasu2080 said:
Click to expand...
Click to collapse
Thanks, this worked, however I am still having issues making it so the "official" method works. If you check my other thread my Mi Pad 5 is still locked.
vannblackwings said:
Thanks, this worked, however I am still having issues making it so the "official" method works. If you check my other thread my Mi Pad 5 is still locked.
Click to expand...
Click to collapse
Check if your PC/Laptop is AMD or Intel. Some AMD got compatible issues with these kind of driver. You should Install new Window or Dual boot a new one or borrow another PC/Laptop.
Kirasu2080 said:
Check if your PC/Laptop is AMD or Intel. Some AMD got compatible issues with these kind of driver. You should Install new Window or Dual boot a new one or borrow another PC/Laptop.
Click to expand...
Click to collapse
I've got both, Laptop is intel, desktop is AMD. I previously unlocked a Redmi Note 10 Pro using the desktop no issues whatsoever. I even went as far as dual booting into windows 7 and 10 just to check.
vannblackwings said:
I've got both, Laptop is intel, desktop is AMD. I previously unlocked a Redmi Note 10 Pro using the desktop no issues whatsoever. I even went as far as dual booting into windows 7 and 10 just to check.
Click to expand...
Click to collapse
Did you add this?
Kirasu2080 said:
Did you add this?
Click to expand...
Click to collapse
Yeah, I am even using a fresh account and phone number. No timer no dice.
vannblackwings said:
Yeah, I am even using a fresh account and phone number. No timer no dice.
Click to expand...
Click to collapse
Maybe try watch a YouTube video and do step by step. I have both rmn8p and mi pad 5. All worked fine.
Kirasu2080 said:
Maybe try watch a YouTube video and do step by step. I have both rmn8p and mi pad 5. All worked fine.
Click to expand...
Click to collapse
Watched more YouTube video and step by steps than I care to remember, however the issue was resolved with the account region. Once I switched from a UK/GB account to a US one I now get a timer. Looks like something's borked because of that specifically, even when the firmware is EEA.
I'm getting this problem too - which account did you change to US and where is that setting?
Go to the mi account website, create a new account but make sure you select US as the region when you do.
smithbill said:
I'm getting this problem too - which account did you change to US and where is that setting?
Click to expand...
Click to collapse
Option is at the top once you click create account, then select the drop down etc
What a ridiculous almost circuitous process you have to go through to get this to work!
After reading your initial reply, i thought I could just log into my Mi account in a browser and change my region to US. But no, you cant change your region, so I had to create a new account using a browser and set the region to US, but then the Unlock Tool wouldn't let me set the International Dial Code to anything except +1 which i'm assuming would mean SMS verification codes wouldn't be received. I think I ended up using a Browser again to login to my new Mi account and then enter & verify my recovery phone number with +44 code.
In the end I think I had created three separate Mi accounts, each associating my phone number to different emails and Mi ID's etc and then requiring verification emails & codes sent to my phone number.
Eventually I got the 168 hour confirmation.
A completely ludicrous process - Xiaomi: if your listening - GET THIS FIXED!!!
(thank you @vannblackwings without who's help I would've struggled with this!)
Kirasu2080 said:
Click to expand...
Click to collapse
help me please!!! after unlocking the bootloader, I can not install twrp via fastboot! HELP ME PLEASE!!