So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Related
I bricked my huawei mate 10. Please help. TIA
me 2
You have to give more information if you want us to provide a viable (if there are any) solution. What firmware were you on, what firmware were you trying to install?
i was trying to install xposed
bootloop
me too please help
I'd really appreciate your help
I have a Huawei Mate 10 on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
System 8.0.0.38(0310)
Product model:
ALP-L29
I tried installing Xposed Framework ... after installation got in a bootloop
eRecovery doesn't work
I don't have TWRP
can only enter fastboot
the device has an SD card slot but I'm confused because some say upgrading or formatting it works and some say it doesn't .
I just want the device to boot ... I don't care about the data
please kindly help
thanks in advance
hero3210 said:
me too please help
I'd really appreciate your help
I have a Huawei Mate 10 on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
System 8.0.0.38(0310)
Product model:
ALP-L29
I tried installing Xposed Framework ... after installation got in a bootloop
eRecovery doesn't work
I don't have TWRP
can only enter fastboot
the device has an SD card slot but I'm confused because some say upgrading or formatting it works and some say it doesn't .
I just want the device to boot ... I don't care about the data
please kindly help
thanks in advance
Click to expand...
Click to collapse
More info:
fastboot oem get-product-model
...
(bootloader) ALP-L29
fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
fastboot oem get-build-number
...
(bootloader) :System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
please inform me of how to flash update.zip because I get an error
or place in in SD card because UPDATE.APP is more than 4GB ..
I think for the experienced, my problems are fairly easy to fix so please help ... I appreciate any suggestion. Thank you.
royhanks3 said:
You have to give more information if you want us to provide a viable (if there are any) solution. What firmware were you on, what firmware were you trying to install?
Click to expand...
Click to collapse
ALP-L29 bootloader unlocked.
Rooted
I am just struck in bootloop.
Erecovery doest help. I have the firmware(update.app) just tell me how to flash the stock rom i.e (update.app)
Thanks in advance.
Please help
Karthik1898 said:
ALP-L29 bootloader unlocked.
Rooted
I am just struck in bootloop.
Erecovery doest help. I have the firmware(update.app) just tell me how to flash the stock rom i.e (update.app)
Thanks in advance.
Please help
Click to expand...
Click to collapse
You need to unpack the update.app with Huawei Update Extractor and get the system.img.Then flash it with fastboot and check if it boots.
Pretoriano80 said:
You need to unpack the update.app with Huawei Update Extractor and get the system.img.Then flash it with fastboot and check if it boots.
Click to expand...
Click to collapse
How can this be done?
Tumpster said:
How can this be done?
Click to expand...
Click to collapse
I've just told you in my previous post, lol.
Use this guide - > https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733 <- to extract the system.img and then flash the image with this command : fastboot flash system system.img
Then reboot the with "fastboot reboot" command and hope that your system boots.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
As i know you cannot downgrade from pie to oreo try to flash back the pie files as u did before with HWOTA8 and see if the devise boot
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Flash back stock pie kernel. Hwota flashes recovery and kernel (and ramdisk which fails because there is no ramdisk partition in pie). If kernel doesn't work because its corrupt or wrong (pie kernel is 4.9 while Oreo use 4.4) your device can't boot recovery or boot to system.
You can downgrade using TWRP but you'd have to do it manually.
Antidote03 said:
As i know you cannot downgrade from pie to oreo try to flash back the pie files as u did before with HWOTA8 and see if the devise boot
Click to expand...
Click to collapse
Thanks for the suggestion. I tried flashing back the pie files using HWOTA8 but the software requires you to boot to recovery in order for the installation to continue but the device won't boot to recovery, it's just stuck on device is booting now screen.
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
ante0 said:
Flash back stock pie kernel. Hwota flashes recovery and kernel (and ramdisk which fails because there is no ramdisk partition in pie). If kernel doesn't work because its corrupt or wrong (pie kernel is 4.9 while Oreo use 4.4) your device can't boot recovery or boot to system.
You can downgrade using TWRP but you'd have to do it manually.
Click to expand...
Click to collapse
Thanks for the explanation. At least I have an idea now what caused the issue . If it's fine do you have the steps or link which provides steps how to downgrade using TWRP?
Carnage! said:
Thanks for the explanation. At least I have an idea now what caused the issue . If it's fine do you have the steps or link which provides steps how to downgrade using TWRP?
Click to expand...
Click to collapse
Look here - > https://forum.xda-developers.com/mate-10/how-to/how-people-bricked-phone-rebranding-ota-t3797555 <- use the Huawei Update Extractor tool to get the image files than flash with fastboot.
kernel = fastboot flash kernel kernel.img
system = fastboot flash system system.img
recovery = fastboot flash recovery_ramdisk recovery.img
Obviously, replace image name with the ones you are using.
For downgrading, download this tool - > https://mega.nz/#!oxkQWApD!-PtLtrekX3DS-iglnr7xpdB1285dF1nZSiOSHyZsqKA <- unpack it on your PC, launch Flash.bat and follow the On Screen instructions .
Now you got it why you shouldn't spam threads? You get answers all over the forum, which is not nice.
Pretoriano80 said:
Look here - > https://forum.xda-developers.com/mate-10/how-to/how-people-bricked-phone-rebranding-ota-t3797555 <- use the Huawei Update Extractor tool to get the image files than flash with fastboot.
kernel = fastboot flash kernel kernel.img
system = fastboot flash system system.img
recovery = fastboot flash recovery_ramdisk recovery.img
Obviously, replace image name with the ones you are using.
For downgrading, download this tool - > https://mega.nz/#!oxkQWApD!-PtLtrekX3DS-iglnr7xpdB1285dF1nZSiOSHyZsqKA <- unpack it on your PC, launch Flash.bat and follow the On Screen instructions .
Now you got it why you shouldn't spam threads? You get answers all over the forum, which is not nice.
Click to expand...
Click to collapse
Thanks for the steps. I will try it later and will let you know. I really apologize for spamming since I panicked and I don't know where to get help. I will continue and reply to this thread only moving forward.
Carnage! said:
Thanks for the steps. I will try it later and will let you know. I really apologize for spamming since I panicked and I don't know where to get help. I will continue and reply to this thread only moving forward.
Click to expand...
Click to collapse
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
@Pretoriano80
Thx this has Fixed my Phone
In Huawei Service Center they are not able to fix the Firmwarefail *rofl*
ante0 said:
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
Click to expand...
Click to collapse
I think he already flashed system once! ?
ante0 said:
I would start with just flashing kernel. Flashing system can disable Oem unlock, which will result in frp lock in fastboot.
Click to expand...
Click to collapse
Got it. Thanks again for all the help!
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
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Looneychoons said:
Hi
I recently bought a p20 lite from Facebook and i think the previous owner must have flashed the wrong firmware. In developer options there is no oem unlock button, and i tried eRecovery and it didn't work. The phone is dual sim, some apps see as if the phone is rooted and when i check with root checker, there's no root. I'm from South Africa and i hope i provided the necessary information. I would like to downgrade the phone to the firmware I'll be able to get the bootloader code from.
Click to expand...
Click to collapse
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
-Alf- said:
Hi, just to be sure -
A) enter Project Menu (*#*#2846579#*#*) > 'Network info ... ' > 'Vendor country info'
B) In fastboot mode run command
fastboot oem oemimforead-CUSTOM_VERSION
and post the results.
Edit.: what was the reason for the failure with erecovery?
Click to expand...
Click to collapse
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Looneychoons said:
Thanks for the reply man.
Vendor country is hw/meafnaf. Secondly, I get oeminforead-CUSTOM_VERSION failed. When i did erecovery i got 'Getting package info failed' i did factory reset and tried again but same error.
Click to expand...
Click to collapse
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
-Alf- said:
Okay, try this way out:
1. Download Oreo Service ROM
2. Unpack it and copy dload folder (can be found in 'Software') to the SD Card (without unpacking it!)
3. Turn of your phone and use three button combo (dload method) .
The process will erase all your data!
Click to expand...
Click to collapse
Thank you bro I'll let you know how it goes. After dload do i setup the device or wipe and factory reset, also do i check for updates or just buy credits for dc unlocker to get my bootloader code?
Looneychoons said:
buy credits for dc unlocker to get my bootloader code?
Click to expand...
Click to collapse
First check if ANE-LX2 is supported, I'm not sure...
Looneychoons said:
wipe and factory reset,
Click to expand...
Click to collapse
not necessary now
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Thanks man I'll kepl you posted.
-Alf- said:
First check if ANE-LX2 is supported, I'm not sure...
not necessary now
Click to expand...
Click to collapse
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
Looneychoons said:
Hey bro I can't thank you enough. All went well after dload, I got my oem unlock button working, all that's left is to get my bootloader code. After I get it I want to root my phone, so can you please help me with a tutorial, from installing the correct twrp for my device and flashing magisk?
View attachment 5372567View attachment 5372569
Click to expand...
Click to collapse
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
-Alf- said:
For Oreo only!
Download TWRP
Magisk.zip
Magisk manager apk
- download Magisk.zip and copy it to SD
- install Magisk manager apk
- install TWRP in fastboot mode, use command:
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot
- flash magisk.zip in TWRP
- reboot
- open M.manager apk
Update Manager & Magisk , if you want.
Click to expand...
Click to collapse
Really bro thank you. You're the best.
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).
Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot