Related
How to unbrick or get back stock on your Huawei Mate 8. There are many reasons why you would want to do that.
In my case my device (AL10) was stuck at "your device cannot be trusted" after updating from B180 to B321.
First I got to thank acer73 for his software. ajsmsg78 and Kris Chen for their links to the right ROMs.
Also thanks to DarkSilentSC for his help, especially with the L29, great support.
He has a L29, which I don't have, so I'm glad he provides help with that device.
This worked for me on my AL10 to get it back on track, should work on other models too. Just have to find the right ROMSs as according to your model. However, I am not responsible if this does not work for you or if it bricks your phone even more.
And remember: don't forget turning on usb debugging whenever you can!
Unbrick (return to Stock)
1. Find yourself a stock ROM.zip according to your model and extract from the zip the update.app (I used one from a B172 (AL10) Stock ROM, I was running a B180 custom ROM, it worked.)
2. Download the Huawei Update Extractor http://forum.xda-developers.com/showthread.php?t=2433454
3. Extract boot.img, recovery.img, system.img and cust.img with the HuaweiUpateExtractor from the Update.App you find in the ROM to somewhere where you can find them easily
4. Head over to http://forum.xda-developers.com/mate-8/development/rayglobe-italian-knife-t3295526 (You can also do it with fastboot commands, but Acer73's tool makes it easier)
5. get yourself the Italian Knife (btw you probably have to turn off your anti-virus program), extract it in a directory on your PC and start Rayglobe_knife.exe
6. Put the images you have extracted into the folder Unbrick (same directory where you extracted Rayglobe Knife in). The folder was created after you started Rayglobe_Knife.exe
7. Boot your phone into bootloader.
8. In the Rayglobe Knife tool choose Unbrick and choose the option where it says you have placed all the images in the unbrick folder.
9. let the magic work. The phone will restart and it will probably take 15 minutes, make sure its charged enough.
After all that I quickly updated to the latest Stock ROM version, in my case B321, which you need to do if you want to flash later a custom B321. See second post if you want to do that as well or continue with unlocking the bootloader.
Now lets get the bootloader unlocked (for some reason mine was still unlocked)
1. Get Minimal ADB https://www.androidfilehost.com/?fid=24521665358595410
2. Hopefully you still have your unlock code (cause you need it otherwise it won't work)
3. Put your phone in Bootloader Mode (Press & hold power and volume down)
4. Extract Minimal ADB zip and run command.bat
5. Type <fastboot oem unlock xxxxxxxxxxxxx> (where xxxx is your bootloader unlock code)
6. Done
Now lets get twrp set up
1. For that we need minimal ADB again
2. Headover to http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
3. Download TWRP according to your EMUI (For B321 it's EMUI 4.1)
4. Place the image in the directory of the Minimal ADB
5. Rename it to just twrp.img (not necessary but simplifies things)
6. Put your phone in Bootloader Mode (Press & hold power and volume down)
7. Run command.bat
8. Type <fastboot flash recovery twrp.img>
9. Then type fastboot reboot
10. Now you can hold volume up and power until your phone boots into TWRP
11. You need to format data (you'll lose everything on your phone)
12. Done
Remember: don't forget turning on usb debugging whenever you can!
!!!FOR L29 scroll down to DarkSilentSC's instructions!!!
After unbricking I quickly updated my AL10 to the latest version, in this case B321. Should work with all B3xx
1. Head over to Kris Chen's thread (this I used for the AL10)
http://forum.xda-developers.com/mate-8/development/rom-verison-t3324164
Or ajsmsg78's (also AL10 and L09)
http://forum.xda-developers.com/showpost.php?p=66776194&postcount=58 to get the Stock B321
2. Download the ROM and after downloading the zip file, extract update.app from it. Copy the UPDATE.APP to the internal memory of your HM8 in a folder called - dload (you may have to create it). Then press [volume+]+
[volume-]+[power] together to force the update.
3. Voila B321
-----------
!!![For the L29 you should try DarkSilentSC's instructions, which you find below or in post #54 on page 6 http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934/page6 don't forget to hit thanks!!!
1. Start from stock B170 firmware with TWRP ready
2. Extract BOOT, CUST, RECOVERY, SYSTEM from B321 UPDATE.APP
3. Add firmware .zip file (which contains META-INF folder and UPDATE.APP) and place it into internal storage
4. Make sure internal storage data is fully backed up
5. Delete All Accounts in Settings
6. Go to Recovery, Wipe Cache, Delvik Cache, Data, System
7. Flash that .zip file! (Getting errors is okay at this time) [This is what I didn't do before!]
8. Boot straight to bootloader
9. fastboot flash boot, cust, and system
10. let it boot. Let it proceed with encryption process in chinese and fully boot into EMUI
11. NOW I'M AT EMUI 4.1!
12. Reboot to fastboot and fastboot flash insecure_boot and flash TWRP
13. Reboot to recovery (TWRP) and then flash whatever rom you want to place in!
14. Enjoying it!
Great, was looking for details instructions like that, was stuck at cannot be trusted screen
Hello. Also i stuck today when i try to update. I try at my own all what did you said ......everything greast but when i try to flash rom from update.app proccess no pass more than 5:%.
My phone was also al-10 but 2 months ago i debrand with internation rom of acer. Nothing i cant flash . phone reboot work but can flash i thing my problem is the oem info file. Can anyone please help me
ganjbass said:
Hello. Also i stuck today when i try to update. I try at my own all what did you said ......everything greast but when i try to flash rom from update.app proccess no pass more than 5:%.
My phone was also al-10 but 2 months ago i debrand with internation rom of acer. Nothing i cant flash . phone reboot work but can flash i thing my problem is the oem info file. Can anyone please help me
Click to expand...
Click to collapse
Which update.app did you use? Maybe your download is corrupt?
BTW I debranded mine too with Acer's to international.
GerManiac said:
Which update.app did you use? Maybe your download is corrupt?
BTW I debranded mine too with Acer's to international.
Click to expand...
Click to collapse
NXT-AL10C00B321 i extract i unbrick from acer tool and then i use uppdate.app t but no pass more than 5%
What method you used for deprand? mine after debrand no able to use wifi recovery also no let me update even if i install factory recovery.
ganjbass said:
NXT-AL10C00B321 i extract i unbrick from acer tool and then i use uppdate.app t but no pass more than 5%
Click to expand...
Click to collapse
But you first used different ROM images to unbrick and then tried to update to B321.
really sounds as if your file is corrupted. Would try to download it again
GerManiac said:
But you first used different ROM images to unbrick and then tried to update to B321.
really sounds as if your file is corrupted. Would try to download it again
Click to expand...
Click to collapse
ok i will try tommorow......thanks for help by theway the phone booted but if i flash recovery for root no boot.... very strange....sometimes aloud to flash from boot some times no ohhhhhhh(((
Or something no correct with huawei extractor..... Can you provide extracted files?
Thanks in advance.
So I unbricked with B170 and then tried force flashing B321. My first attempt at flashing B321 ended up getting stuck at 5%. Tried flashing again and it said it was incompatible with the current firmware version of my phone. Any ideas on what I should do next?
Edit: Nevermind. I mistakenly copied the UPDATE.APP from B170 to the dload folder instead of the one from B321. lol
Now on B321. Thanks!
AndroidBestieRE said:
Great, was looking for details instructions like that, was stuck at cannot be trusted screen
Click to expand...
Click to collapse
Used this stock ROM for L29 to unbrick, it worked well following OP instructions
update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v46463/f1/full/update.zip
hi, i have follow unbrick guide with knife, flash from knife and phone reboot. when phone reboot in settings, info phones, serial number is b321. is corretcly??
danielg90 said:
hi, i have follow unbrick guide with knife, flash from knife and phone reboot. when phone reboot in settings, info phones, serial number is b321. is corretcly??
Click to expand...
Click to collapse
Don't know which ROM you used to unbrick.
But seems that you used an B321 if that worked for you and you have no problems then that is great.
Could mean that wet can unbrick straight with the most current ROM available. If someone else could confirm?
GerManiac said:
Don't know which ROM you used to unbrick.
But seems that you used an B321 if that worked for you and you have no problems then that is great.
Could mean that wet can unbrick straight with the most current ROM available. If someone else could confirm?
Click to expand...
Click to collapse
i have AL10, please link stock rom that you used
danielg90 said:
i have AL10, please link stock rom that you used
Click to expand...
Click to collapse
Can't find the link right now, am in the car, but I've found this link to B170
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G884/g77/v43738/f1/full/update.zip:
Did not check though if it works
GerManiac said:
Can't find the link right now, am in the car, but I've found this link to B170
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G884/g77/v43738/f1/full/update.zip:
Did not check though if it works
Click to expand...
Click to collapse
sorry, is possible flash with knife if bootloader is locked? my bootloader is locked
hello, my phone is still stuck.. i tried other cust/system/recovery/boot from other update.app, but its still stuck at: your device has been unlocked... im on l29
Have NXT-L29, downloaded stock L09 file from posted link, placed UPDATE.APP into 'dload' folder which I created, but still hanging at 5%. What to do?? Exactly where do I create this 'dload' folder? Just at 'Internal Storage'?
danielg90 said:
sorry, is possible flash with knife if bootloader is locked? my bootloader is locked
Click to expand...
Click to collapse
Bootloader has to be unlocked. You can unlock best with DC unlocker, it's fast and only costs around 5 dollars.
Unless you already have your unlock code then you can unlock following instructions see my first post
GerManiac said:
Bootloader has to be unlocked. You can unlock best with DC unlocker, it's fast and only costs around 5 dollars.
Unless you already have your unlock code then you can unlock following instructions see my first post
Click to expand...
Click to collapse
ok how can i unlocked bootloader with b321 stock?
DarkSilentSC said:
Have NXT-L29, downloaded stock L09 file from posted link, placed UPDATE.APP into 'dload' folder which I created, but still hanging at 5%. What to do?? Exactly where do I create this 'dload' folder? Just at 'Internal Storage'?
Click to expand...
Click to collapse
What are you trying to do? Unbrick or update?
The folder has to be created in internal storage
Any help?
Tried downloading every single ROM I found but none of them allow me to update from my current firmware.
I think I mgiht need to first stablish a european stock android 5 so I can go ahead and use the ROMS that are actually around the web, but cdont know how to do that!
THANKS!!
I have the same problem, althought mine ends in B140. Does anyone know how to update it?
same problem but i have b210.
thanosnic said:
same problem but i have b210.
Click to expand...
Click to collapse
heroe7121 said:
I have the same problem, althought mine ends in B140. Does anyone know how to update it?
Click to expand...
Click to collapse
groggycl said:
Any help?
Tried downloading every single ROM I found but none of them allow me to update from my current firmware.
I think I mgiht need to first stablish a european stock android 5 so I can go ahead and use the ROMS that are actually around the web, but cdont know how to do that!
THANKS!!
Click to expand...
Click to collapse
yes it is possbile... but a long way..
Things you need:
Root
Unlocked bootloader
TWRP recovery
Stock Recovery
First thing first, unlock your bootloader (see chapter 2 of this MEGA thread). Then you need TWRP recovery. Download this : (it contains root file and twrp).
TWRP and ROOT
Now, tap your build number 7-10 times, this will get you Developers Option on Settings. Go to Developers Option and enable it, also you must enable "Enable USB Debugging.. then connect it to your computer. Now extract the downloaded folder, you'll see a folder named data. go inside that and hold Shift and Right Click and Click on Open Commands Windows Here.. run following commands inside quotations:
"adb devices" -> lists your device, if it doesn't then you have some problems while enabling USB debugging... do it again..
"adb reboot bootloader" -> it will reboot the device to white screen with android logo and it must display "Unlocked" on green colours. if it doesn't, it means you havent unlocked your bootloader and you must not proceed any further..
"fastboot flash recovery recovery.img" -> doing this will flash TWRP recovery
"fastboot reboot"->reboots the device..
For rooting, copy 1.zip and 2.zip to your phone/sd card. Then you must go to recovery mode. Connect your mobile to computer via USB cable, and open commands window on data folder (same as you did for TWRP).
"adb reboot recovery" -> will go to TWRP recovery. Click on Install and select 1.zip first to flash... after flashing it will reboot your device. Open the SuperSu app once and close and uninstall it. Go to recovery mode again and then flash 2.zip.. it will reboot again.. now, download Es File explorer or other root browsers. go to /data/app and cut eu.chainfire.supersu and paste it in /system/app with the following permissions rwx r-x r-x and reboot. Congrats, you are rooted now.. Off to next steps.
Now, as you're rooted. Download this file ... After downloading this file you need to copy and paste to this path: /dev/block/platform/hi_mci.0/by-name (for this, you need to be rooted).. It will change your region from c185 to c432.. Restart and you must have c432.
Now, unroot your device and flash stock recovery(for the time being). It is necessary to have stock recovery and be unrooted while upgrading android.
Upgrading process
Download this http://huaweidevices.ru/huaweiservic...urope_Dual.rar B132 version, there must be 2 folders "dload"(it should contain UPDATE.APP with file size approx. 1.3 GB) and "custom" (custom folder must also have UPDATE.APP file inside it, but very small in size) , copy the dload folder to internal memory of your phone (the folder must have updata.app inside it) and do local update... after that copy the custom folder to your device and rename it to dload and do local update again.
Note: it is necessary to flash larger UPDATE file and then smaller UPDATE file to remove Balong issues.
Then download this: http://huaweidevices.ru/huaweiservic...170_Europe.zip B170 version and repeat the above process of upgrading.
after this you should be able to see OTA update of B550/B560 marshmallow update... if it doesn't show yet, then download it from here: http://download-c.huawei.com/downloa...20&siteCode=es B550 version.
A while ago I installed TWRP and rooted my WAS-LX1A and everything worked perfectly fine except that I couldn't install updates. Today I tried to install install a more recent rom and, as expected, it failed. So i tried to install it manually, unpacking boot.img, system.img and recovery.img from the update.app file and flashing them using
Code:
fastboot flash *type* *file*.img
I was able to flash boot and recoverybut when I tried to do the same on system it got stuck and I was forced to interrupt the process. Now my device is constantly stuck on
Code:
Your device is booting now...
and I can't access recovery nor fastboot and adb isn't working:
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I tried using the dload folder method in a FAT32 formatted sd card and every sort of button combination but i'm still stuck at the same point. Anyone can help me?
luis ota doesnt works due to root a custom recovery, i recommend you access to twrp, next:
1- Make a backup only of oeminfo(coy to safe place), download oeminfo ss or ds depending your device, extract and copy/replace oem to the original oem
2- Downloaded servicerom b182 or b183, extract and copy all file and folder(was-lx1a folders and update.app), to dload folder on your sdcard.
3- Now press restore oem and shutdown when it finished, now do 3btns method.
Alternatevility could uninstall adb and reinstall, check if device manager has traces of device or adb and remove too
foliaje said:
luis ota doesnt works due to root a custom recovery, i recommend you access to twrp, next:
1- Make a backup only of oeminfo(coy to safe place), download oeminfo ss or ds depending your device, extract and copy/replace oem to the original oem
2- Downloaded servicerom b182 or b183, extract and copy all file and folder(was-lx1a folders and update.app), to dload folder on your sdcard.
3- Now press restore oem and shutdown when it finished, now do 3btns method.
Alternatevility could uninstall adb and reinstall, check if device manager has traces of device or adb and remove too
Click to expand...
Click to collapse
Didn't work and now the phone is locked and I've lost my unlock code. TWRP also isn't working, as holding pwr+volumeup starts erecovery while the booting screen changed from "Your device has been unlocked" to "Your device has failed verification". Any tips?
mister if you frp(oem is unlocked(red color)) you can solve with dload method and servicerom b182 or b183, other method is dcphoenix(paid)
LuisTheLollichop said:
Didn't work and now the phone is locked and I've lost my unlock code. TWRP also isn't working, as holding pwr+volumeup starts erecovery while the booting screen changed from "Your device has been unlocked" to "Your device has failed verification". Any tips?
Click to expand...
Click to collapse
So, with the service rom on sdcard in folder dload. Booting phone with volumeUp+volumeDown+power also does not work ?
[email protected]@[email protected] said:
So, with the service rom on sdcard in folder dload. Booting phone with volumeUp+volumeDown+power also does not work ?
Click to expand...
Click to collapse
It stops at 5% saying "Software install failed!" only giving me the option to reboot
And after changing the oeminfo my phone appears to be locked as i said in my previous reply
LuisTheLollichop said:
It stops at 5% saying "Software install failed!" only giving me the option to reboot
And after changing the oeminfo my phone appears to be locked as i said in my previous reply
Click to expand...
Click to collapse
oeminfo: backup insdcad(copy to safe place), with the downloaded oeminfo just copy/replace and then restore.
srom: create one folder called dload in sdcard, then extracted the service copy all was folders + update.app(they are inside of dload folder) to the dload sdcard
alternatively you try with dcphoenix and/or dcunlocker(paid both)
LuisTheLollichop said:
It stops at 5% saying "Software install failed!" only giving me the option to reboot
Click to expand...
Click to collapse
Just to be clear, so i understand the situation :
You use the b182 / b183 service rom from here : https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ?
If yes and it don't work, then i guess your f**ked. Sorry
[email protected]@[email protected] said:
Just to be clear, so i understand the situation :
You use the b182 / b183 service rom from here : https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ?
If yes and it don't work, then i guess your f**ked. Sorry
Click to expand...
Click to collapse
You can send him to the service center, they make it free for you with boardswap.
I have had a boardswap twice. Now I know what the problem is and have made a decrypt boot img
Download boot image from this link
https://drive.google.com/open?id=0B1Z5zkx7AGWGbHF6NXo0OFJTRWc
Now flash this boot image in fastboot mode (fastboot flash boot custom_boot_decryptdata_b130.img)
Now hold volume up and type fastboot reboot press enter.
Keep holding volume up until phone reboot to erecovery
Disconnect from PC, Shutdown phone
Hold volume up and power to enter TWRP
Wipe>format data
Go back Reboot>Recovery
Download Full Data zip http://update.hicloud.com:8180/TDS/...WAS-L01A_hw_eu/update_full_WAS-L01A_hw_eu.zip
,and Public Full data zip http://update.hicloud.com:8180/TDS/...86/f2/full/public/update_data_full_public.zip
Copy both zip files to sd card and install one by one in TWRP
reboot>bootloader
Extract boot, system, recovery, from update.zip it using Huawei firmware extractor
Extract cust.img from update_full_WAS-L01A_hw_eu.zip
Flash these images in fastboot mode.
Then reboot to recovery and factory reset, the phone boots normally
Otherwise extarct update.app from update.zip
make a dload folder and copy to sdcard.
Then switch off phone, hold all buttons together to start update.
Fixing Bricked P10 Lite without TWRP , This works even if your Boot is locked
Don't worry my friend be chill, I too bricked my huawei P10 Lite Middle East Version and after a month of struggle I was finally able to fix this issue and restored my STOCK .
This video is made to help you successfully fix your Bricked Huawei P10 Lite
Follow the below youtube video link clearly to unbrick your Huawei
If the above video doesn't play then click on thsi link below
https://youtu.be/0vDgDXePAR4
Cheers.....
I've managed to make it work somehow by bruteforcing the unlock code ahahah Still, thanks everyone <3
Fixed! Go here for steps
I've tried the relock.bat provided in the unofficial bootloader unlock/lock thread but I keep getting the bootloader unlocked warning. I also downloaded and tried installing the stock ROM mentioned in https://m.youtube.com/watch?v=peSI-KeEt5E&time_continue=23 but the window just closed itself so I manually flashed recovery, boot, system and vendor images using twrp. I then booted and installed the April security patch update but I got random soft-reboots in the process.
Can anyone guide me to restoring the device to locked condition? (4GB ram variant)
Update: Noticed that these reboots occur as soon as app installation is over. Disabled app updates for now
Relock Bootloader ZenFone Max Pro M1
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume Down key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
myapky said:
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
Click to expand...
Click to collapse
No success. I'm following the method shown in this thread
Edit: Reboots are fixed after I wiped data before flashing the images
myapky said:
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume Down key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
Click to expand...
Click to collapse
IF YOU ARE ON THE LATEST FIRMWARE THEN THE ABOVE STEPS WORK, I CANNOT POST LINKS HERE AS I'M NOT ABLE TO.
MY PHONE FIRMWARE : Version WW-14.2016.1804.305
CONFIRM YOURS............!!!!
myapky said:
WW-14.2016.1804.305
Click to expand...
Click to collapse
OPM1.WW_Phone-14.2016.1804.305-20180521
Check this [GUIDE][Back-To-Stock] Flash Stock ROM
CHECK THIS : https://forum.xda-developers.com/showpost.php?p=76695194&postcount=95
Download stock recovery availbale at xda forum.
Than download the official latest firmware 1.4GB from asus website and place in external sdcard.
Flash stock recovery with fastboot method. Boot into recovery and flash the firmware zip..it will automatically encrypt your internal data.
SINGHYAR.
myapky said:
CHECK THIS : https://forum.xda-developers.com/showpost.php?p=76695194&postcount=95
Click to expand...
Click to collapse
This got my device into Red State with message "Your data is corrupt". Unlocked bootloader again, will try this method by installing system, boot, recovery and vendor partition images
That script is working for me, but I installed the images of the csc zip which was indonesian edition. Trying again with ZB601KL images
Thanks @myapky! Phone is now having a locked bootloader
Can I relock bootloader after installing Magisk?
Sourav-21 said:
Can I relock bootloader after installing Magisk?
Click to expand...
Click to collapse
You should lock bootloader only on stock recovery without root and with no system modification (like uninstall of system apps, property file change).
If you lock the bootloader with custom recovery or modified system then if OTA messes up boot or any other partition .. you have no way to fix it.
Also .. only locking the bootloader will not fix OTA .. as any OTA patching boot.img will mess your Magisk anyway .. so keep bootloader unlocked if you have modifications.
.A.V.i.n.a.S.h. said:
You should lock bootloader only on stock recovery without root and with no system modification (like uninstall of system apps, property file change).
If you lock the bootloader with custom recovery or modified system then if OTA messes up boot or any other partition .. you have no way to fix it.
Also .. only locking the bootloader will not fix OTA .. as any OTA patching boot.img will mess your Magisk anyway .. so keep bootloader unlocked if you have modifications.
Click to expand...
Click to collapse
Thank you. I forgot that Magisk patch the system.img. In old days superSU just modify the system partition.
I want to relock the bootloader only for the irritating Warning message at the startup. Is there any way to stop that message like moto G?
Sourav-21 said:
Thank you. I forgot that Magisk patch the system.img. In old days superSU just modify the system partition.
I want to relock the bootloader only for the irritating Warning message at the startup. Is there any way to stop that message like moto G?
Click to expand...
Click to collapse
It appears on custom ROM as well .. so not sure about any way to block it.
If i unlock via official app and when some update available and I download & flash by stock recovery will it work?
Another question is if I install custom rom then how can I back in stock rom?
Ariful Hasan Soikot said:
If i unlock via official app and when some update available and I download & flash by stock recovery will it work?
Another question is if I install custom rom then how can I back in stock rom?
Click to expand...
Click to collapse
Recommended to UNLOCK unofficially - using this Guide.
If you have unlocked officially then you will not get OTA update notification.
To update (if you are on stock system without modifications like TWRP, Root etc..),
Download full firmware from ASUS official site ( ZBL601KL OR ZBL602KL ) and try to unzip it once to check for file errors.
If no issues in unzip then keep the file in base path of Internal storage.
You will get a message like System Update file detected (if not then reboot and check).
Select the notification and authorize to update. DONE.
To revert back to Stock from Custom roms - use this GUIDE or follow the method in this thread
.A.V.i.n.a.S.h. said:
Recommended to UNLOCK unofficially - using this Guide.
If you have unlocked officially then you will not get OTA update notification.
To update (if you are on stock system without modifications like TWRP, Root etc..),
Download full firmware from ASUS official site ( ZBL601KL OR ZBL602KL ) and try to unzip it once to check for file errors.
If no issues in unzip then keep the file in base path of Internal storage.
You will get a message like System Update file detected (if not then reboot and check).
Select the notification and authorize to update. DONE.
To revert back to Stock from Custom roms - use this GUIDE or follow the method in this thread
Click to expand...
Click to collapse
I don't understand about base path of internal storage. Plz can you show a screenshot or make clear about which folder i have to put full firmware?
Ariful Hasan Soikot said:
I don't understand about base path of internal storage. Plz can you show a screenshot or make clear about which folder i have to put full firmware?
Click to expand...
Click to collapse
Just keep the file in Internal storage and not under any folder/directory in Internal Storage.
In Internal Storage you should have ..
Android (directory)
DCIM (directory)
Download (directory)
WhatsApp (directory)
..... etc
UL-ASUS_X00T-WW-14.2016.1804.252-user.zip (file)
Remember that the current UL-ASUS_X00T-WW-14.2016.1804.305-user.zip file on https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_BIOS/ is corrupted.
You can download UL-ASUS_X00T-WW-14.2016.1804.252-user.zip from here - https://androidfilehost.com/?fid=674106145207491520
Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?
İ don't now
İ need answer to to trying this method
But my phone C185
And the update file in Firmware finder 2 file not 3
use Hrupdater
CouCouFR34 said:
Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?
Click to expand...
Click to collapse
You would have to modify hwota script as Pie only uses 2 zips.
aureliomilitao said:
use Hrupdater
Click to expand...
Click to collapse
that's not recommended as Pie uses System as root.
ante0 said:
You would have to modify hwota script as Pie only uses 2 zips.
that's not recommended as Pie uses System as root.
Click to expand...
Click to collapse
how modify hwota script as Pie only uses 2 zips?>
same steps with 2 file works??
please my account HCU is block
need help for fix my IMEI with acount HCU via TeamViewer
Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?
CouCouFR34 said:
Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?
Click to expand...
Click to collapse
Remove the following line from update-binary in hwota8_update.zip and repack.
echo --update_package=/sdcard/HWOTA8/update_data_public.zip >> /cache/recovery/command
Or check out this post: https://forum.xda-developers.com/showpost.php?p=78962795&postcount=171
I want to patch new updates of emui 9 with latest google security patches so which no check recovery i use on emui 9.
OK it works very well and EMUI9 is definitely better than version 8; on the other hand how to reinstall TWRP?
I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?
CouCouFR34 said:
I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?
Click to expand...
Click to collapse
You don't need TWRP to install Magisk; for that matter, they can't be installed simultaneously on EMUI 9 together anyway.
The EMUI 9 method for Magisk is to patch recovery_ramdisk.img extracted from update.app, flash the patched image, and boot to recovery from then on. (Huawei made it impossible to load a custom ramdisk on Pie otherwise.)
Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?
CouCouFR34 said:
Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?
Click to expand...
Click to collapse
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Thank you irony_delerium ; very clear tutorial ; on the other hand, in UPDATE.APP there are 2 RECOVERY files : RECOVERY_RAMDIS.img and ERECOVERY_RAMDI.img which do the same weight; patching MAGISK with RECOVERY_RAMDIS.img I arrived at a system error and a dialogue asking me to either erase the data, or a factory restore; on the other hand with ERECOVERY_RAMDI.img it was installed alone? does it seem normal to you?
irony_delerium said:
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Click to expand...
Click to collapse
Hello
If you wouldn't mind confirming a few things from your post, as I'm trying to do this.
Is the sole purpose of extracting the big file to extract the recovery_ramdis ? You don't mention if anything is done with the big file.
The ADB commands didn't work for me, (error: push requires an argument).
But, I sent the recovery_ramdis via magisk manager, and it worked, then advised me that it put the image in /storage/emulated/0/Download/patched_boot.img but I can't find that location.
OK, edit ... I found the file and flashed it, rebooted into recovery and I get the message software installation failed.
I've had a whole lot of failures, phone won't root despite magisk giving no errors, dload won't work, superSU won't work.
Update .... root decided to work out the blue so I tried EMUI flasher and it looked like it was going to work ... but failed the update at about 10%.
Update - Bricked.