Develop Bugs

[Guide] Re-lock and Un-root WI-FI Xoom Build HWI69

This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com

first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse

HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally

I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while

I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?

Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work

I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update

what format are these imgs in?
I am trying to unyaffs them but it is not the right format

Your trying to what?

The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk

I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.

Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?

worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..

yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...

Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.

Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt

Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s

[Q] Can't get fastboot even with cable.

Windows 7, completely fresh installation, plug powered down kindle fire in with fastboot cable and just boots regularly. I cannot figure this out at all! Please help.

Update
Okay, so I was able to switch back to an ubuntu system and here is what I have:
I can enter fastboot mode and perform operations. Following the twrp - second bootloader guide results in a boot loops and I am unable to get past the orange kindle fire logo, it doesn't do anything at all.
Under linux does anyone know what I need to do to get this thing working again!? I have never had so many problems with a device! Ahhh, wish I hadn't tried to add wallpapers.
The issues started when I tried to push framework.odex and services.odex and it didn't go.

Solved
Okay, for anyone running Ubuntu like I was and stuck in a boot loop here's what I did:
Download stock recovery.img and boot.img.
Download KFHD_SRT V ??? tool or any other stock system.img.
Flash the three files using fastboot, then reboot will give you all stock restore.
sudo fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 66.375s]
writing 'system'...
OKAY [ 62.345s]
finished. total time: 128.720s
sudo fastboot -i 0x1949 flash recovery recovery.img
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 1.488s]
finished. total time: 2.098s
sudo fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.628s]
writing 'boot'...
OKAY [ 1.046s]
finished. total time: 1.674s
sudo fastboot -i 0x1949 reboot
rebooting...

[ROM][G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d

@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak

Thnkx buddy ...!!

thanks..Anyone tried it? it works?
Sent from my HTC Desire 300 using XDA Premium 4 mobile app

FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300

Is this confirmed working?

will this work on chinese 301e ....because these is no playstore in chinese version

aamszia said:
will this work on chinese 301e ....because these is no playstore in chinese version
Click to expand...
Click to collapse
Can I have a copy of your build.prop?

MameTozhio said:
@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak
Click to expand...
Click to collapse
i got status(0) error while flashing this rom :'( . what's wrong ?

MStevie said:
i got status(0) error while flashing this rom :'( . what's wrong ?
Click to expand...
Click to collapse
maybe this was created to kill your phone?

so i recieved another phone ... still no rom
chinese 301e

SPSPaWn said:
FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300
Click to expand...
Click to collapse
i got status(0) error while flashing this rom

I also have this error when I try to flash the HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox + init.d
Stock ODEX root 1.10.401.4 updated works without a problem.

what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....

maplegsm said:
what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....
Click to expand...
Click to collapse
You need to unlock the bootloader go to http://www.htcdev.com/ and click "Unlock Bootloader" select other device from the list and follow the instructions. Hope this helps.

where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????

RamHa said:
where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????
Click to expand...
Click to collapse
This is just a stock system dump I did about 2 years ago that was meant to be flashable with root but it doesn't flash properly for some, I won't be updating it any further.

Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy

Riski3Run said:
Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy
Click to expand...
Click to collapse
That's good! Just be sure to disable automatic receiving of MMS messages as this is vulnerable to all the stagefright exploits.

f
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
< waiting for device >
sending 'recovery' (6910 KB)... OKAY [ 1.463s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.563s
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.310s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.410s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.347s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 9.641s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.382s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.482s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>

[T00F] Stuck with Nothing but Droidboot & Recovery

Hi,
My Asus Zenfone 5 A500CG T00F was bricked earlier and I followed the community help to unbricked it.
Everything went fine except last step of flashing the ROM.
Somehow I messed up and now I have nothing but a locked droidboot (IFWI Version 59.29) loader and messed up recovery (ASUS_T00F-WW-2.21.40.44).
I have tried all available help regarding unlock the bootloader but It didn't worked. I can't flash using sideload due to *invalid cache(Invalid Argument)*.
I can't fix the partitions because it says the *GPT command failed*.
I am totally clueless now. Really appriciate any pointers.

flukebox85 said:
Hi,
My Asus Zenfone 5 A500CG T00F was bricked earlier and I followed the community help to unbricked it.
Everything went fine except last step of flashing the ROM.
Somehow I messed up and now I have nothing but a locked droidboot (IFWI Version 59.29) loader and messed up recovery (ASUS_T00F-WW-2.21.40.44).
I have tried all available help regarding unlock the bootloader but It didn't worked. I can't flash using sideload due to *invalid cache(Invalid Argument)*.
I can't fix the partitions because it says the *GPT command failed*.
I am totally clueless now. Really appriciate any pointers.
Click to expand...
Click to collapse
Moreover, Whenever I tried flash anything with fastboot it goes smoothly, NO Errors. But when I reboot I get back same old droidboot.

Use TWRP recovery instead

nheolinkin said:
Use TWRP recovery instead
Click to expand...
Click to collapse
Hi,
I am not able to install that because bootloader is NOT unlocked, that's where I am stuck at.
Anyway to install TWRP recovery on locked bootloader ?

If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.

nheolinkin said:
If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.
Click to expand...
Click to collapse
{
"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"
}
It says droidboot version 2.1 Build May 12 2015. Nothing more.

nheolinkin said:
If your fastboot is from 2.21.40.44 too, you can not flash ifwi for unlocking bootloader. Perhaps you wanna give some information about how you unlock bootloader or what error you get from fastboot gui.
Click to expand...
Click to collapse
For unlocking , I tried flashing (UBL Toolkit for Zenfone 5, Unlook Bootloader tool v4.0 and others) but no success. Problem is while doing any flashing with fastboot there is no error as such but It give me same screen after reboot. I may be doing something wrong I am not sure. If you can provide me the step to follow I can repeat the steps and tell you the result.

flukebox85 said:
For unlocking , I tried flashing (UBL Toolkit for Zenfone 5, Unlook Bootloader tool v4.0 and others) but no success. Problem is while doing any flashing with fastboot there is no error as such but It give me same screen after reboot. I may be doing something wrong I am not sure. If you can provide me the step to follow I can repeat the steps and tell you the result.
Click to expand...
Click to collapse
Run this tool
Choose option 1 in every step.
If it does not work, show me what it said on ADB window when tool was running.

nheolinkin said:
Run this tool
Choose option 1 in every step.
If it does not work, show me what it said on ADB window when tool was running.
Click to expand...
Click to collapse
Hi,
Sorry I don't have any windows setup for now. So I tried running the commands manually.
1) UNLOCK.bat
Option 1 points to files/patch.bat
2) files/patch.bat
Option 1 points to files/115fastboot.bat
3) files/115fastboot.bat
:Selection1
echo ' UPDATING FASTBOOT
fastboot flash dnx generaldnx_osr.bin
fastboot flash fastboot 1.17.40.16_fastboot.img
fastboot reboot-bootloader
sleep 20
echo ' RELOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi 115ifwi.bin
fastboot reboot-bootloader
sleep 20
echo ' UNLOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi if.bin
fastboot reboot-bootloader
sleep 20
echo ' SUCCESSFULLY PATCHED
pause
goto Quit
So. I tried running following commands manually with fastboot/droidboot on Zenfone5 and USB connected.
Below is the output.
-----------------------------------------------------------------------------------------------------------------------------------------------------
echo ' UPDATING FASTBOOT
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx_osr.bin
target reported max download size of 1320454826 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.509s]
writing 'dnx'...
OKAY [ 0.667s]
finished. total time: 1.177s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash fastboot 1.17.40.16_fastboot.img
target reported max download size of 1320454826 bytes
sending 'fastboot' (12421 KB)...
OKAY [ 1.787s]
writing 'fastboot'...
(bootloader) secure device
(bootloader) signed image
OKAY [ 2.128s]
finished. total time: 3.915s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.325s]
finished. total time: 0.326s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Phone rebooted to fastboot fine.
echo ' RELOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1320681472 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.500s]
writing 'dnx'...
OKAY [ 0.652s]
finished. total time: 1.152s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi 115ifwi.bin
target reported max download size of 1320681472 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.697s]
writing 'ifwi'...
OKAY [ 0.863s]
finished. total time: 1.560s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.319s]
finished. total time: 0.319s
-----------------------------------------------------------------------------------------------------------------------------------------------------
At this Phone DIDN'T rebooted to fastboot. Manually has to rebooted to fastboot.
This happens always with ifwi flash. It's show that my battery dies but if I manually reboot it reboots fine.
echo ' UNLOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1321028266 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.505s]
writing 'dnx'...
OKAY [ 0.650s]
finished. total time: 1.155s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi if.bin
target reported max download size of 1321028266 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.698s]
writing 'ifwi'...
OKAY [ 0.867s]
finished. total time: 1.565s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.321s]
finished. total time: 0.321s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Sadly, It's same droidboot/fastboot after each reboot.
Nothing changed. Ifwi and DroidBoot version are same.

flukebox85 said:
Hi,
Sorry I don't have any windows setup for now. So I tried running the commands manually.
1) UNLOCK.bat
Option 1 points to files/patch.bat
2) files/patch.bat
Option 1 points to files/115fastboot.bat
3) files/115fastboot.bat
:Selection1
echo ' UPDATING FASTBOOT
fastboot flash dnx generaldnx_osr.bin
fastboot flash fastboot 1.17.40.16_fastboot.img
fastboot reboot-bootloader
sleep 20
echo ' RELOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi 115ifwi.bin
fastboot reboot-bootloader
sleep 20
echo ' UNLOCKING BOOTLOADER
fastboot flash dnx generaldnx.bin
fastboot flash ifwi if.bin
fastboot reboot-bootloader
sleep 20
echo ' SUCCESSFULLY PATCHED
pause
goto Quit
So. I tried running following commands manually with fastboot/droidboot on Zenfone5 and USB connected.
Below is the output.
-----------------------------------------------------------------------------------------------------------------------------------------------------
echo ' UPDATING FASTBOOT
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx_osr.bin
target reported max download size of 1320454826 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.509s]
writing 'dnx'...
OKAY [ 0.667s]
finished. total time: 1.177s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash fastboot 1.17.40.16_fastboot.img
target reported max download size of 1320454826 bytes
sending 'fastboot' (12421 KB)...
OKAY [ 1.787s]
writing 'fastboot'...
(bootloader) secure device
(bootloader) signed image
OKAY [ 2.128s]
finished. total time: 3.915s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.325s]
finished. total time: 0.326s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Phone rebooted to fastboot fine.
echo ' RELOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1320681472 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.500s]
writing 'dnx'...
OKAY [ 0.652s]
finished. total time: 1.152s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi 115ifwi.bin
target reported max download size of 1320681472 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.697s]
writing 'ifwi'...
OKAY [ 0.863s]
finished. total time: 1.560s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.319s]
finished. total time: 0.319s
-----------------------------------------------------------------------------------------------------------------------------------------------------
At this Phone DIDN'T rebooted to fastboot. Manually has to rebooted to fastboot.
This happens always with ifwi flash. It's show that my battery dies but if I manually reboot it reboots fine.
echo ' UNLOCKING BOOTLOADER
-----------------------------------------------------------------------------------------------------------------------------------------------------
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash dnx generaldnx.bin
target reported max download size of 1321028266 bytes
sending 'dnx' (96 KB)...
OKAY [ 0.505s]
writing 'dnx'...
OKAY [ 0.650s]
finished. total time: 1.155s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot flash ifwi if.bin
target reported max download size of 1321028266 bytes
sending 'ifwi' (1983 KB)...
OKAY [ 0.698s]
writing 'ifwi'...
OKAY [ 0.867s]
finished. total time: 1.565s
[email protected]:~/Desktop/Asus/Unlock-Bootloader-ZF5/files$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.321s]
finished. total time: 0.321s
-----------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
And I still with the same droidboot. Nothing changed on reboot.

flukebox85 said:
And I still with the same droidboot. Nothing changed on reboot.
Click to expand...
Click to collapse
I see. It's not about the fastboot.
Try command "fastboot erase cache" and see it works or not
If it doesn't, then I can't help for now.

nheolinkin said:
I see. It's not about the fastboot.
Try command "fastboot erase cache" and see it works or not
If it doesn't, then I can't help for now.
Click to expand...
Click to collapse
[email protected]:~$ fastboot erase cache
erasing 'cache'...
OKAY [ 1.830s]
finished. total time: 1.830s
[email protected]:~$

ZENFONE 5
sAME PROBLEM HERE its been softbricked now fastboot recovered but cannot get into recovery only ifwi changes from 59.29 thru 59.2a to 59.27 now could anybody advice which fastboot and recovery shld i flash to get into recovery
Really s...s
And getting error e:/unable to mount cache during factory reset
I unlocked bootloader with option 1 all went fine now im on ifwi 59.a1 shld I flash fastboot recovery same version i proceeded bootloader unlock with?
Kind regards

Xiaomi Mi 10 Lite - Recovery mode

Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10

stephane_p said:
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
Click to expand...
Click to collapse
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup

Spuffyffet said:
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Click to expand...
Click to collapse
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.

stephane_p said:
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
Click to expand...
Click to collapse
However, it's still not working. I have the same issue.

stephane_p said:
However, it's still not working. I have the same issue.
Click to expand...
Click to collapse
well use "fastboot reboot recovery"

Spuffyffet said:
well use "fastboot reboot recovery"
Click to expand...
Click to collapse
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here

stephane_p said:
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
Click to expand...
Click to collapse
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)

Spuffyffet said:
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Click to expand...
Click to collapse
I downloaded platform-tools zip file (r33.0.0 for windows) and extract it in C:\Android\platform-tools
Then, I retry
C:\Android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 5.415s]
Writing 'recovery' OKAY [ 0.586s]
Finished. Total time: 6.017s
C:\Android\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But, I still get the fastboot screen instead of recovery mode.
Thank you for your help.

Have you tried with another recovery image, like TWRP ?

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
well i have and it worked for me

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

stephane_p said:
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using the wrong command bro, don't use boot. Use "fastboot flash recovery twrp_recovery.img". Why are you flashing recovery.img as boot bro?

OK guys I've found my mistake. I thought the model of my phone was Monet. But it's not. It's Toco... A stupid error showing that I have to be more rigorous.
I thank you again for your help. All the best for xda.
See you