Database Users

[GUIDE] How To Enter Fastboot Mode

This is the method tried on H815T model. But I think this should work with also other H815 models (other devices cannot say). Thanks to @autoprime, @thecubed and @Unjustified Dev for this.
Disclaimer: I am not responsible if your device gets into any more trouble for this.
Steps:
1. Download & clean install LG Drivers in your pc if u don't have it already.
2. Go into download mode by presing down the UP button and connecting the usb cable to the pc.
3. Go into LG ROOT folder. see this link to download: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
4. Double click on ports.bat to know your COM port. Let's say it's COM4.
5. Open a windows command promt by Shift+Rt Click into the Lg Root folder.
6. Now send these commands:
Code:
Send_Command.exe \\.\COM4
It will reply
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
7. Now command type
Code:
id
It should reply
Code:
uid=(0)root gid=(0)root
#
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
9. Now pull out your battery, put it back in, go into HARD RESET mode by pressing down DOWN BUTTON+POWER BUTTON together and when the LG logo apprears, release the power button for a second and press it back again.
10. Now in HARD RESET, it will ask you whether you want to reset everything or not. Select "No" and it will take you to fastboot mode.
Special note:
1. @autoprime told me to factory reset everything before starting this whole process. I did as my bootloader was locked. Don't know how it affects in unlocked bootloader.
2. How to get out of fastboot normally: I don't know it quitely. My bootloader was locked, so neither I could flash any system file through fastboot, nor "fastboot reboot" or "fastboot reboot bootloader" worked for me. @autoprime told me to get out of fastboot, manually go into download mode, then pull out your battery and put back in. Actually you can't get out of the fastboot that way until you flash a KDZ.
Thank u. Reply in the comments if fastboot could help you any.

delete

Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!

TheBledard said:
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
Click to expand...
Click to collapse
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.

nipun1110 said:
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
Click to expand...
Click to collapse
I couldn't get into Fastboot at all. Any command typed in send_command.exe gives "Fail" as result... Phone is connected in Download Mode and recognized in Windows, DIAG1 port is COM4.
Screenshot attached

lock bootloader , fastboot unnecessary

29y6145 said:
lock bootloader , fastboot unnecessary
Click to expand...
Click to collapse
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk

I always get a "FAIL" reply. Any ideas?

nipun1110 said:
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader...
Code:
adb reboot bootloader

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Hahahah tru!

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
maybe u r suggesting to say
fastboot reboot bootloader
right?
Sent from my LG-H815 using Tapatalk

This does not work for me, I have an unlocked bootloader, but just get the response "FAIL".

And... Why don't you just zero the laf partition instead through an adb shell? What does this do that's different?

If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.

petermg said:
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
Click to expand...
Click to collapse
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.

autoprime said:
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
Click to expand...
Click to collapse
Ok then if u suggesting me I should delete the post, I will ask Moderator to do so.
Sent from my LG-H815 using Tapatalk

It's good

Holly molly sir! You are a legend. Long story not so short. My lg got the bootloop bug. Took 2 months to fix, but apparently they changed my locked to three uk H815 "eu open" motherboard with actually unlocked one. So I was finally able to unlock boot-loader, root and **** up (LOL). Apparently I didn't install twrp properly (you'd think "fastboot boot twrp.img" would not install it but run it once) And i was following this to get Android M on. But it requires reboot before boot-loader is flashed. Right when i clicked reboot i figured it wont start in twrp but in stock recovery. So I couldn't even get proper bootloop, it would cut half way into the LG logo. I reckon kdz-ing would havedone the trick, but god it takes ages to DL the kdz file. So in the mean time i found this legendary post. The odd thing was i had to click Yes, on the factory reset screen, but it got me to "Fastboot mode started" and from there i booted into twrp and finished what it had started, currently its Optimising app 35 of 55. Nice one OP, Nice One!

hi i have unlocked bootloader. but i keep getting FAIL as response

nipun1110 said:
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
Click to expand...
Click to collapse
Hi,
how can I change it back to default Factory reset??

Locked Boot loader, Encrypted Device, BootLoop, No Recovery/ Factor. HELP

So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.

can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys

It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse

Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.

What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk

an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.

SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.

tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.

Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s

That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock

Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.

So any luck to boot this sucker ? Don't even have stock recovery ..

have you tried "fastboot boot boot.img" from the correct factory image ?

Boot loop plus no recovery equals BLOD. Sorry but likely you are done.

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

How to uninstall CWM from Huawei P8, B200, rolled back from MM

I don't have an unlocked bootloader and i flashed the CWM. Now when i try to enter the recovery mode with buttons, nothing happens just turns the phone on normally. I searched for stock recoveries, but didn't found nothing.
I have GRA-L09, B200, Europe Open
Thanks for help!

To get an unlocked bootloader you must go to settings> about phone> build number
and then press build number 7 times
after you did that exit out of about phone then click on the newly-appeared 'developer settings'
there you should find OEM Unlocking and Enable USB Debugging
You'll get it from there.

I have the Dev Ops, but don't have OEM unlock.

But shouldn't you already have an unlocked bootloader to have DevOps?

Don't know. I don't typed any code in to unlock bootloader.

Are you sure you have DevOps?
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
And also try to do it not with buttons, but with your computer
I don't know the script for how to boot into recovery mode but to fastboot, for example, you'd type in >fastboot
when your phone is connected to your PC via USB.
Y'know, just search up 'How to use Recovery Mode' - maybe you just did it wrong

Didn't tryed it w/ adb yet.

ADB didn't worked. I'm trying a full hard reset..

Hard reset didn't do nothing. HELP PLS!!

adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?

TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?

GaT7 said:
That means you have a locked bootloader, so CWM didn't install successfully.
In other words, you need to unlock the bootloader first in order to successfully install CWM.
So, 1st step - visit the Huawei unlocking code request page, taking your time to fill in the form accurately & submit it.
[Btw, if you don't already have a Huawei ID, you can register for one here: http://www-file.huawei.com/en/my-huawei/register
Then use these login details in the above link to request for the unlock code]
2nd step: Once you receive the unlock code from them, use it to unlock the bootloader by issuing the following command in fastboot mode [the asterisks (*) represent your 16-digit unlock code]:
Code:
fastboot oem unlock ****************
Now you can attempt to install CWM. Where are you getting the CWM img file from?
Click to expand...
Click to collapse
Sorry, "Phone Unlocked" with red

TheGolem said:
Sorry, "Phone Unlocked" with red
Click to expand...
Click to collapse
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo

Ok, I just read your post in the other thread about wanting to update B200 to B370.
TheGolem said:
I have b200 but can't install it [B370]. Why?
Early flashed the CWM with flashify succesfully, but don't have unlocked bootloader. And if i try to enter recovery mode, nothing happens. Is it possible, that i cant' install it because of this?
Click to expand...
Click to collapse
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.

GaT7 said:
Ok, I just read your post in the other thread about wanting to update B200 to B370.
As the guys already said, you do not need to install anything in order to update an official rom.
So, let's leave out CWM, bootloaders, etc for now, & help you update only from B200.
When you try using TopperBG's method to update, what happens?
What is your current FULL firmware version? It will be in this format: GRA-L09CxxxB200 - if everything else is as I've mentioned, I'm interested in the Cxxx part.
Click to expand...
Click to collapse
Update succeed, it wroks fine. The problem is with the recovery mode.
When i'm trying the button method to enter recover, the phone just normally turns on. When still hold the buttons, black screen. It's with the abd too.

TheGolem said:
adb reboot-bootloader worked, but it has a subtitle: Phone Locked (with red). What is it?
Click to expand...
Click to collapse
you don't have a unlocked bootloader so you can't have cwm

I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.

TheGolem said:
I said it wrong:
-Android 5 succeed
-If i try to install Android 6
https://forum.xda-developers.com/huawei-p8/how-to/emui4-0-1-p8-official-marshmallow-6-0-t3417212
or enter recovery mode, then happens the black screen.
Click to expand...
Click to collapse
1. You need to install stock recovery for android 5(unlocked bootloader is required).
2. Then you can use the dload method to update.
3. You can flash TWRP after that because no-one uses CWM.

GaT7 said:
Ok, so it appears you may have corrupted the recovery partition.
Is the phone otherwise booting into the system & functioning normally?
Also, can you tell us what you are wanting to ultimately achieve by installing CWM?
Just to confirm the bootloader is unlocked, run this command in fastboot mode & let us know the result:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Phone normally booting, no problem with current system.
I typed in the command, and its <waiting for device>.

GaT7 said:
Where are you getting the CWM img file from?
Click to expand...
Click to collapse
http://www.teamandroid.com/2015/06/07/install-huawei-p8-clockworkmod-recovery/2/
Step 5
cwm-p8-nogui.img

[Huawei Y5-II] Bootloader OEM Unlock

Hello, this morning I was making a Factory reset on my phone, but when i was gonna login with my Gmail account i realized that i've forgotten the password, and the recovery number was inactive so i couldnt recover my account, then I flashed a Update.app but it didnt work either, then I put the device in fastboot mode to flash a recovery.IMG but when im gonna active the "Unlock OEM" in developer settings (the device is in Cofiguration interface) so when i ingress to Setting Menu, and i give in Compilation Number it doesnt work, so i really dont know what to do now, if anyone can help me ill will apreciate it!!

reynoxo said:
Hello, this morning I was making a Factory reset on my phone, but when i was gonna login with my Gmail account i realized that i've forgotten the password, and the recovery number was inactive so i couldnt recover my account, then I flashed a Update.app but it didnt work either, then I put the device in fastboot mode to flash a recovery.IMG but when im gonna active the "Unlock OEM" in developer settings (the device is in Cofiguration interface) so when i ingress to Setting Menu, and i give in Compilation Number it doesnt work, so i really dont know what to do now, if anyone can help me ill will apreciate it!!
Click to expand...
Click to collapse
I am sorry i couldn't understand the latter half of your post.
What do you want to do? Unlock your bootloader? Flash recovery? or factory reset?

dev.kasibhatla said:
I am sorry i couldn't understand the latter half of your post.
What do you want to do? Unlock your bootloader? Flash recovery? or factory reset?
Click to expand...
Click to collapse
I need to install a custom recovery and to do that I need to unlock bootloader mode

reynoxo said:
I need to install a custom recovery and to do that I need to unlock bootloader mode
Click to expand...
Click to collapse
Fine i ll type down steps in max detail for you.
Go to developer options, enable usb debugging and oem unlock.
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
[/LIST]
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. You can also flash the recovery using fastboot flash command.

dev.kasibhatla said:
Fine i ll type down steps in max detail for you.
Go to developer options, enable usb debugging and oem unlock.
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
[/LIST]
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. You can also flash the recovery using fastboot flash command.
Click to expand...
Click to collapse
Thank you very much, it was very helpful.

hi,i like unlock bootloader - right check usb debuging,oem unlock?fastboot oem unlock and say this : FAILED (remote:size is wrong)?