Database Develop

[Q] Nexus one broken power button won't boot

I need some help here.
Power button broke on my n1 sometime ago. Recently I tried to flash a new kernel but forgot to wipe and it's basically stuck at the logo.
I'm able to get into the hboot screen via bqttry removal technique but cannot select any option because of bad power button.
Any ideas how to flash a new room? I tried connecting USB to pc but phone is not recognized while in hboot mode.
Any help would appreciated as it's my only phone
Thanks

Is your phone unlocked (ie do you have a lock symbol at the bottom of the 'X' screen)?
If so, I believe you can hold the trackball while booting up and that will take you into fastboot.
From there, I think you just issue the command
Code:
fastboot reboot recovery
If that doesn't work, you can just boot off a recovery file that is stored on your computer. Download either clockworkmod (I would recommend any v2.x as v3.x has some problems) or Amon_RA to a easy to type location on your computer. Then issue the command
Code:
fastboot boot recovery "c:\location to\recovery.img"

Ok, so I got it to boot in fastboot, but there's no option to
./fastboot-mac reboot recovery
Click to expand...
Click to collapse
also
./fastboot-mac boot recovery ../recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
I get:
cannot load 'recovery'
and I did this:
fastboot flash recovery /path/to/<recovery>.img
Click to expand...
Click to collapse
Is there a way reboot it into recovery?
Thanks!

Passimg back to stock, root, and try again...

jp2000 said:
I get:
cannot load 'recovery'
Click to expand...
Click to collapse
Is there any more into that error? Did you verify the md5sum to make sure the recovery isn't corrupted?
Also, if you have a recent nandroid backup saved on your sdcard, you can pull that off and flash the imgs directly
Code:
./fastboot-mac flash system /location/to/system.img
./fastboot-mac flash boot /location/to/boot.img
./fastboot-mac flash userdata /location/to/data.img
./fastboot-mac reboot
Where these files will be located depends on your recovery. I know with clockworkmod they are located in the backup folder under the clockworkmod folder on the sdcard. I don't know where they are stored for Amon_RA, but I would assume it would be similar.

Thanks to everyone for your suggestions.
Finally got my phone working!

Hi.
I have the same problem but whenever I try "fastboot flash" or "fastboot recovery" I end up with "FAILED (remote: signature verifiy fail)". I think this is due to that my bootloader is not unlocked, so I tried:
fastboot oem unlock
I got the option to unlock bootloader but I had to use my power button to select "unlock". My power button is broken so I don't know what to do.
Is there anything else I can do? Otherwise I think I have to open the phone and try to repair the button.

PASSIMG back to stock and root. Use "unroot/restore" section in Wiki.
If you're skilled enough with soldering tiny connectors - you can repair the button. There is a guide on this forum, showing the exact location to attach to.

Thanks. Now I can use the phone again!

Where is this repair guide...please let me know...
Sent from my Nexus One using xda premium

[Q] Cannot boot into recovery

I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.

dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.

Try flashing CWM as well and see what happens ...

dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.

redbull123 said:
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
Click to expand...
Click to collapse
I can't get to settings. It hangs at the HTC logo.

v-b-n said:
Try flashing CWM as well and see what happens ...
Click to expand...
Click to collapse
I did try that. It hangs at the "Entering Recovery..." screen.

dlbarron said:
I did try that. It hangs at the "Entering Recovery..." screen.
Click to expand...
Click to collapse
did u "fastboot erase cache" after flashing the recovery?

kibmikey1 said:
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Click to expand...
Click to collapse
Is that the right recovery?
Don't I have to be able to boot into recovery to run the RUU? Where can I get it?
What are some of the other options?

nkk71 said:
did u "fastboot erase cache" after flashing the recovery?
Click to expand...
Click to collapse
Yes, I tried erase cache before and after, no difference.

I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151

xxmorph3u5xx said:
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
Click to expand...
Click to collapse
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.

Looks like I have no choice but to try the RUU. I have been hesitant because I have yet to find a good explanation and good downloads of all the parts I need. Is there something like that available?

all right, this will certainly add to the confusion.
I flashed recovery_m7_att_stock and was able to get into it a little. Then I went back to the bootloader and flashed openrecovery-twrp-2.5.0.0-m7 and actually get into it.
WHAT?
I pushed the CM nightly rom to it and it installed, although there were some errors about not being able to mount some things data and cache. But it did install and I was able to get into CM.
I'm almost afraid to try anything else at this point.

dlbarron said:
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Click to expand...
Click to collapse
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition

nkk71 said:
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
Click to expand...
Click to collapse
After rebooting I'm still able to get into TWRP. I've been able to flash a couple of ROMs (very carefully) and I'm no longer seeing any errors about not being able to mount.
Looks like what ever was wrong has been corrected. Now all we have to do is figure out what went wrong and what I did to fix it.
Thanks everyone.

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK

[SOLVED] Cannot find BOOTLOADER option?

Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.

bashme said:
Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
that is the BOOTLOADER.:silly:
to enter TWRP
go to HBOOT then enter RECOVERY
if not entering then its messed up . flash it again with new file or try different version.

+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.

gazza35 said:
+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.
Click to expand...
Click to collapse
It does not do anything unless you have just the correct files in your SD card that define the network and so on. Only service centers and network providers have such files.

Silly me lol
I selected HBOOT then RECOVERY but it goes back to the bootloader menu??
I have already re-flashed it. I guess i will have to find another file to flash.
Thanks for the advice guys

OK guys.
I flashed a different version of TWRP img file and it still does not boot into TWRP?
I noticed something else. When i select HBOOT, for around a two seconds several lines of info are displayed:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
I pasted a copy of the TWRP img file in the root of my SD card. But still it comes back to Bootloader??
Not sure what to do now?
Any advice guys, please?

Hi guys.
Still not able to load into TWRP. I briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Can anyone help please?
Cheers.

bashme said:
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
Click to expand...
Click to collapse
You are flashing the wrong recovery. Considering the m4 at the end of the image name, this is for the One Mini not the One Mini 2. Which is why you are not able to boot into TWRP.
Get the correct image from here

Hi csoulr666.
Thank you for your reply.
I downloaded the image from the link you kindly provided - recovery-twrp-2.8.5.0.img
When i issue the command fastboot boot recovery-twrp-2.8.5.0.img i get the following response
downloading 'boot.img'...
OKAY [ 1.489s]
booting...
OKAY [ 0.004s]
finished. total time: 1.499s
Then the device reboots into the standard htc home screen and NOT into twrp. At this point the USB cable is still attached to the device and PC. Not sure if this has any bearing on the normal boot??
I performed the above steps several times, but still the device boots up to htc home screen and not twrp.
In bootloader, i also selected HBOOT, i briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
i then select RECOVERY, however the device stays in bootloader??
Very frustrating to say the least.
Am i missing something else?
Thanks for the advice up until now.
P.S please excuse me, i am a newbie so not that much familiar with rooting.
Cheers.

bashme said:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
if you dont want keep seeing this just remove SDCard while you performing the actions.
try this recovery instead
its normal the device boot into the rom unless you press the buttons to get into bootloader.

Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.

bashme said:
Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.
Click to expand...
Click to collapse
not sure what you asking and for what but after a search i found this:
open command prompt and type
adb devices (if your device shows continue)
adb shell
su -c 'setprop sys.usb.config diag,adb'
nothing happened on mine but i don't have HTC drivers installed. All you need in here

Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Previously, I was able to enable HS USB diag port using the above adb command on the Xperia Z and Samsung Mini S4. But I've not been able to activate HS USB on Xperia Z3 and now HTC One Mini 2. I was under the impression that if I rooted and flashed a custom rom onto the HTC One Mini 2, all developer features would be automatically available, especially the HS USB diag port??
To compound the misery, after much reading on rooting and flashing for HTC One Mini 2, I flashed cm-NostromoPop-v2.0-20150430-1330-memul.zip and open_gapps-arm-5.0-nano-20160401.zip. Thankfully the device is not bricked. However, now i get the following problems
When accessing Google Play Store - 'Check your connection and try again'
'Google Play Services won't run...' message repeatedly appears
I cannot boot into twrp recovery so that i can flash another rom
I read on the net that installing the wrong GApps file produces the above google problems? Could i have installed the incorrect GApps file?? Not sure how to verify this? Could the rom i installed be incorrect?
And what can i do to get into twrp recovery again? Not even the twrp recovery image i earlier flashed and successfully booted into has helped this time.
I am rigorously searching the net for answers, to no avail thus far.
Ahh the joy of messing with a phone. I'm very tired but will keep trying lol
Any help would be warmly welcomed.
Thanks in advance.

bashme said:
Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Click to expand...
Click to collapse
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.

kativiti said:
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.
Click to expand...
Click to collapse
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.

bashme said:
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.
Click to expand...
Click to collapse
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.

kativiti said:
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.
Click to expand...
Click to collapse
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again

bashme said:
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again
Click to expand...
Click to collapse
you can use ADB push but you need TWRP for that.

kativiti said:
you can use ADB push but you need TWRP for that.
Click to expand...
Click to collapse
OK so after much fretting i managed to get my device working.
I managed to boot into bootloader and then flashed an earlier version of twrp and it immediately booted into recovery.
From here i wiped cache, system...... and then installed CM12 with corresponding GApps.
Device now working...PHEW!
OK so now back to trying to get HS USB port activated using ADB commands, which i am trawling the net to find. I just don't understand why it is possible to activate HS USB port in Windows for Samsung and Sony, but not on this HTC One Mini 2?? The ADB setprop command you listed earlier is usually the one that triggers windows to open up the HS USB Diagnostics port, but it is not happening with this HTC One Mini 2? Anyway, i'll keep checking the net.
I have added an image just to show what it is i am trying to activate - Qualcomm HS USB Diagnostics Interface Port
Once again many thanks for your assistance kativiti.

reserved

Honor 4x factory reset and recovery menu not work

Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.

If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).

oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....

Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.

oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX

Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked

thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down

shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.

zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!

I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.

Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.

Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...

Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.