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,
My CLT-L09 (UK Model with 128GB of Memory and 6GB of Ram) is in a bootloop after I screwed up. I've got access to Fastboot and eRecovery, but eRecovery is refusing to download a fresh image. It always complains of a server error, even though I can see a good connection going out to Huawei in my firewall logs. The two are talking to each other. I suspect Huawei doesn't like my phone!
Anyone have a copy of the STANDARD recovery ramdisk they could share? I've tried the CLT-L29 standard ramdisk, the "recovery_ramdisk_nocheckP20.img", the "recovery_ramdisk_BKL-L04_nocheck.img" and none of them coax eRecovery into downloading a fresh image and fixing my phone.
Any ideas?
Cheers,
Mich
mictho100 said:
HI All,
My CLT-L09 (UK Model with 128GB of Memory and 6GB of Ram) is in a bootloop after I screwed up. I've got access to Fastboot and eRecovery, but eRecovery is refusing to download a fresh image. It always complains of a server error, even though I can see a good connection going out to Huawei in my firewall logs. The two are talking to each other. I suspect Huawei doesn't like my phone!
Anyone have a copy of the STANDARD recovery ramdisk they could share? I've tried the CLT-L29 standard ramdisk, the "recovery_ramdisk_nocheckP20.img", the "recovery_ramdisk_BKL-L04_nocheck.img" and none of them coax eRecovery into downloading a fresh image and fixing my phone.
Any ideas?
Cheers,
Mich
Click to expand...
Click to collapse
eRecovery and Recovery Ramdisk are separate partitions. Flashing different recoveries won't affect how eRecovery works. Is your bootloader unlocked? How did you get into bootloop state?
danifilth4king said:
eRecovery and Recovery Ramdisk are separate partitions. Flashing different recoveries won't affect how eRecovery works. Is your bootloader unlocked? How did you get into bootloop state?
Click to expand...
Click to collapse
Thanks for your fast reply!
So, you may have figured that I am merely a follower of instructions, when it comes to flashing phones.... Unfortunately I screwed up and neglected a small but very important details when I followed this thread: https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
My phone is the CLT-L09. But for some bizarre reason I thought I had the CLT-L29. No idea how I got that idea! I was on build 110, like a lot of unfortunate people, and I was sick and tired of not getting timely security updates. So I took matters into my own hands (which I regret now....)
I followed the above thread and managed to get my phone onto CLT-L29C432B131A. And it worked! At first I was quite happy, but then I found some issues.
I found was that the build number was showing up as "Chipset-boston 8.1.0.001(01V2)". And I was having issues with a bunch of apps not wanting to show up in Google Play for my phone, which I have had on this phone before flashing it. For example Netflix and Amazon! I knew then that I couldn't stay on this build and had to find a way back onto the legit L09 release.
I followed https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 again trying to apply a L09 release, but it didn't work. I could get proper root anymore, no matter what I tried. I also tried the HuRu updater, and that didn't make any difference. The CLT-L29C432B131A image I managed to get myself on just didn't want to budge from the phone.
In my desperation (and lack of understanding!) I started playing with different ramdisk images, trying to get eRecovery to allow me to re-image the phone.
So, long story short; I am now at the point where all I have is two things:
1 - eRecovery boots, but refuses to re-image my phone with a "Getting package info failed" error. I suppose my L29/L09 image mix is confusing the sh!t out of it!
2 - Fastboot works and allows me to flash ramdisk images
3 - TWRP 3.2.0 *was* working until this morning, but has now quit. Not sure how I broke that.
Is there any way back from this?
mictho100 said:
Thanks for your fast reply!
So, you may have figured that I am merely a follower of instructions, when it comes to flashing phones.... Unfortunately I screwed up and neglected a small but very important details when I followed this thread: https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
My phone is the CLT-L09. But for some bizarre reason I thought I had the CLT-L29. No idea how I got that idea! I was on build 110, like a lot of unfortunate people, and I was sick and tired of not getting timely security updates. So I took matters into my own hands (which I regret now....)
I followed the above thread and managed to get my phone onto CLT-L29C432B131A. And it worked! At first I was quite happy, but then I found some issues.
I found was that the build number was showing up as "Chipset-boston 8.1.0.001(01V2)". And I was having issues with a bunch of apps not wanting to show up in Google Play for my phone, which I have had on this phone before flashing it. For example Netflix and Amazon! I knew then that I couldn't stay on this build and had to find a way back onto the legit L09 release.
I followed https://forum.xda-developers.com/huawei-p20/how-to/rebrand-huawei-p20-eml-l29-eml-l09-t3779283 again trying to apply a L09 release, but it didn't work. I could get proper root anymore, no matter what I tried. I also tried the HuRu updater, and that didn't make any difference. The CLT-L29C432B131A image I managed to get myself on just didn't want to budge from the phone.
In my desperation (and lack of understanding!) I started playing with different ramdisk images, trying to get eRecovery to allow me to re-image the phone.
So, long story short; I am now at the point where all I have is two things:
1 - eRecovery boots, but refuses to re-image my phone with a "Getting package info failed" error. I suppose my L29/L09 image mix is confusing the sh!t out of it!
2 - Fastboot works and allows me to flash ramdisk images
3 - TWRP 3.2.0 *was* working until this morning, but has now quit. Not sure how I broke that.
Is there any way back from this?
Click to expand...
Click to collapse
Run this command in fastboot:
fastboot oem get-product-model
This will help you figure out what model your phone thinks it is.
And this command:
fastboot getvar vendorcountry
Will help you figure out what region it's currently on. Let me know.
danifilth4king said:
Run this command in fastboot:
fastboot oem get-product-model
This will help you figure out what model your phone thinks it is.
And this command:
fastboot getvar vendorcountry
Will help you figure out what region it's currently on. Let me know.
Click to expand...
Click to collapse
Looks like it doesn't have a product model defined! I ran the command twice:
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.002s
[email protected]:~/Mich/android$
Would you recommend using the Huawei Update Extractor tool to flash the individual partitions manually, with the correct (original) image? My device is a CLT-L09C782. And was on b110. I have the update here, and I can extract the various images. But I have never done this kind of low level flashing. If you reckon it'll fix it, would you be happy to give me some quick tips?
This is the process I have found on the subject, but I am not sure whether it is correct or still up to date: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
Thanks!!!
mictho100 said:
Looks like it doesn't have a product model defined! I ran the command twice:
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot oem get-product-model
...
(bootloader)
OKAY [ 0.002s]
finished. total time: 0.002s
[email protected]:~/Mich/android$ fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.002s
[email protected]:~/Mich/android$
Would you recommend using the Huawei Update Extractor tool to flash the individual partitions manually, with the correct (original) image? My device is a CLT-L09C782. And was on b110. I have the update here, and I can extract the various images. But I have never done this kind of low level flashing. If you reckon it'll fix it, would you be happy to give me some quick tips?
This is the process I have found on the subject, but I am not sure whether it is correct or still up to date: https://www.theandroidsoul.com/extract-huawei-firmware-update-app/
Thanks!!!
Click to expand...
Click to collapse
Well it's returning 'hw/eu' so your device is still C432 but looks like oeminfo is damaged, I think.
I wouldn't try the low level flashing business - could result in a brick.
I'm on CLT-L09C432. I'll link you to a TWRP backup of my oeminfo you should be able to restore it from that then hopefully eRecovery will be able to get the right package info for you then.
Flash the unofficial TWRP from here https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
Make sure you follow the step to boot straight to recovery after flashing. Then make a backup of your oeminfo via TWRP, then adb pull the backup to your PC (instructions here: https://www.howtogeek.com/240655/how-to-copy-twrp-android-backups-to-your-pc-for-safe-keeping/ )
Now download these 2 files:
https://drive.google.com/file/d/1hv2HjIEo3bUoveceZWtH8b8uWTB5cuAJ/view?usp=drivesdk
https://drive.google.com/file/d/1EXrnTkbAdI6qaKvo6Du3LwuN6XIuayNb/view?usp=drivesdk
and replace the backup files on your PC with the downloaded ones.
Using the file manager in TWRP, delete the TWRP folder from internal memory then ADB push the backup folder from your PC back to the phone. (Instructions on howtogeek post earlier)
Use TWRP to restore the backup then reboot to fastboot and try
fastboot oem get-product-model
If it returns CLT-L09 them you're good to try eRecovery again.
Hope this helps!
Afternoon Sir!
Tried to follow the above instructions but hit a snag; I cannot boot into TWRP when the cable is plugged into the phone, so I cannot pull the files from it!
If no cable is plugged in, TWRP boots fine and everything works. But as soon as I plug the cable in, the phone reboots automagically and boots into eRecovery. F**DN£(D annoying!
I've flashed TWRP again, just in case it hadn't copied properly, but it made no difference. Had a look on the tintertubes, but couldn't find any references to anybody else experiencing this issue. In fact, my TWRP was working fine with the cable a couple of days ago. I distinctly remember being able to mount the sdcard via USB, to copy files to/from it. No idea how this broke!
So, back to the original idea of flashing the IMG files?
mictho100 said:
Afternoon Sir!
Tried to follow the above instructions but hit a snag; I cannot boot into TWRP when the cable is plugged into the phone, so I cannot pull the files from it!
If no cable is plugged in, TWRP boots fine and everything works. But as soon as I plug the cable in, the phone reboots automagically and boots into eRecovery. F**DN£(D annoying!
I've flashed TWRP again, just in case it hadn't copied properly, but it made no difference. Had a look on the tintertubes, but couldn't find any references to anybody else experiencing this issue. In fact, my TWRP was working fine with the cable a couple of days ago. I distinctly remember being able to mount the sdcard via USB, to copy files to/from it. No idea how this broke!
So, back to the original idea of flashing the IMG files?
Click to expand...
Click to collapse
That's odd. Did TWRP successfully do a backup of your oeminfo? I thought it might fail as your oeminfo seems corrupted.
Have you been able to use ADB before now? It could be a drivers issue...
Try booting to TWRP with cable unplugged, then in your command dialogue type 'adb devices' wait for the daemon to start and then plug in the cable when it says 'waiting for device's or something.
I've never heard of TWRP randomly rebooting when a cable is plugged in.
danifilth4king said:
That's odd. Did TWRP successfully do a backup of your oeminfo? I thought it might fail as your oeminfo seems corrupted.
Click to expand...
Click to collapse
Yup, TWRP has successfully backed up oeminfo. I can see the files in the TWRP file browser.
danifilth4king said:
Have you been able to use ADB before now? It could be a drivers issue...
Click to expand...
Click to collapse
Yeah, ADB works a treat. Not had any problems with it.
Try booting to TWRP with cable unplugged, then in your command dialogue type 'adb devices' wait for the daemon to start and then plug in the cable when it says 'waiting for device's or something.
I've never heard of TWRP randomly rebooting when a cable is plugged in.[/QUOTE]
Tried that, unfortunately it didn't make any difference.
This is such a weird problem. I have TWRP, and I have the oeminfo files. I just can't get stuff on or off the phone! (if it had an SD card, it would be easy, but it doesn't have one!)
Is it possible to pull files via fastboot?
OK, found the problem with the reboot when plugging in the cable! It was a dodgy USB-C cable!! OMG!
I'll run through the process on howtogeek now and will let you know what happens!
So, I'm all up and running again!! !! !!!!!! :laugh:
Replacing the oeminfo files did the trick and the phone then identified itself as CLT-L09 in Fastboot.
I then ran eRecovery and it too was happy to finally download the stock recovery and re-image the phone to CLT-L09 8.1.0.128(C432).
I really cannot thank you enough mate. Honestly. I had been fighting with this phone for over 5 days, and running in circles without getting anywhere., and you pulled me out of the quagmire!
mictho100 said:
OK, found the problem with the reboot when plugging in the cable! It was a dodgy USB-C cable!! OMG!
I'll run through the process on howtogeek now and will let you know what happens!
Click to expand...
Click to collapse
Great news, good luck!
---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------
mictho100 said:
So, I'm all up and running again!! !! !!!!!! :laugh:
Replacing the oeminfo files did the trick and the phone then identified itself as CLT-L09 in Fastboot.
I then ran eRecovery and it too was happy to finally download the stock recovery and re-image the phone to CLT-L09 8.1.0.128(C432).
I really cannot thank you enough mate. Honestly. I had been fighting with this phone for over 5 days, and running in circles without getting anywhere., and you pulled me out of the quagmire!
Click to expand...
Click to collapse
So glad I could help you mate! No worries
I've been in your position with this phone before and know how frustrating it is when you can't figure out how to fix something. Cheers for the gift
---------- Post added at 08:29 PM ---------- Previous post was at 08:24 PM ----------
If you wanna root, I recommend Magisk 16.4 and latest magisk manager. I've had issues with later magisk versions.
I guess your phone got factory reset after the recovery? Bit of a bummer if so.
You can update with HuRUpdater now to build 152 if you're feeling brave. You're on C432 now too, so no more slow updates ?
Just don't forget to uninstall Magisk with the Uninstall feature in Magisk Manager before using HuRUpdater or you'll bootloop again ?
Hello all, I have a big problem - I tried to use last TWRP from L00 Kostyan LOS13 version. I bricked my phone :-(. I had Kostyan last LOS13. by mistake I installed recovery.img to oem info partition. When I start the mobile LEDs first blink is red then green. There is no logo. I can only go to FASTBOOT&RESCUE MODE. It say phone locked. I can connect to phone via fastboot, adb says there is no device. I found out via fastboot that bootloader is locked. I am not able to load anything - its say command not allowed probably due to locked bootloader. Coudl you help me please? I also tried to save an official Huawei ROM to SD card to dload folder, but nothing happens during starting phone (I tried all combinations - power button + only vol-, only vol+, both volume). I can go only to FASTBOOT&RESCUE MODE :-(
You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
masemoel said:
You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
Click to expand...
Click to collapse
Thank you very much for you quick response. I extracted the official P7-L10V100R001C00B609Esp ROM (I can try another but I do not think it matters). I do not see there anything similar to oem partition. I tried to flash recovery and boot section. But I always got "FAILED (remote: Command not allowed)". I tried also the TWRP with the same result.
I tried fastboot oem unlock but I got "FAILED (remote: data parse fail)" it probably requires a code.
I think I have to unlock bootloader but how to do it if my phone does not work?
Hi,
today I tried to flash TWRP on my XZ1 Compact to later install LineageOS on it, as the provider-supplied Android version is stuck at version 9.
I managed to unlock the bootloader and I followed this guide on TWRP.me to install TWRP.
All steps were successful, except the actual flashing of the recovery.
Meaning, that I could successfully list my device with `adb devices`, successfully boot into the bootloader with `adb reboot bootloader` (blue LED indicator, black screen), as well as successfully list the device with `fastboot devices` afterwards.
The final step though fails as follows:
Code:
sudo ./fastboot flash recovery twrp-3.6.1_9-0-lilac.img
Sending 'recovery' (33816 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
After the above command failed, the phone seems to end the bootloader mode and returns to just charging via USB.
I tried this several times, but nothing changed.
I'd appreciate any help to get TWRP installed to be hopefully able to install LineageOS.
If there's any further information/details missing, please let me know.
EDIT:
I tried the above steps with ADB/Fastboot versions 33.0.1-8253317 and 33.0.2-855794 on a Linux machine with the same outcome.
Thanks a lot in advance!
SOLVED: For some reason switching to another laptop (with the exact same adb/fastboot files and TWRP) solved the problem.
Had the same f--ing thing. Google brought me to this post where a user solved it by trying out different laptops and USB ports. Thought it was nonsense, but tried it out on another laptop and it worked. BTW, adb's fastboot never worked on Windows for me due to some driver issue which apparently only concerns Xperias and I tried two different Linux distros before finally having success booting up EndeavourOS from a USB.
I have a Redmi 7 and for some reason this is the top result for my search of this exact problem for the redmi, so I'm going to post this here in hops it can help keep someone from banging their head against the wall like I have. And hopefully this method helps us out with Sony as well.
I tried 4 different PCs and I couldn't get mine to work.
However I did get it to work by manually rebooting into recovery after flashing twrp by holding the power + volume up buttons right at the fastboot screen and releasing the buttons after seeing the Redmi name.
To clarify:
Run fastboot flash recovery twrpname.img
Do not run "fastboot boot twrpname.img"
From the fastboot screen on your phone hold the power & volume up buttons until you see the Redmi name display
You will be in TWRP