Database Develop

[SOLVED] Rooting, Custom Recovery on HBOOT 1.55

I just received a new warranty phone from AT&T - I had my old phone S-OFF, unlocked, etc running my ROM of choice. However, the new phone I received today is on HBOOT 1.55. Now, I unlocked the bootloader and have been trying for hours to get root, custom recovery, and S-OFF. I know that Rumrunner can get SOFF for 1.55, but it apparently doesn't work without root. Which I can't figure out how to get without being able to flash a custom recovery. Normally, I could just do that with fastboot, but when I try, I just get a "failed to load" error, which apparently is due to the fact that HBOOT 1.55 doesn't allow the fastboot flash recovery command (and I'm positive file name and command was entered correctly). I've tried toolkit by Hasoon (sp?), and I get an error with that, which I think is just running fastboot commands. Anyway, if you've read this far, I appreciate it, and you probably see my dilemma. Can anyone help, please? So I need to get either root or custom recovery and I can seem to figure out a way to do it.
Thanks

gsxrfl1k6 said:
I just received a new warranty phone from AT&T - I had my old phone S-OFF, unlocked, etc running my ROM of choice. However, the new phone I received today is on HBOOT 1.55. Now, I unlocked the bootloader and have been trying for hours to get root and S-OFF. I know that Rumrunner can get SOFF for 1.55, but it apparently doesn't work without root. Which I can't figure out how to get without being able to flash a custom recovery. Normally, I could just do that with fastboot, but when I try, I just get a "failed to load" error, which apparently is due to the fact that HBOOT 1.55 doesn't allow the fastboot flash recovery command (and I'm positive file name and command was entered correctly). I've tried toolkit by Hasoon (sp?), and I get an error with that, which I think is just running fastboot commands. Anyway, if you've read this far, I appreciate it, and you probably see my dilemma. Can anyone help, please?
Thanks
Click to expand...
Click to collapse
There is a root info guide on the XDA HTC One homepage.

Ktan188 said:
There is a root info guide on the XDA HTC One homepage.
Click to expand...
Click to collapse
I appreciate the reply, but rooting that way requires a custom recovery. Which as I stated above, I'm not able to install so far due to having HBOOT 1.55 and no SOFF to downgrade it. So the more pressing issue is not so much root but installing the custom recovery. I can't use GOO Manager or any of the others because I don't have root and I can't use fastboot because I have HBOOT 1.55

Are you on windows 8.1?

SaHiLzZ said:
Are you on windows 8.1?
Click to expand...
Click to collapse
no,7

Never had such an issue with fastboot

SaHiLzZ said:
Never had such an issue with fastboot
Click to expand...
Click to collapse
Did you try with HBOOT 1.55? I read that the commands for boot and flash recovery don't work

Yes I have. Check your fastboot drivers.

SaHiLzZ said:
Yes I have. Check your fastboot drivers.
Click to expand...
Click to collapse
Gave that a try, updated fastboot and adb, still getting - "target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error"

Try a diffferent computer, usb cable or usb port.

SaHiLzZ said:
Try a diffferent computer, usb cable or usb port.
Click to expand...
Click to collapse
Same result on the ports and cable, haven't tried the different computer yet, though. Although, the bootloader unlock process used fastboot and it worked ok....

flash works but not boot?
Hi guys, I'm a complete noob at his stuff but i managed to get fastboot to flash twrp but it wouldn't boot twrp first so i could do a stock recovery. I think this might be the problem with hboot 1.55 which I'm not stuck with after returning to stock for an OTA update. My lesson learn't. I also had drama flashing anything with twrp 2.6.3.3, but downngrading it to 2.6.3.0 then worked a treat. Good luck :good:

gsxrfl1k6 said:
Gave that a try, updated fastboot and adb, still getting - "target reported max download size of 1526722560 bytes
error: cannot load 'recovery.img': No error"
Click to expand...
Click to collapse
1- to flash custom recovery, you only need an unlocked bootloader, S-off not required
in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
2- "error: cannot load 'recovery.img': No error" -> that just means the filename is wrong, use the correct one, do a "dir" in command prompt and see what it's really called.
EDIT: next time copy/paste the command prompt output, would have saved you some time, when we can see the actual output

nkk71 said:
1- to flash custom recovery, you only need an unlocked bootloader, S-off not required
in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
2- "error: cannot load 'recovery.img': No error" -> that just means the filename is wrong, use the correct one, do a "dir" in command prompt and see what it's really called.
EDIT: next time copy/paste the command prompt output, would have saved you some time, when we can see the actual output
Click to expand...
Click to collapse
If you refer to my op, you'll see that I said fastboot is not working for me - the FIRST thing I did long before I posted my plea for help was to try the commands you wrote. And, as i also stated in the op, the command and file name was entered correctly. Lastly, I did copy and paste the console output, hence the stuff in the quotes. Thanks though.

gsxrfl1k6 said:
If you refer to my op, you'll see that I said fastboot is not working for me - the FIRST thing I did long before I posted my plea for help was to try the commands you wrote. And, as i also stated in the op, the command and file name was entered correctly. Lastly, I did copy and paste the console output, hence the stuff in the quotes. Thanks though.
Click to expand...
Click to collapse
no need to get snappy, anyway here you go, check my command prompt:
Code:
C:\ADB2>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB2
25/11/2013 16:57 <DIR> .
25/11/2013 16:57 <DIR> ..
19/08/2012 00:00 846,848 aapt.exe
19/08/2012 00:00 191,488 adb.exe
19/08/2012 00:00 96,256 AdbWinApi.dll
19/08/2012 00:00 60,928 AdbWinUsbApi.dll
20/05/2013 03:03 1,151,546 APKBIT.exe
20/11/2010 21:23 345,088 cmd.exe
19/08/2012 00:00 140,800 fastboot.exe
05/07/2013 21:50 27,446,092 fw_2.24.401.1_custom.zip
03/10/2013 06:56 1,102,709,591 Guru_Reset_M7_2.24.707.1.zip
12/11/2013 16:37 1,252,513 logcat_log.txt
31/03/2012 23:53 186 mainver_fix.bat
19/02/2012 00:24 656,708 misctool
19/02/2012 07:41 4,526 misctool.c
04/10/2013 17:35 0 nandroid.md5
27/10/2013 20:38 10,823,680 openrecovery-twrp-2.6.3.0-m7.img
09/06/2013 13:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
[B][B]14/06/2013 19:01 7,600,128 recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B][/B]
30/09/2013 02:08 8,427,520 recovery-clockwork-touch-6.0.3.8-m7ul.img
05/11/2013 02:29 9,052,160 recovery-clockwork-touch-6.0.4.4-m7ul.img
14/11/2013 07:12 8,955,904 recovery-clockwork-touch-6.0.4.5-m7ul.img
09/06/2013 15:02 648,208 revone
03/11/2013 20:56 249,028 Screenshot_2013-11-03-20-51-36.png
29/02/2008 03:33 5,925,120 stock_boot_img_2.24.401.8.img
05/05/2013 15:04 9,820,416 stock_recovery_1.29.666.17.img
22/08/2013 12:17 8,964,352 stock_recovery_2.24.401.1.img
29/09/2013 21:31 10,584,320 stock_recovery_2.24.401.8.img
24/06/2013 09:09 8,964,352 stock_recovery_2.24.707.1.img
27 File(s) 1,225,415,925 bytes
4 Dir(s) 11,100,098,560 bytes free
C:\ADB2>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[B][COLOR="Blue"]C:\ADB2>fastboot flash recovery recovery.img[/COLOR][/B]
[COLOR="Red"]error: cannot load 'recovery.img'[/COLOR]
C:\ADB2>[B]fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B]
sending 'recovery' (7422 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
C:\ADB2>[B][B]fastboot erase cache[/B][/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>

nkk71 said:
no need to get snappy, anyway here you go, check my command prompt:
Code:
C:\ADB2>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB2
25/11/2013 16:57 <DIR> .
25/11/2013 16:57 <DIR> ..
19/08/2012 00:00 846,848 aapt.exe
19/08/2012 00:00 191,488 adb.exe
19/08/2012 00:00 96,256 AdbWinApi.dll
19/08/2012 00:00 60,928 AdbWinUsbApi.dll
20/05/2013 03:03 1,151,546 APKBIT.exe
20/11/2010 21:23 345,088 cmd.exe
19/08/2012 00:00 140,800 fastboot.exe
05/07/2013 21:50 27,446,092 fw_2.24.401.1_custom.zip
03/10/2013 06:56 1,102,709,591 Guru_Reset_M7_2.24.707.1.zip
12/11/2013 16:37 1,252,513 logcat_log.txt
31/03/2012 23:53 186 mainver_fix.bat
19/02/2012 00:24 656,708 misctool
19/02/2012 07:41 4,526 misctool.c
04/10/2013 17:35 0 nandroid.md5
27/10/2013 20:38 10,823,680 openrecovery-twrp-2.6.3.0-m7.img
09/06/2013 13:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
[B][B]14/06/2013 19:01 7,600,128 recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B][/B]
30/09/2013 02:08 8,427,520 recovery-clockwork-touch-6.0.3.8-m7ul.img
05/11/2013 02:29 9,052,160 recovery-clockwork-touch-6.0.4.4-m7ul.img
14/11/2013 07:12 8,955,904 recovery-clockwork-touch-6.0.4.5-m7ul.img
09/06/2013 15:02 648,208 revone
03/11/2013 20:56 249,028 Screenshot_2013-11-03-20-51-36.png
29/02/2008 03:33 5,925,120 stock_boot_img_2.24.401.8.img
05/05/2013 15:04 9,820,416 stock_recovery_1.29.666.17.img
22/08/2013 12:17 8,964,352 stock_recovery_2.24.401.1.img
29/09/2013 21:31 10,584,320 stock_recovery_2.24.401.8.img
24/06/2013 09:09 8,964,352 stock_recovery_2.24.707.1.img
27 File(s) 1,225,415,925 bytes
4 Dir(s) 11,100,098,560 bytes free
C:\ADB2>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[B][COLOR="Blue"]C:\ADB2>fastboot flash recovery recovery.img[/COLOR][/B]
[COLOR="Red"]error: cannot load 'recovery.img'[/COLOR]
C:\ADB2>[B]fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img[/B]
sending 'recovery' (7422 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
C:\ADB2>[B][B]fastboot erase cache[/B][/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>
Click to expand...
Click to collapse
Didn't mean to sound snappy.
I just realized that since I reformatted my laptop a couple of weeks ago, file extensions were hidden so the file name was wrong due to .img.img. So thanks for suggesting I pull a dir, I'm an idiot...

gsxrfl1k6 said:
Didn't mean to sound snappy.
I just realized that since I reformatted my laptop a couple of weeks ago, file extensions were hidden so the file name was wrong due to .img.img. So thanks for suggesting I pull a dir, I'm an idiot...
Click to expand...
Click to collapse
no worries. the .img.img issue is happening a lot!
BTW, if fastboot doesn't recognize your device it usually just sits there waiting:
Code:
C:\ADB2>fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
< waiting for device >

nkk71 said:
no worries. the .img.img issue is happening a lot!
BTW, if fastboot doesn't recognize your device it usually just sits there waiting:
Code:
C:\ADB2>fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
< waiting for device >
Click to expand...
Click to collapse
Good to know, thanks again.

[Q] why are the recovery files corrupted?

ok so i unlocked my bootloader for my htc one m7 but when i want to install cwm recovery or twrp recovery, the files are corrupted and cannot load even when i tried flashing it it says that the file cannot be loaded.
with this problem i cant install recovery on my phone.
PLS HELP
thanks

Damacy6 said:
ok so i unlocked my bootloader for my htc one m7 but when i want to install cwm recovery or twrp recovery, the files are corrupted and cannot load even when i tried flashing it it says that the file cannot be loaded.
with this problem i cant install recovery on my phone.
PLS HELP
thanks
Click to expand...
Click to collapse
"cannot load" is usually a user error. Most likely the Recovery file is in the wrong location.
Can you try to flash recovery again then copy the full output from your command window and post it here. And a screen shot of your fastboot folder would also be helpful :good:

Damacy6 said:
ok so i unlocked my bootloader for my htc one m7 but when i want to install cwm recovery or twrp recovery, the files are corrupted and cannot load even when i tried flashing it it says that the file cannot be loaded.
with this problem i cant install recovery on my phone.
PLS HELP
thanks
Click to expand...
Click to collapse
adb not found file path that's problem

like said above "can not load" error is not caused by a corrupted file. "Can not load" error = "Fastboot can't find the file you want to flash". There are 3 reasons why it can occur:
1- The file you want to flash is not in the correct folder.
e.g: to use "fastboot flash recovery recovery.img" , recovery.img file must be in the same folder where adb and fastboot are otherwise you must write the path to this file:
"fastboot flash recovery C:\path\to\my\file\recovery.img"
If the files is not in adb/fasboot folder or if you are not specifying the path to your file, fastboot will not find it and will output "can not load error".
2- A typo in your file name.
For example, If the recovery is named "openrecovery-twrp.img" and you are making a typo in your command: "fastboot flash recovery openrecoveryy-twrp.img" fastboot will not find the file and output "can not load" error.
3- You have double file extension.
Windows, by default, is hiding extension of known file type. So your "recovery.img" file might be displayed as "recovery'" only in the file explorer. The user then mistakenly add a ".img" to "recovery" to have "recovery.img" displayed in the explorer but this will result with a real file name of "recovery.img.img". If you do "fastboot flash recovery recovery.img", fastboot will look for "recovery.img" not for "recovery.img.img" so it will output "can not load" error.
How to avoid that? Read this.

alray said:
like said above "can not load" error is not caused by a corrupted file. "Can not load" error = "Fastboot can't find the file you want to flash". There are 3 reasons why it can occur:
1- The file you want to flash is not in the correct folder.
e.g: to use "fastboot flash recovery recovery.img" , recovery.img file must be in the same folder where adb and fastboot are otherwise you must write the path to this file:
"fastboot flash recovery C:\path\to\my\file\recovery.img"
If the files is not in adb/fasboot folder or if you are not specifying the path to your file, fastboot will not find it and will output "can not load error".
2- A typo in your file name.
For example, If the recovery is named "openrecovery-twrp.img" and you are making a typo in your command: "fastboot flash recovery openrecoveryy-twrp.img" fastboot will not find the file and output "can not load" error.
3- You have double file extension.
Windows, by default, is hiding extension of known file type. So your "recovery.img" file might be displayed as "recovery'" only in the file explorer. The user then mistakenly add a ".img" to "recovery" to have "recovery.img" displayed in the explorer but this will result with a real file name of "recovery.img.img". If you do "fastboot flash recovery recovery.img", fastboot will look for "recovery.img" not for "recovery.img.img" so it will output "can not load" error.
How to avoid that? Read this.
Click to expand...
Click to collapse
i tried and its neither of this problems but i think its the recovery file cause its corrupted.

Damacy6 said:
i tried and its neither of this problems but i think its the recovery file cause its corrupted.
Click to expand...
Click to collapse
cannot load == MyFileNameIsWrong
even if the file is corrupt, it won't give you that error (so better check MD5, just in case)
so this http://forum.xda-developers.com/showpost.php?p=55681400&postcount=21
or @Danny201281's drag & drop method
PS: next time post the output of your command prompt (not just the error, everything you typed and the output), for example:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s

Problem installing not incremental ROM

Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.

I am on mac so cannot use Mi Flash

EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader

helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.

Only i dont understand: (recomend this others from this year locked boot loader) ?

EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.

Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:

EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.

Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...

EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.

When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.

EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)

Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?

EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/

every time I type:
fastboot oem edl
the screen of the smartphone goes off

Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?

EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?

No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.

Is Snapdragon SDK actually Qualcomm drivers?

helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?

fastboot error lg optimus l90 D415

So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing

SMOKYxPANDA said:
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
Click to expand...
Click to collapse
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.

0000.0000.00 said:
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
Click to expand...
Click to collapse
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing

SMOKYxPANDA said:
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
Click to expand...
Click to collapse
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?

0000.0000.00 said:
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
Click to expand...
Click to collapse
No, i'm not trying to save any data, I want a fresh start, the problem when trying the "fastboot oem unlock" command is that it gives me an error, again i put a link below to show you what appears when trying that command..
https://drive.google.com/file/d/0B0shRlbnxbQpeFlxcWxjS0l1eE0/view?usp=sharing

This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing

SMOKYxPANDA said:
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
Click to expand...
Click to collapse
Something probably happened..
Can you please send the results of fastboot getvar all so I can check.

I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view

SMOKYxPANDA said:
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
Click to expand...
Click to collapse
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s

SMOKYxPANDA said:
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
Click to expand...
Click to collapse
Then try flashing twrp and the bootstack and Tell me how it goes from there.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
0000.0000.00 said:
Then try flashing twrp and the bootstack and Tell me how it goes from there.
Click to expand...
Click to collapse
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img"
Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...

SMOKYxPANDA said:
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img" Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
Click to expand...
Click to collapse
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
0000.0000.00 said:
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
Click to expand...
Click to collapse
After that, run fastboot reboot recovery to reboot into recovery. Press the advanced button and then press the button that says adb sideload with the touchscreen and start it. Then to install the zip run adb sideload zipname where zipname is the name of the zip you want to flash.
After that boot back into the download mode thing to reflash recovery and then reboot into recovery with fastboot reboot recovery. After that I would flash the zips for a ROM and optionally gapps with adb sideload.

This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing

SMOKYxPANDA said:
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
Click to expand...
Click to collapse
Were you able to flash recovery and boot into it?

0000.0000.00 said:
Were you able to flash recovery and boot into it?
Click to expand...
Click to collapse
No, you can observe in the picture where it gives me the same error message, unknown command

SMOKYxPANDA said:
No, you can observe in the picture where it gives me the same error message, unknown command
Click to expand...
Click to collapse
Could you please send me a picture of the output of fastboot devices.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
I think the fastboot on the phone has issues because it seems to not flash anything. I think you should try this >>> https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>

asahi7 said:
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

thanks, already did, unfortunately seems like there is a problem with the rom. i flash each file but when i test again i always get slb1 corrupt. no recovery, no download mode. it was worth the try

Question NE2217 Can't unlock my bootloader

I got my token, hit oem unlocking. Rebooted to fastbootd mode, then I use fastboot flash cust-unlock. Which returns,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
If I try it without cust-unlock I get,
C:\Users\James>fastboot flash C:\Users\James\Desktop\10pro\unlock_code.bin
unknown partition 'C:\Users\James\Desktop\10pro\unlock_code.bin'
fastboot: error: cannot determine image filename for 'C:\Users\James\Desktop\10pro\unlock_code.bin'
If I fastboot reboot to bootloader and do the same command I get,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.002s]
Writing 'cust-unlock' (bootloader) Device is unlocked.
OKAY [ 0.004s]
Finished. Total time: 0.099s
But, that doesn't actually unlock my bootloader. Can someone please help?

Here's some more I have tried
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown 'flashing' command unlock
C:\Users\James>fastboot unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown command unlock

Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock

centifanto said:
Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
Click to expand...
Click to collapse
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping

Grin59 said:
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping
Click to expand...
Click to collapse
Four things:
Name of file doesn't matter
SIM unlock and bootloader unlock are separate things
Move the unlock.bin to the same folder as your platform tools so you don't have to put the entire the path. Or put it in quotation marks
Is fastboot in your system PATH? If not, prefix fastboot to look like this
Code:
./fastboot.exe

Also, what does the following command return?
Code:
fastboot devices

centifanto said:
Also, what does the following command return?
Code:
fastboot devices
Click to expand...
Click to collapse
C:\>fastboot devices
*serial number* fastboot
Also not too sure what you mean, "Is fastboot in your system PATH? If not, prefix fastboot to look like this"
But it is installed to my system drive. Even tried downloading new platform tools and trying it in my root drive of C:\

No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?

centifanto said:
No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?
Click to expand...
Click to collapse
Okay so I got it, thank you for the help.
Did the commands you sent in the bootloader menu, guess I missed the second.
For anyone who can't unlock the bootloader I'll post simple instructions, on the NE2217
OEM unlock - on
adb reboot bootloader
fastboot devices
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
anyone can add anything else