As you can see in the title, i decided to write a small fastboot tut, especially for our p880 and its "own" commands and tricks
I am, as always, not responsible for what you do with your device. Do it on your own risk.
I will however not explain on how to set up fastboot on your PC. There are tons of tuts out there on xda, just search for it
NOTICE: You need an unlocked bootloader for this
Screenshots will be added later, 'cause my lappy is compiling right now and i thought i could use the time to write this so just wait a bit
Now, lets begin with the fun, shall we?
General
Fastboot is usually quite easy to use. But if you went searching for a tut on the web, you might have noticed that it doesn't work the way it should on your device.
That's because LG messed something up in the bootloader, but let's don't worry about that now, it does work nontheless
Fastboot is "a part" of the bootloader. This means, neither the kernel (boot), nor the recovery gets booted.
That gives you the ability to flash, but also boot kernels/recoveries. And yes, i meant booting, without really flashing it
Now we need to get into fastboot mode:
And this is (one of) the point(s) where LG messed up. The usual command is "adb reboot bootloader". But this command does not work on your device the way it should.
It gets you into a kind of fastboot mode, but you can't flash anything, because it says the bootloader would be locked, even tho it isn't.
The working command is
Code:
adb reboot oem-unlock
i guess this command sounds familliar, doesn't it? and don't worry, it will not lead you to a menu that deletes your data.
It will lead you to the working fastboot mode
now we're in the working fastboot mode. To check if you've set up fastboot correctly, type
Code:
fastboot devices
this should list your phone and its serial number.
It is recognized? good. so now we might want to check the status of our device (BL unlock state, serial number,...).
Therefore type
Code:
fastboot getvar all
now you can check whether it's really unlocked or not.
If everything's fine, you might want to...
Flash something
In order to flash something, you need the appropriate image. For kernels it's mostly "boot.img"
The command to flash something via fastboot is in general
Code:
fastboot flash <partition> <filename>
Example: You want to flash a kernel (named test_boot.img) and you have downloaded the kernel to the folder where your fastboot.exe is.
So you type
Code:
fastboot flash boot test_boot.img
This will copy the kernel to your device and then flash it to the LNX (boot) partition.
Of course you can flash other partitions, too, like system, data, cache, recovery...
After a flash, it is wise to clear the cache, or even your /data partition...
Deleting a partition
You don't need a recovery to wipe a partition, just use fastboot
The general command is
Code:
fastboot erase <partition>
For our example it's enough to wipe the cache. You can do this using this command:
Code:
fastboot erase cache
Also here you can wipe all partitions, like system, data, cache, boot, recovery...
So now we've flashed what we wanted to, wiped the needed partitions, but how do i..
Get out of fastboot
This is as easy as getting in just type
Code:
fastboot reboot
to reboot the device (Here's another thing, where LG messed up.... it reboots, but stays at the LG spash screen.
So press the power button for at least 10 secs. Now your device will reboot into recovery (!?)
then just tap reboot system now and be happy )
or
Code:
fastboot continue
this one will not reboot the device, but continue the boot procedure. I, for one, would suggest you to use the first command
now your device will boot up normally (except your kernel/system.... has a bug of course )
for more help, just type
Code:
fastboot help
and the last point is...
Bricking the device
nah, just kidding
Reserved
Thanks for this usefull post!
Sent from my LG-P880 using xda app-developers app
thanks, it's very useful for me.:good:
Thanks,
it's so easy
fastboot boot <kernel> <ramdisk> -c "androidboot.mode=normal"
Click to expand...
Click to collapse
<kernel> is the kernel zImage
<ramdisk> can be a .img, .cpio, .cpio.gz
-c "androidboot.mode=normal” is needed the get the kernel booted for the p880 with the correct commandline
Gesendet von meinem LG-P880 mit Tapatalk 4 Beta
So, to get into fastboot mode, I have to turn on my phone, plug it to my computer and in cmd I type adb reboot oem-unlock, right? Is there any possibility to access it in case of a bootloop or something?
boot into recovery system by holding power+vol-down till it vibrates, then use either adb to issue the command or when using twrp as recovery system: Reboot --> Fastboot
Gesendet von meinem LG-P880 mit Tapatalk 4 Beta
A little update from LG...
I wrote them that they have messed up our bootloader, and told them the bugs/problems/... well, see yourself:
1) "adb reboot bootloader" doesn't bring me into bootloader. Well it does, but even though i have unlocked the bootloader, it still says it would be locked.
instead i need to use "adb reboot oem-unlock" to get into bootloader.
- P880 does not support "adb reboot bootloader" to go into bootloader. P880 only works "adb reboot oem-unlock" instead of "adb reboot bootloader" to go into bootloader. and then you can use the fastboot command mode after accept unlock bootloader.
2) "fastboot reboot" partly reboots the device, but then it keeps stuck at the first LG splash screen. pressing power button for 10 seconds brings me into recovery then, instead of into the ROM.
- P880 supports "fastboot reboot", before flashing the customize image, "fastboot reboot" reboot normally.
3) "fastboot flash system [path/to/system.img]" gives me "fatal error: unknown partition"
- P880 can only flash boot, recovery. Ex> fastboot flash boot/recovery boot.img/recovery.img
4) "fastboot boot [...]" doesn't work at all.
- P880 does not support "fastboot boot [...]" command
- P880 supports only flash, erase, reboot as you already seen in bootloader unlock warning message.
5) I have found no way to boot into fastboot/bootloader without a booting phone. Maybe you could try to add the possibility to boot directly into fastboot.
- You can only go into fastboot mode using "adb reboot oem-unlock"
Click to expand...
Click to collapse
lg is retarded, but hey atleast they had the decency to answer
Yeh, you need to kdz flash if you mess up both system and recovery.
Keep an suid busybox in /data so you can root and re-flash CWM/TWRP in the backup+restore mode without having to clear data so the stock ROM can boot.
Can't seem to get his wokring properly, think it's the drivers.
I connect my phone to the pc, run cmd and I reboot it to to the bootloader. From there, I can't do anything. I i Write "fastboot devices" I get nothing, can't flash anything either. Have tried the official drivers from lg, but it doesn't work.
That's the same way of using fastboot like it is on Sony devices, you should mention it so more people would use this guide.
The only difference is that on sony devices if you want to unlock your bootloader you need to get the key from this site and then fastboot 0x0fce oem unlock 0xKEY
hi dudes , if phone (4x hd) is in s/w update mode , can I use fastboot command?
ppl, i beg for help:
when I use adb reboot oem-unlock or adb reboot bootloader, my phone only resets itself and boots back into normal working mode. I've tried to boot it into bootloader with holding volume up and power button and it boots into some kind of mode wheres only picture with symbols of mobile with symbols of data cable and power cable being plugged into phone with red symbol over cables that they shouldn't be unplugged. I've also tried eboot oem-unlock and reboot bootloader commands in that mode and it only resets the phone back into normal working mode while command fastboot flash recovery twrp.img only gave me "waiting for the device" and nothing happening...
also I've entered into hidden menu with 3845#*880# command bit there's no "BL status" or "Bootloader Unlock Check" or anything that has any connection to Bootloader
help?
@gesaugen: Works only with firmware 20A and higher.
GoodSoul said:
@gesaugen: Works only with firmware 20A and higher.
Click to expand...
Click to collapse
GoodSoul, thanks for info!
So I only need to upgrade firmware and it should work then...
I tried this method and for fastboot devices
i get no permissions fastboot
pls help
edit: i just did it with sudo fastboot devices
but i have another error:
fastboot flash zimage zImage
sending 'zimage' (4913 KB)...
OKAY [ 1.216s]
writing 'zimage'...
FAILED (remote: Invalid Partition Name.)
InterrtuptoR said:
but i have another error:
fastboot flash zimage zImage
sending 'zimage' (4913 KB)...
OKAY [ 1.216s]
writing 'zimage'...
FAILED (remote: Invalid Partition Name.)
Click to expand...
Click to collapse
Only "boot" and "recovery" are supported for fastboot flash command. Boot is the kernel and takes boot.img. Unfortunately, "system" is not supported, otherwise developing on this phone would have been similar to Nexus devices.
Related
Please help in big trouble.. my phone is stuck at Fastboot screen.. Nothing is working no volume keys nothing... What did i Do:
Unlocked bootloader...
and then I was trying to flash a custom recovery but after typing fastboot boot recovery.img.. it showed something like booting and then it finished.. Then in the tutorial it was written :
Perform a nandroid backup.
After nandroid backup is done, reboot the device in fastboot mode again.
In the Command Prompt type following command: fastboot flash recovery recovery.img
BUt i didn't performed a nandroid backup and straight after fastboot boot recovery.img was done I typed fastboot flash recovery recovery.img.... and now nothing is happening so I quit command prompt and unplugged usb but still I cant do anything and the phone is stuck at fastbood mode. When i am trying to connect usb it's saying usb not recognized... PLEASE HELP ME!
PC is not detecting my phone now.
anuragvivek93 said:
Please help in big trouble.. my phone is stuck at Fastboot screen.. Nothing is working no volume keys nothing... What did i Do:
Unlocked bootloader...
and then I was trying to flash a custom recovery but after typing fastboot boot recovery.img.. it showed something like booting and then it finished.. Then in the tutorial it was written :
Perform a nandroid backup.
After nandroid backup is done, reboot the device in fastboot mode again.
In the Command Prompt type following command: fastboot flash recovery <name of recovery>.img
BUt i didn't performed a nandroid backup and straight after fastboot boot recovery.img was done I typed fastboot flash recovery recovery.img.... and now nothing is happening so I quit command prompt and unplugged usb but still I cant do anything and the phone is stuck at fastbood mode. When i am trying to connect usb it's saying usb not recognized... PLEASE HELP ME!
PC is not detecting my phone now.
Click to expand...
Click to collapse
Not sure what thread you are following.. but steps don't sound correct.
Depending on the hboot you are on the fastboot boot recovery.img.. doesn't work.
to flash recovery you should have used fastboot flash recovery recovery.img
what happens if you hold down volume button and power for 10-20secs will it reboot to bootloader? If so from bootloader hit the power button to get to fastboot USB then select reboot option.
If nothing is working other option let phone go flat, then recharge and try again.
Is your device s-off?
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
rafaelbrunner said:
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
Click to expand...
Click to collapse
I'm sorry about multiple topics... my bad.... but you can erase the other in general topic....
but to flash i need to be in recovery mode at boolloader, no?
i can do this command in bootloader menu?
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Fastboot and recovery are two different things. If you can get to Fastboot (bootloader) mode you should be able to flash recovery from there as stated by rafaelbrunner.
Hi Guys !
I'm facing a problem on rooting my Moto G 2014.
I've easily unlocked the bootloader but i can't flash the TWRP recovery.
I've read everything I could read about the process and I think I'm doing it the right way (the recovery file in the adb folder, etc...) and everything seems to be ok.
I've just a purple line at the end of the TWRP flashing procedure saying:
Mismatched partition size (recovery)
This post says that it's not really a problem: http://forum.xda-developers.com/showpost.php?p=48294073&postcount=6
Then, when I reboot the recovery, the phone reboots and the system starts normally (instead of restarting with the custom recovery ?). When I switch it off and switch it on in recovery mode, I still have the stock recovery.
Tried several times with TWRP 2.8.0.1
I can't say if it's because of a problem with TWRP (it's said here that it is buggy) or because I'm doing something wrong that I don't succeed.
I saw that there was a 2.7.1.1 release of TWRP for Moto G 2014 but it's no more available anywhere for now. I would have liked to try it...
Do you know if there's some known issues about flashing the Moto G 2014 recovery or can you help in any way ?
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWAP2801 titan-motog-2014.img
target reported max download size of 536870912 bytes
sending 'recovery' (9738 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 0.700s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
error: device not found
C:\Program Files <x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
magmatik said:
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
Click to expand...
Click to collapse
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
2987
jbanti said:
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
Click to expand...
Click to collapse
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
magmatik said:
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
Click to expand...
Click to collapse
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
1932
eskamhl said:
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
Click to expand...
Click to collapse
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
magmatik said:
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
Click to expand...
Click to collapse
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
eskamhl said:
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
Click to expand...
Click to collapse
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
magmatik said:
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
Click to expand...
Click to collapse
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
eskamhl said:
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
Click to expand...
Click to collapse
When I try to boot into recovery from the bootloader (what I already did before), the screen turns black, 1 sec later the led switch on for half a sec and nothing else happends.
So, as you say, the recovery I downloaded was maybe corrupted. I'll check.
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
magmatik said:
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
Click to expand...
Click to collapse
My friend... a few posts above
eskamhl said:
now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select )
Click to expand...
Click to collapse
I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...
eskamhl said:
My friend... a few posts above
Click to expand...
Click to collapse
You're right... my bad
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
AzweL said:
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
Click to expand...
Click to collapse
The very first thing I recommend you to do, is to download the right recovery and install it via command
Code:
fastboot flash recovery recovery.zip
Let me know if you run into any further troubles.
AzweL said:
Hey,
My phone is stuck in the fastboot mode, without any OS, nothing works... no Recovery ,...
S-ON, no-debugging usb, Bootloader locked and can't unlock him... I already tried with htc-dev, everything works but nothing appair on my screen to confirm the unlocking.
I'm really stuck, searched lot of things on google, ....
I used fastboot, and ADB, the first one recognize my device, but the last one not. I can't boot on RUU mode neither.
Any ideas?
Click to expand...
Click to collapse
Hi,
Frist in boot loader check your OS version it should be something like 2.19.401.2 or lower than this.
NB: ALWAYS TRY WITH MORE THAN 75% BATTERY, AND THAT FOR ANY CODE TO WORK PROPERLY, MAKE SURE TO SELECT FASTBOOT BY POWER KEY IN BOOTLOADER
Anyway, if you can enter fastboot, then you have some chance of recovering your device and because you have S-Off it is going to be a bit difficult.
First download this stock boot file : https://mega.nz/#!lEAVwRSL!wrP2hi6GEYLeJaPf2ssZo9wCtSi7E4yfyUHgh3Q3XSs
Then place this file in the ADB folder, then run command :
To flash boot file command is:
Code:
- Fastboot Devices (this command is important to know if the device is connected and accepting and responding commands)
- fastboot flash boot boot_signed.mg (assuming this is the name you saved the file with)
- fastboot reboot bootloader
Also download Stock Recovery: https://mega.nz/#!gVJE1Bxa!6SwXStAD8p-XlnQiPkRcdNo_ITFD1ykn-tN6wIBVi1I
Place this in ADB folder and run command:
Code:
fastboot flash recovery stockrec.img // (assuming that is the name you have saved the file with), only after flashing this you will know if the device has any OS, if OS exists it will boot up.
fastboot erase cache
Attempt and let us know how it went...Good Luck
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.
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.