Database Info

[Q] fastboot flash recovery problem? "variable not supported"

Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.

i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.

Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!

Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck

In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2

Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.

just hold up like normal after
fastboot reboot

ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.

Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.

Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!

Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else

Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.

Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.

arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>

Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...

arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !

Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app

4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:

I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.

[Q] Brick - Can't get cold boot / broken cwm

NB/EDIT : I am pretty sure this is due to cmupdater requiring "next boot" to recovery. Is there any way to get through this?
NB/ EDIT : Now, I can cold boot. But the flash (DD/ fastboot seems not be working. hope better news next hours).
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...

http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
florck said:
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
Click to expand...
Click to collapse

Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
elfaure said:
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
Click to expand...
Click to collapse

florck said:
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
Click to expand...
Click to collapse
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com

elfaure said:
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
Click to expand...
Click to collapse
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...

florck said:
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
Click to expand...
Click to collapse
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.

_that said:
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
Click to expand...
Click to collapse
Unfortunately, i don't have twrp... I can't see the solution here... :crying:

florck said:
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
Click to expand...
Click to collapse
Why doesn't adb work? Can you see any USB device on your computer?

_that said:
Why doesn't adb work? Can you see any USB device on your computer?
Click to expand...
Click to collapse
Oh ! I got and ADB shell.
but when I "ls /dev/block", I only get
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p3
platform
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?

florck said:
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
Click to expand...
Click to collapse
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment bootit.zip
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.

_that said:
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment 1985914
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
Click to expand...
Click to collapse
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?

florck said:
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
Click to expand...
Click to collapse
The funny serial number is normal for the recovery.
Try the procedure again and hold down volume-left immediately after pressing "Enter" in adb shell on the insmod command. Maybe you can get to the bootloader menu. If not, I'll try to build another kernel module.

That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.

florck said:
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
Click to expand...
Click to collapse
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment bootit-bootloader.zip
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.

_that said:
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment 1985941
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
Click to expand...
Click to collapse
You're a genius, I can now fastboot and / or cold boot. When I cold boot I have my fully functional previous android. But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?

florck said:
You're a genius, I can now fastboot and / or cold boot.
Click to expand...
Click to collapse
That's good news - until today your situation was considered an unrecoverable hard brick.
florck said:
But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
Click to expand...
Click to collapse
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.

_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...

florck said:
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
Click to expand...
Click to collapse
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461

_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
_that said:
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
Click to expand...
Click to collapse
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...

florck said:
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
Click to expand...
Click to collapse
Any other idea ? Something to flash in other blocks?

Recovery no longer allows me to select files from memory (twrp)

I updated now I can't do anything. Im able to book ROM and to boot into recovery but am no longer able to select anything while in recovery.. basically if i want to changes roms or whipe data and etc.. i can't do that anymore..
Is there a way to revert back to stock? ( bootloader is unlocked before this happened and rom is rooted)
Is there a way to fix this? same thing happens when i install clockworkmod recovery..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

let it boot and set for 30 min then reflash twrp and it works same thing happened to me

toolhas4degrees said:
let it boot and set for 30 min then reflash twrp and it works same thing happened to me
Click to expand...
Click to collapse
Can you recommend which version of twrp to use ? Link?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4

I"m still trying to fix this issue.. any help would be great

dilfatx said:
I"m still trying to fix this issue.. any help would be great
Click to expand...
Click to collapse
twrp 2.5 is the only one that has no issues as of now.

FIXED!
After doing some more extensive reading and trials and errors.. these two threads where helpful
[UNLOCKED BL] Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash staging blob
, hit enter and wait until it completes
Hold the power button for 10 seconds to reboot the tablet
You are now updated to Android 4.2
Click to expand...
Click to collapse
and to install recovery I used this step from the same thread
[UNLOCKED BL]-- Installing TWRP (Recovery) --
Since this new update brings a new bootloader, older recovery versions from 4.1 won't work at all. Don't try to flash one!
This guide will give you a recovery that works just fine on the new bootloader. And yes, it can read/write to an external SD just fine. Follow this steps to install the new recovery on your device:
Connect the tablet to the computer
Reboot the tablet using the proper button on the power menu, holding Volume down until you see three icons (RCK, Android and Wipe Data)
Download this file and unpack it (it contains fastboot and a version of TWRP 2.5.0.0 that works with the new bootloader)
Open a command line on the extracted folder (you can use the instructions I wrote in Method 2 if you don't know how to do this) and type
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for the script to complete. Once it is done, reboot the tablet by holding volume down and power button for 10 seconds or using
Code:
fastboot reboot
on the command line. Don't enter recovery directly!
You have now the new recovery for Android 4.2 .
Click to expand...
Click to collapse
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:

dilfatx said:
After doing some more extensive reading and trials and errors.. these two threads where helpful
and to install recovery I used this step from the same thread
from [GUIDE][14/09]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices and it was successful using this specific method :laugh:
Click to expand...
Click to collapse
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups

frankgreimes said:
Thank you for this, I have had to go back to 2.4.4 because it was the only working one, going to try this when I'm home.
Got it working (updated from 2.4.4 to 2.5.0 finally made it work thanks and now my external SD can finally be used going to buy one only for backups
Click to expand...
Click to collapse
no problem

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.

Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.

Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk

joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.

Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?

dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.

Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?

Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

Honor 6 - Unable to access recovery mode. Stuck at boot screen (honor logo)

Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath

sampathnayak09 said:
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
Click to expand...
Click to collapse
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)

How to return back to Stock Recovery & Install Stock Rom.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.

muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath

sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
@DigiGoon

@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img

@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
mahadikrs said:
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
Click to expand...
Click to collapse
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.

muradulislam said:
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
Click to expand...
Click to collapse
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.

sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs

mahadikrs said:
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
Click to expand...
Click to collapse
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.

muradulislam said:
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
Click to expand...
Click to collapse
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0

DigiGoon said:
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi,
I did flash the stock recovery, but my phone keeps rebooting and doesn't get into recovery mode.
I am sure it has sufficient battery charge. (Close to 90%).
Is there a way to do a clean install on Android phones? Like the way we install Windows OS on computers. Format hard disks, create partitions and then install a fresh OS?
Thanks

mahadikrs said:
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
Click to expand...
Click to collapse
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?

sampathnayak09 said:
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
Click to expand...
Click to collapse
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.

mahadikrs said:
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
Click to expand...
Click to collapse
Thank you for providing the links. Let me try installing these.

muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
goldfinv said:
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
Click to expand...
Click to collapse
Phone has 75% + charge as shown in TWRP recovery.

sampathnayak09 said:
Phone has 75% + charge as shown in TWRP recovery.
Click to expand...
Click to collapse
Maybe try flashing one of the custom EMUI ROMs via TWRP?
Sent from my H60-L04 using XDA Labs

@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?

sampathnayak09 said:
@[email protected]@goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Give it a couple of tries. Users have suggested that it usually gets stuck somewhere but trying for 2,3 times gets the job done.
Sent from my PLK-L01 using XDA Labs

sampathnayak09 said:
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Let me know which Rom version is your phone running now & which version you are trying to migrate to.
Also if 3 button Force update is not working then you can try the project menu option.
But first let me know what state your phone is currently in.