Database Users

I got soft bricked after OTA (HELP)

Hello everyone first of all english is my second language and i can make mistakes please dont put sarcastic comments about how bad i type or how big noob am i. Secondly my issue is , i accidently pressed install update at my phone which was running at 4.2.2 .(4.4.2) OTA i guess then some think like fastboot mode 840 popped up.(i used to have htc one x) and this code seemed familiar to me so i downdloaded twrp recovery (latest version) unzipped it to get the recovery.img and used the command fastboot flash recovery recovery.img i thougt i fixed my phone but my got more bricked know it says boot verification and opens at a black screen when i plug it in i see somethink like this oi57.tinypic{dot}com/r888sg.png (i only have a driver c) others is somehow connected to phone itself . what can i do ? all help will be apriciated .
I might be a newbie at this stuff but i am trying my best . thank you sincerly
edit:when i try to use adb i get a massage like this
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Minimal ADB and Fastboot>dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of
=/sdcard/fota-backup.img
'dd' iç ya da dış komut, çalıştırılabilir
program ya da toplu iş dosyası olarak tanınmıyor.
C:\Minimal ADB and Fastboot>adb push loki_flash /data/local/tmp/loki_flash
error: device not found
C:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse

Edit : i used this code to alter my recovery and flash twrp which somehowed killed my phone
Code:
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (8650 KB)...
OKAY [ 0.335s]
writing 'recovery'...
OKAY [ 0.995s]
finished. total time: 1.334s

Flashing a KDZ from scratch doesn't help?

robogo1982 said:
Flashing a KDZ from scratch doesn't help?
Click to expand...
Click to collapse
i kinda fixed it but my cache partiton got corrupted . im in ubuntu and i cant install anythink i cant mount cache , when i try to install another rom it says permission denied

Please Help me! I can't flash stock rom

Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery

Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.

I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux

daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later

Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.

daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery

Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .

This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo

sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble

Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.

I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...

Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.

Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?

Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again

Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here

Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .

Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img

Help me please i can't flash twrp oneplus 5 FAILED

oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest

abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
Click to expand...
Click to collapse
Try 'boot recovery.img' then flash it via twrp

Krsambhav16 said:
Try 'boot recovery.img' then flash it via twrp
Click to expand...
Click to collapse
how to try boot recovery
please explain

abuawaahed said:
how to try boot recovery
please explain
Click to expand...
Click to collapse
I'm sorry but you seem to be doing something without researching or understanding what it is. If you don't know what you're doing please don't do it.

abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest
Click to expand...
Click to collapse
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win

pankajsammal said:
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win
Click to expand...
Click to collapse
git bash for what

@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...

abuawaahed said:
git bash for what
Click to expand...
Click to collapse
Used gitbash terminal to use the fastboot command to flash recovery.

mukesh22584 said:
@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...
Click to expand...
Click to collapse
thanks but also not working
fastboot erase recovery
failed (remote :unknown command )
fastboot erase cache
failed (remote :unknown command )

pankajsammal said:
Used gitbash terminal to use the fastboot command to flash recovery.
Click to expand...
Click to collapse
$ fastboot flash recovery twrp-3.1.1-0-oneplus5.img
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
also failed

Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....

And which version you are using adb&fastboot setup and drivers? Try different versions Adb setup 1.4.3 example.

mukesh22584 said:
Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....
Click to expand...
Click to collapse
yes unlocked bootloader done
oem enable
usb debugging on

Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here

Gonik said:
Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here
Click to expand...
Click to collapse
not working
i think because of oxygenos 4.5.5

abuawaahed said:
not working
i think because of oxygenos 4.5.5
Click to expand...
Click to collapse
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5

just update to latest fastboot/adb package and flashing should be fine.

inffy said:
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5
Click to expand...
Click to collapse
see image unlock bootloader is ok

acmerw said:
just update to latest fastboot/adb package and flashing should be fine.
Click to expand...
Click to collapse
adb-setup-1.4.3 installed

I had the exact same issue, my main rig is on the latest update of windows so the adb minimal drivers couldn't install properly (windows problem)
so tried to do this on my laptop (not on the latest update) and was able to install the drivers.
Now when it came to flashing the recovery - I kept getting the same error as you.
To fix this I tried a different USB port (2.0) and it worked.
Give it a try, should work now.

Cannot Unlock Bootloader (HELP!)

Hello, I received yesterday my Zuk Edge, and I wanted to unlock the bootloader. So I enter to the web page and get my unlock_bootloader.img
I then proceed to fastboot flash it, but I'm always getting this message back:
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.034s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.064s
I already tried different commands, and every time I get the same response back.
Also, I want to flash the official firmware via Qfil, but i can't get it to recognise the device. I already installed the lenovo, zuk and qualcomm drivers.
Can someone please help me?
Thanks

Hi there,
Did you change settings Debug USB and OEM Unlock in Developer Settings to On?
Regards

PanNet said:
Hi there,
Did you change settings Debug USB and OEM Unlock in Developer Settings to On?
Regards
Click to expand...
Click to collapse
Yes, I did that. I found the solution after the installation of different drivers. I will post a guide on how I did this, as I think there is no noob friendly step by step guide.
Thanks for your reply!

oalf170892 said:
Yes, I did that. I found the solution after the installation of different drivers. I will post a guide on how I did this, as I think there is no noob friendly step by step guide.
Thanks for your reply!
Click to expand...
Click to collapse
I have the same problem Can You help me? thanks.

emailyn said:
I have the same problem Can You help me? thanks.
Click to expand...
Click to collapse
Me to, I have Android 6 on mine and no way to OTA update, how do I get Android 7 on this ?

emailyn said:
I have the same problem Can You help me? thanks.
Click to expand...
Click to collapse
I share the drivers I installed and after that, evrything worked.
https://mega.nz/#F!eolnyZqa!oTTrtqJFeG708JSTcRjhzQ

HUAWEI P10 Lite help to unlock after LCD replacement

Hello,
I'm new to this forum, so please excuse me if this is not correct section to post.
I'm more used to Samsung and ODIN, first time i encounter this situation with Huawei
Here is the situation.:
Had to replace a LCD of a Huawei P10 Lite for a client. (WAS-LX1A model)
I did it, without issue...
Tested the replacement LCD (without glue it) display OK touchscreen OK
It went to the welcome screen asking for the PIN code to unlock the screen/
Ok so i turn it off.
Finish the replacement fix
Turning it back i got infinite loopboot ... showing HUAWEI logo , and rebooting all the times....
Trying to go to recovery mode holding VOL+ VOL- without success
The only key giving a reaction is VOL- going to FASTBOOT
This is the information i got the first time i went to FASTBOOT
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
( i did it but the phone is NOT detected in HiSuite,
but the phone is recognized on my Devices Manager of my Windows 10 laptop
under the name
KEDACOM USB DEVICE
> Android Bootloader Interface
so to continue what i had on my screen 1st time i went into Fastboot
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
Android reboot reason:
coldboot 16
NA
volumnkey_down_press_process_func
Phone Locked
FRP Lock
Click to expand...
Click to collapse
:'(
I don't understand why i get the FRP lock, usually its when you format and try to bypass the password of the google account (usually occuring when trying to ovveride this protection with stolen smartphones...) but here its not the case.
A few minutes before the smartphone asked me to encode the PIN code of unlocking screen (for my client its not a schema its a PIN code) i just tried 2 numbers and i even not validated my input i just turned off the phone ....
Well anyway, no when i go again in the fastboot the message is different and is always this one now
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_PMU 144
ocp_ldo17 ocp_ldo31
volumnkey_down_press_process_func
Phone Locked
FRP Lock
Click to expand...
Click to collapse
What have i tried already ?
i downloaded a TWRP image of 22 MB , installed " Minimal ADB and fastboot " SDK
with ADB i can't see the device
with FASTBOOT i can list the device
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
2XJ7N17406000665 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
but any other command (except fastboot reboot) fails,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk p10twrp04.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24954 KB)...
OKAY [ 0.736s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.748s
C:\Program Files (x86)\Minimal ADB and Fastboot>
....So what should i do next ?
Enabling the Developer Debbung USB option in the menu of the smartphone ?
How come ? the phone can't boot android so i can't access the options menu ..... :'(
Thanks in advance for you help

Try this - https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946

Same problem, I have changed LCD and the touch does not work if I restart, if I do it in hot it works.
Does anyone know any solution? Thanks