So I was on honor 9 stf-l09c432b182 with openkirins twrp and had sideloaded Supersu and everything was working fine.
My plan was to uninstall root, flash stock recovery and upgrade to B183.
So I uninstalled supersu, flashed the recovery.img and recovery2.img in fastboot.
Then I tried to install B183 with the system updater of emui. Failed in the middle of the process.
So then I tried to manually flash system.img, cust.img, recovery.img, recovery2.img, boot.img(basically everything that doesn't give the error: remote command not allowed)
from B183 and when I rebooted i had a really weird version number( similar to this: https://forum.xda-developers.com/honor-9/help/strange-version-t3699280).
Now heres the part where I probably bricked some stuff: I was really concerned and tried to flash my old B180 firmware and then my device is stuck at the screen: Your device can't be trusted...
(http://s1.postimg.org/yilteiv0f/bab3a651_1dcc_4073_88ec_8172118b7227.jpg)
Your device is booting now.
I tried to relock and unlock the bootloader, but does not work.
Tried: fastboot oem lock, fastboot oem relock, fastboot flashing lock
Now current status:
I can boot into bootloader via volume down+ plug in.
Oem and frp are unlocked.
I can hold down volume up and go into erecovery but trying to install something from there didn't work.
I can charge my phone.
Something similar happened to this guy here: https://forum.xda-developers.com/honor-8/help/stuck-device-booting-t3650016 but he was lucky to find someone who repaired it for him.
I would thank you all soo much if you could help me, or just give me a tip what I can do.
Thanks for all replies
You should try to full restore to service repair stock working firmware with sdcard :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Alternatively, you could try to downgrade to stock firmware without rebrandind (no sdcard needed) :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
k1ks said:
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
Click to expand...
Click to collapse
Which version should I use for rebrand ? B120 ?
If yes, I cant find any download links for B120 zips.
Thanks for your reply.
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
k1ks said:
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
Click to expand...
Click to collapse
Ok thank you so much my phone is now working again on B120, what a trip!
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
Youre welcome , , a little spicy huawei.
I had the same mishap.
I think we have to wait for a possible fix of the twrp , nothing is stable at the moment.
Too much random behavior.
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Freakeee93 said:
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Click to expand...
Click to collapse
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
oslo83 said:
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
Click to expand...
Click to collapse
But that HWOTA.zip is not available anymore. So I did't knew what to do.
Edit: Found it... It's edited from the mod. Am trying if the download is ready.
It works again!!!! Great and thank you for your help!:good::good::good:
Related
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Demian3112 said:
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Click to expand...
Click to collapse
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
jimandroidnerd said:
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
Click to expand...
Click to collapse
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Demian3112 said:
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Click to expand...
Click to collapse
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
jimandroidnerd said:
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
Click to expand...
Click to collapse
My device got bricked B330. So i had to reflash some stuff and ended up with false info under the section About Phone i had the same issue as him So i followed that instructions but i couldnt flash the Cust.img in the recovery (twrp) it gives me the error that i have as title. Without flashing the cust.img i cant use a revert package through dload since my Phone shows other information then the update package (denies to do the update instant) . My question how can i fix the error "File bigger then target device" so i can flash the Cust.img since fast boot doesnt work (error remote: command not allowed recovery) and twrp is my only option..
Instructions i followed to get back to stock.
Flash Boot.img, system.img, cust.img through twrp > flash stock recovery > Apply UK back to stock through dload
I cant flash cust.img so step 1 fails and i cant do the rest.
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Demian3112 said:
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Click to expand...
Click to collapse
I could give you my twrp backup? Maybe that will help
jimandroidnerd said:
I could give you my twrp backup? Maybe that will help
Click to expand...
Click to collapse
I mean i should be able to flash cust.img through fastboot right?
Demian3112 said:
I mean i should be able to flash cust.img through fastboot right?
Click to expand...
Click to collapse
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Nvm thanx! Fixed it im an idiot.
I was so bussy almost 2 days with this. I have no experience (14old) and i simply went bussy so much with it that i started looking over the simple things. I fixed it now it left me with a damm headache thnx anyways, i learned something again!
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Demian3112 said:
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Click to expand...
Click to collapse
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
This is what i got.. http://prntscr.com/brv0ay the Repository doesnt contain this files aswell any idea? Is it possible to flash for example a full Kiw L22 rom and then use a revert package for L21 through Dload?
Oke what i did:
Wipe
Apply Cust partition with terminal
Apply backup/restore
flash stock recovery
Boots same issue, I just need the dload to get to work so i can flash the recovery pack. But it stays at 0 percent even after 15 mins.
What i found out is that i dont have the stock firmware (Dont have fingerprint and stuff, device doenst show as KIW L21), so i doenst do a ota update and local update ofcourse. I need a TWRP backup with firmware included. What im trying now is installing L21 MIDDLE-EAST firmware and then try to use a revert package for L21 through OTA.
Arobase40 said:
Well, I'm not sure this is a good idea as it took me 11 days to upgrade from B140 (Lollipop) to B330 (Marshmallow) and only a few minutes to brick my Honor 5x L21 using a backup from kiwi_twrp_5-14_recovery.img when I wanted to revert back to B140... ^^
At boot time after the restore, I have an animated red H letter from the Honor Logo and impossible to get back to the welcome screen nor to any other screen so I don't have access to TWRP anymore...
We really need to have access to the official downgrade firmware from Honor !!!
Click to expand...
Click to collapse
Same issue.. I get red H honor logo.. cant apply a single update through ota/dload and finger print is gone.. I can do everything, installing apps and stuff but i cant revert back to full stock.
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
Could you link me the firmware.vfat and misc.emmc and persist.ext. Is there a way to make the update.app a flashable zip? Anyways any idea what i still could do?
Anyways what would you recommend me to go back to stock right now? Is it cuz my system partition is messed up? How to fix? thx anyways!
Arobase40 said:
As I said it is NOT really a good idea to use a TWRP backup to revert back from Marshmallow to Lollipop as it will brick your device !
I also said : ask your local Honor technical support for an official revert back firmware as your whole system is obviously messed up.
I don't know how you upgraded your smartphone but better downgrade to Lollipop first and try to upgrade again to MM a "proper way"...
Click to expand...
Click to collapse
]
Thats the point.. I simply cant. Phone doenst accept dload updates instant says "System Failed", most near honor technical support is 98 km out.
Ok anyways does anyone have a B330 full stock backup?
Arobase40 said:
I didn't say you had to move yourself to a technical support but place a phone call or mail them. You should find their phone number or their email address from your the Honor Website.
I'll do it myself by tomorrow...
Click to expand...
Click to collapse
I fixed it. Go to hi honor and search for honor 5x firmware, download it unpack it put the update.app on dload on microsd make sure you flashed stock recovery through fastboot hold power + volume down + volume up until it vibrates and done. I couldnt install any dload file on XDA the error "system failed" means the update is not for your device. The one on hihonor was the only one that worked for me ive been bussy 3 days its worth trying. I can link/upload you the download and instructions if you want to but ill do it tomorrow.
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Hello i have the same problem could you please give me your backup so i can try it?
Same issue
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Hi, i have new honor 9, as i open the phone , it is upgrade to B183 Version.
i need to automatic call recorder and i have found a zip.file to flash whit twrp. So i want install twrp and root...
The first time i download TWRP 3.1.1-1 and Supersu 2,82, i install all whit my zip file per automatic call recorder...
all is ok, twrp, i have root and call recorder working,,, but...
I lose navigation buttons and Camera Flash.
for navigation buttons isnt a problem... i can use only Home button ( i had a Meizu phone before but...
I need camera flash ! it have to work.
so....
for have again all working , i used the Rebrand Guide of HWOTA, whit B120 all work again.
cannot have more OTA upgraded but i think because i just had download them whit my imei.... ok i will wait new update for verifyng it.
I can use Finder Firmware Huawey for have manual upgrade.
Now i'm again in b183.
how can I do now for have a valid twrp or valid method for root phone? Because i read that same people have them..... but i think have reroll to b120 almost 50 time whithout always same results....
oh oh, i see now that i have wrong section. moderator can you move?
SOLVED!
After many time i can have all working now:
Starting to B183 firmware whit button and flash not working:
Step 1) Rollback on B120, downgrading by flashing with hwota scripts, this post . option are 2 (directory upgrade) and 1 (same brand). with this you will have working buttons
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Step 3) Unlock the bootloader.
Step 4) Install the TWRP-3.1.1.1_120_130_170.img from this thread.
Step 5) Install Supersu SR5
WARNING: you have to be carefull when go in TWRP recovery: do not modify system data at twrp's boot, then rebooted choosing not to install twrp at twrp's exit prompt. ( dont'know if it is important... but so it work
so you will have a b183 firmware whit all working: root, button and flash.
please, reply if this work for you.
Add more infos about FF .
In updater system , no update available after roolback to B120.
Need to use Firmware Finder Huawei on Playstore.
1-Choose the desired full version
2-Check Firmware access for be sure not make mistakes.
3-Get an update throught DNs , register update and change Dns .
4- Come back to updater and check update .
angelobiz said:
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Click to expand...
Click to collapse
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Zuzler said:
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Click to expand...
Click to collapse
While on stock B120 use the android application Huawei Firmware Finder to upgrade:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/
But you could try to test to use HWOTA to upgrade from b120 to b183 and then report here?
I already tried upgrading to B182/183 with HWOTA. I was on B120 and did a B182 and B183 upgrade. I was left with no capacitive keys and no flash. Camera was working however.
Just right now downloading B183 on top of a new locked B120 with the Firmware Finder, will report back.
However, it's very inconvenient to update the system this way if you have an unlocked bootloader and are rooted. I mean, downgrade to B120, twice within HWOTA, upgrade within the system and then AGAIN re-unlock the bootloader which results in a factory reset - come on...
Does it also work with Magisk or only with SuperSu?
SuperSu already is nice, but the additional benefits like would be nice to have, especially passing SafetyNet.
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
zxz0O0 said:
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
Click to expand...
Click to collapse
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Zuzler said:
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Click to expand...
Click to collapse
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Good. This might be a breakthrough. Could you please share a step by step guide what to do? Thanks.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
angelobiz said:
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
Click to expand...
Click to collapse
It would be a good thing.
Edit : As we are all trying to make your device 100% functional with root.
Here is a link for a Su Emui , not testes yet. Work on the mosty Huawei devices
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
http://www.mediafire.com/file/pn2pv1rqih1ug81/SuperSU-v2.82-EMUI5-SELPermissive[1].zip
https://androidfilehost.com/?fid=673956719939815322
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you provide details?
I wonder if we can pull the touch_key firmware from a working B120 firmware and flash over a later version?
angelobiz said:
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Now i'm ok .
I used the good twrp and sideloaded Supersu.sr3 .
All buttons and flashlight work nice
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
So did your twrp fix touch_key once broken?
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you please share your modified TWRP recovery, so we can test on our phones?
This issue is driving me crazy.
Thanks :good:
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
cvpcvp said:
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
Click to expand...
Click to collapse
Hi, look here
If you are running EMUI 9.1, flash C432 oeminfo and use variant with HuRupdater https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538623
https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538725
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
cvpcvp said:
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
Click to expand...
Click to collapse
Can you write down exactly what you did?
What is your version of EMUI?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
I guess I've stupidly used the wrong command line a number of times to get twrp to run.
fastboot flash system, boot or recovery twrp....
At least it worked with the country ID change ... if only a small consolation for the first
fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.112(C432)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)
cvpcvp said:
ANE-LX1 8.0.0.112(C432)
Click to expand...
Click to collapse
your firmware is incomplete, it must be 8.0.0.143, if I'm not mistaken. Try again Huru method & factory reset in Stock recovery (not in TWRP!).
Or, download Service ROM Link , unpack , there's dload folder in "Software" . Copy dload folder (without unpacking it) to the OTG flash, turn off the phone and press and hold both volume buttons + Power ( this method will lock the BL again).
Thanks for the files. But i get an
Softwaere install failed
Incompatibility with current version.
Please download the correct update package.
EDIT: cant find the firmware version: ANE-L01C185B112 / ANE-LX1 8.0.0.112(C432)
EDIT2: same fail with 8.0.0.178(C432)
cvpcvp said:
Softwaere install failed
Incompatibility with current version
Click to expand...
Click to collapse
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
cvpcvp said:
cant find the firmware version: ANE-L01C185B112
Click to expand...
Click to collapse
Flash only C432 regional variant!
-Alf- said:
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
Click to expand...
Click to collapse
Can you explain me, how i can Boot into twrp without Flash twrp in recovery ramdisk?
cvpcvp said:
without Flash twrp in recovery ramdisk?
Click to expand...
Click to collapse
And what stopping you from doing it?
-Alf- said:
And what stopping you from doing it?
Click to expand...
Click to collapse
Okay, idon't think that's relevant anymore anyway
I found the problem. It was the TWRP version. I took the latest one (twrp-3.5.2_9-0-anne.img) and it couldn't mount the /system partition. Now I took a version from this forum (twrp-3.2.1-0.img), which seems to be specially adapted for the Huawei devices. Unfortunately, it doesn't support OTG, but that wasn't a problem because I moved the files it to the internal memory.
Only with this twrp version could HuRUpdater.zip be executed correctly and all other files just like that. Here, too, I was first asked to press the vol-down button.
After the smartphone finally boots properly, I flash the firmware via dload to lock the bootloader again and do over the Recovery Wipe data / factory reset + cach partition.
Now I'm on version 8.0.0.046(0CXB). Unfortunately the device cannot find a new firmware version and nothing can be updated via HiSuit.
Can you tell me which step I have to take now to get the latest Android version for the device?
Thank you very much so far for your help
cvpcvp said:
Now I'm on version 8.0.0.046(0CXB)
Click to expand...
Click to collapse
Unfortunately, you have incomplete FW there again, I think you're doing something wrong. And until the correct FW is there, you won't be able to receive OTA update or update via dload.
If you have followed instructions to the letter , it must work.
Use this TWRP . ( I don't know why you used TWRP 3.5.2.9, in the guide there is a link to 3.2.1-pretoriano80.). 3.5.2.9 isn't fully compatible with our device.
Try this way out:
- Flash TWRP
- Wipe - format data
- Reboot back to TWRP
- Wipe - Advanced wipe - wipe Dalvik/ART, cache, data, system
- Go back and flash HuRu
Note: the installation of the first file (write radio image...) must take longer, 2-3 minutes, this is proof that the installation is proceeding properly.
Btw, have you tried update via eRecovery & Wi-Fi?
Did it exactly like that. And then the 9.1.0.370 (C432) from the same thread loaded (dload / ANE-L01_hw_eu).
Now i have the firmware: ANE-LGRP2-OVS 9.1.0.370 in the device information.
Unfortunately, there is no further update, but I also don't know whether the current one is already the most recent?
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Can I fix that too? Then everything should be fine as far as possible
cvpcvp said:
ANE-LGRP2-OVS
Click to expand...
Click to collapse
Wrong again .
cvpcvp said:
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Click to expand...
Click to collapse
Oh, it's all clear now
Because this oeminfo is for dual SIM. Oeminfo for single SIM can be found for example here:
https://forum.xda-developers.com/t/c432-single-sim-oeminfo.3873312/
Also update_all_hw.zip file is for ANE-L21, you need ANE-L01, unfortunately, I don't have files for single SIM.
cvpcvp said:
Can I fix that too?
Click to expand...
Click to collapse
Maybe...You have to downgrade to Oreo via HuRupdater using downloaded files, then install TWRP over eRecovery and install stock Recovery.
Download https://androidhost.ru/2zMw and create dload folder .
In TWRP install new oeminfo.img , then go back to the main TWRP's menu, select Reboot > Power off. Use three buttons kombo to flash service ROM.
To be honest, I've never tried a variation like this, so I'm not responsible for this procedure, but it should work. The question is, is it worth it ...
-Alf- said:
Wrong again .
Click to expand...
Click to collapse
Which step is missing now exactly? I followed the steps from you. I also used the files from the other thread that you linked. The single-sim / dual-sim problem is not important either. The main thing is that it works that way too
cvpcvp said:
The single-sim / dual-sim problem is not important either.
Click to expand...
Click to collapse
Are you sure? In my opinion, this is your main problem...
Hello, it's been a while. I sat down again and went through everything. The dual SIM files fold onto a single SIM smartphone. I was finally able to install the update via eRecovery after flashing via TWRP. Then two updates were pulled or installed via Android OS. Now I'm on 9.1.0.132 (C432E5R1P7).