EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
Do you mean you can install these over erecovery partition?
adamfirari said:
Do you mean you can install these over erecovery partition?
Click to expand...
Click to collapse
These TWRPs allow you to install any compatible TWRP over eRecovery.
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
TureX said:
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
Click to expand...
Click to collapse
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Fjord1 said:
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Click to expand...
Click to collapse
3.2.1-0 by pretoriano80 .
Note: If you don't have the required files stored somewhere, then it's just an academic question - Firmware finder is ďead.
-Alf- said:
Firmware finder is ďead.
Click to expand...
Click to collapse
It makes me sad...
And what about dload method?
Fjord1 said:
downgrade to Oreo
Click to expand...
Click to collapse
Fjord1 said:
dload method
Click to expand...
Click to collapse
you will get absolutely no success, it may even brick your phone.
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...
Anyone have any clues how I can work around this please. Is patched boot img the only way forward?
OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
-Alf- said:
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
Click to expand...
Click to collapse
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Mahad Habib said:
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Click to expand...
Click to collapse
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
-Alf- said:
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
Click to expand...
Click to collapse
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Mahad Habib said:
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Click to expand...
Click to collapse
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
hopeless_bricker said:
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
Click to expand...
Click to collapse
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
hopeless_bricker said:
Since the recovery partition is occupied by Magisk
Click to expand...
Click to collapse
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Click to expand...
Click to collapse
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.
Handy but I can't boot into the erecovery with the button combo now.
P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?
Related
HwOTA7 + HwOTA8 for Huawei P10 Lite1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
and will be repack firmware (only HwOTA8)!!!
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA_WARSAW.zip
Short video tutorial for upgrade of any version authorized or unauthorized in phone P10 Lite Thanks @Alexxxx1
HwOTA8 method for rollback from EMUI 8 to Emui 5 - Huawei P10 lite Thanks @Alexxxx1
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!
used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD
Locked Bootloader
GizmoTheGreen said:
used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD
Click to expand...
Click to collapse
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
---------- Post added at 10:43 PM ---------- Previous post was at 10:11 PM ----------
vovan1982 said:
HwOTA for Huawei P10 Lite1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
PPS: Sorry for my English!!!
Click to expand...
Click to collapse
Hello!
I need your help with the update.bat file
When I try to execute the file, it just shows a cmd screen for a couple of seconds and nothing happens
what am I possibly doing wrong?
Plus, theres no instrutions for pluggin the phone into the PC, what I being doing its plug in it on bootloader mode
I hope you can understand me, english is not my mother language.
And thank you in advance
EDIT: Forget it man, I make it work, I just copied the HWOTA directory to C: and it works
So far i just used the update firmware option and everything is working
GizmoTheGreen said:
used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD
Click to expand...
Click to collapse
Hi, of couse, on Oreo not TWRP. TWRP from Nougat does not work.
kristoff_andxp said:
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
---------- Post added at 10:43 PM ---------- Previous post was at 10:11 PM ----------
Hello!
I need your help with the update.bat file
When I try to execute the file, it just shows a cmd screen for a couple of seconds and nothing happens
what am I possibly doing wrong?
Plus, theres no instrutions for pluggin the phone into the PC, what I being doing its plug in it on bootloader mode
I hope you can understand me, english is not my mother language.
And thank you in advance
EDIT: Forget it man, I make it work, I just copied the HWOTA directory to C: and it works
So far i just used the update firmware option and everything is working
Click to expand...
Click to collapse
Yes, I can understand you. You did the right thing, way to HwOTA as short as possible.
vovan1982 said:
Hi, of couse, on Oreo not TWRP. TWRP from Nougat does not work.
Click to expand...
Click to collapse
so need to wait for twrp port... ok ^^
kristoff_andxp said:
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
Click to expand...
Click to collapse
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...
GizmoTheGreen said:
so need to wait for twrp port... ok ^^
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...
Click to expand...
Click to collapse
The greater question is: can be the bootloader locked after Oreo update ?
Eurofighter_ty said:
The greater question is: can be the bootloader locked after Oreo update ?
Click to expand...
Click to collapse
Don't know, I'm not going to try
My Bootloader is Unlocked after successful installation.
But why my PC says the prone is PRA-LX1 instead of WAS-LX1?
GizmoTheGreen said:
Don't know, I'm not going to try
Click to expand...
Click to collapse
Did u relocked bootloader?
Alexxxx1 said:
Did u relocked bootloader?
Click to expand...
Click to collapse
no. it did not relock bootloader automatically and I want it unlocked. also afraid of brick if I lock it with this rom.
GizmoTheGreen said:
no. it did not relock bootloader automatically and I want it unlocked. also afraid of brick if I lock it with this rom.
Click to expand...
Click to collapse
Yes, with this method bootloader stay unlock same as on p10 plus, but if you can enter in stock recovery no afraid of any brick if you relock bootloader.
Poslato sa VKY-L29 uz pomoć Tapatoka
for anyone wondering, I solved Magisk installation on oreo!
use .app extractor to get the RAMDISK image, patch it with magisk app on the phone. then use fastboot to install to ramdisk partition, like so
Code:
fastboot flash ramdisk patched_image.img
hope this helps
GizmoTheGreen said:
for anyone wondering, I solved Magisk installation on oreo!
use .app extractor to get the RAMDISK image, patch it with magisk app on the phone. then use fastboot to install to ramdisk partition, like so
Code:
fastboot flash ramdisk patched_image.img
hope this helps
Click to expand...
Click to collapse
Did you try it? Someone said he wasn't able to do it.
Jaizu said:
Did you try it? Someone said he wasn't able to do it.
Click to expand...
Click to collapse
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis
GizmoTheGreen said:
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis
Click to expand...
Click to collapse
So, what's the first impressions of Emui 8?
Sent from my WAS-LX1 using Tapatalk
GizmoTheGreen said:
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis
Click to expand...
Click to collapse
Mind sharing patched .img files? What device model are you using?
GizmoTheGreen said:
so need to wait for twrp port... ok ^^
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...
Click to expand...
Click to collapse
On P10 Lite with Oreo worked TWRP with P Smart Oreo.
vovan1982 said:
On P10 Lite with Oreo worked TWRP with P Smart Oreo.
Click to expand...
Click to collapse
Got a link?
vovan1982 said:
On P10 Lite with Oreo worked TWRP with P Smart Oreo.
Click to expand...
Click to collapse
If you mean that: http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img (TWRP-3.2.1-0 for Huawei P Smart)
I've not test yet if it's fully comatible, but you can enter into TWRP and seems to works.
Reboot into fastboot and enter the command:
fastboot flash recovery_ramdisk FIGO321.img
recovery_ramdisk partition in Android 8 is the Recovery
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
Hi All
Note: This procedure is for Windows PC only.
I can see there is a similar thread to help on rooting your device.
I created this thread it make it more easier and focussed just on rooting your device rather with additional information.
This menthod is to root your device without TWRP.
There is a detailed guide by @Freak07 which you can find here.
Prerequisite:
1. Your device bootloader is unlocked
2. You have enabled your Developer Options and enabled USB debugging (Settings > System > About phone > Software information, tap build number 7 times to enable Developer options)
3. Flash Tools, download from here and extract to your PC
4. Latest Magisk Manager which you can download from the relevant thread (search or click here)
BOOT IMAGES
Stock Boot images:
Firmware WW_16.1220.1906.174_0 >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 >>>> Click here
Patched Boot images:
Firmware WW_16.1220.1906.174_0 (patched with Magisk 19.3 stable version) >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 (patched with Magisk 19.3 stable version) >>>> Click here
Steps to Root:
1. Connect your device with USB cable
2. Go to the folder where you copied Flash Tools and double click to run cmd-here.exe
3. In the command prompt run the command adb devices, this will run the Deamon and show your device under List of devices attached. If doesn't show your device, check your device is connected and USB debugging is enabled.
4. Now run the command adb reboot bootloader to boot your device in to Fastboot mode
5. Now flash the patched boot image with the command fastboot flash boot magisk_patched.img
Restart your device with the fastboot command fastboot reboot and enjoy your ROOTED device
It works great, thanks!!
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
EMJI79 said:
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
Click to expand...
Click to collapse
Hi ASUS firmware for Zenfone do not have system img and instead it is the payload.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
smohanv said:
Hi ASUS firmware for Zenfone do not have system img and instead it is the paylod.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
Click to expand...
Click to collapse
If I just reset system via stock recovery, will I lose user data?
EMJI79 said:
If I just reset system via stock recovery, will I lose user data?
Click to expand...
Click to collapse
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
smohanv said:
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
Click to expand...
Click to collapse
I will do that.
Just another question: can I just boot in Twrp without installing it?
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
You can boot in to TWRP without permanently flashing it.
Take few cautions before you attempt to boot in to TWRP using this option,
1. Remove fingerprint in security settings (settings > Security & lock screen > Fingerprint)
2. Remove screen lock PIN in settings > security & lock screen > screen lock > select NONE here and also make sure Fingerprint is not enabled in this screen
How to boot in to TWRP:
Download TWRP from here
Use the command in Fastboot > fastboot boot twrp-3.3.1-15-ASUS_I01WD.img
Now you can use file manager in TWRP and remove magisk folder. You have to mount system folder to do so.
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
smohanv said:
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
Click to expand...
Click to collapse
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
EMJI79 said:
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
Click to expand...
Click to collapse
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
smohanv said:
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
Click to expand...
Click to collapse
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
EMJI79 said:
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
Click to expand...
Click to collapse
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Which method from the link do you advise to try first?
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
smohanv said:
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
No luck, can't flash anything in TWRP ...
Guess I have to wait TWRP is updated.
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
EMJI79 said:
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
Click to expand...
Click to collapse
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
New Update
smohanv said:
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
Click to expand...
Click to collapse
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Damionix said:
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Click to expand...
Click to collapse
Yes you will loose root. Why do you go for build 171 when 189 is available now.
Official link: >>> https://www.asus.com/us/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
New build can be downloaded from here >>> Download
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka ADB) and USB drivers should be set beforehand. Latest versions are reliable enough. PixelExperience, PixelOS and MIUI (official and Xiaomi.eu) ROMs have been tested. Before proceeding to flash, make sure about your ROM type (standard or vendor_boot) to avoid not desired consequences. Blew are the most recent versions.
_________________________________________________________________________
TWRP (standard)
Android 12:
twrp-3.7.0_12-v7.7_A12-alioth-skkk.img
Android 13:
twrp-3.7.0_12-v7.8_A13-alioth-skkk.img
[Instructions]
1. Reboot to fastboot mode.
2. Execute command below in ADB on PC:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your downloaded recovery file address.
3. Choose "Flash current TWRP" from TWRP's "Advanced" option.
4. Reboot.
_________________________________________________________________________
OrangeFox (standard)
Android 12+:
[email protected]_3_A12.zip
[Instructions]
1. Reboot to TWRP.
2. Choose "ADB Sideload" from TWRP's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
_________________________________________________________________________
OrangeFox (vendor_boot)
Read this thread for a detailed explanation and list of vendor_boot ROMs.
This is beta release. Treat it as such.
Android 13:
[email protected]_1_vendor_boot_vBaR.zip
[Instructions]
1. Reboot to your ROM's recovery.
2. Choose "ADB Sideload" from recovery's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
fastboot flash vendor_boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your extracted recovery image address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Run "flash-whole-image.bat" file.
4. Reboot
_________________________________________________________________________
Ps: though there are some glitches, both recoveries can install Magisk to root the device.
_________________________________________________________________________
Sourceforge archive page
OrangeFox homepage
Platform Tools download page
Google USB Driver download page
Last time I tried installing lineageos using latest twrp it failed miserably
heybaybee said:
Last time I tried installing lineageos using latest twrp it failed miserably
Click to expand...
Click to collapse
Me too, better use its recovery.
New versions available. Links have been updated.
rashazad said:
New versions available. Links have been updated.
Click to expand...
Click to collapse
Thanks for the thread. Does the latest version support flashing MIUI Global ROMs? Im having a hard time flashing them via TWRP SKK 3.7.0_A12_V6.7_A13.
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
panjgoori said:
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
Click to expand...
Click to collapse
Which ROM are you using?
DarthJabba9 said:
Which ROM are you using?
Click to expand...
Click to collapse
MIUI EU 13.0.9
panjgoori said:
MIUI EU 13.0.9
Click to expand...
Click to collapse
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
I accidently bricked my phone and its in EDL Mode now. Can you help me please
panjgoori said:
I accidently bricked my phone and its in EDL Mode now. Can you help me please
Click to expand...
Click to collapse
Sorry, I know nothing about EDL mode for this device. But I'm sure there are lots of tutorials on XDA or in a general Google search.
Vendor_Boot recovery links and instructions added.
Small changes made in instructions.
New version (7.8) for TWRP A13 (standard).
New version (11.1_1) for OFox (vendor_boot).
New version (11.1_3) for OFox (standard).
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
néonaloj said:
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
Click to expand...
Click to collapse
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
rashazad said:
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
"recovery.img" being your extracted recovery image address.
4. Reboot.
Click to expand...
Click to collapse
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
nehalchoy said:
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
Click to expand...
Click to collapse
That error does not seem to be related to the process.
Something (probably free apace) is wrong about your pc or phone.
What ROM were you using?
rashazad said:
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
Click to expand...
Click to collapse
Well I didn't want to make a complete tutorial ...
To flash twrp trough twrp, 'install' > change with "image" > install the recovery.img.. It has always worked, for long years..
About flashing a A13 rom (++) coming from MIUI A12 (I each time restarted from scratch, re-installing global MIUI) : I've tried a lot of ways.
I began to install A12 twrp skkk in fastboot mode (1st 'boot' then flash), reboot to recovery, then upgrade to A13 twrp through twrp (reboot to recovery), then A13 FW > bootloop ;
I tried flash A12 twrp (fastboot)(reboot to recovery), then A13 twrp (fastboot too)(reboot to recovery), flash FW > bootloop ;
I also tried A12 twrp (reboot to recovery), then FW (reboot to recovery ok), A13 twrp (reboot to recovery) > bootloop...
I won't list all what i did ! but finally I flashed A13 twrp directly on A12 MIUI (reboot to recovery ok), flash FW (reboot to recovery ok) and that worked. I then flashed my A13 rom (without rebooting system first) > reboot to recovery +reboot system, and finally flashed Gapps, magisk and other stuff. I do know it's not a common way, but the one that worked.
EDIT : I do know it can work (maybe even easier) to flash the MIUI A13 fastboot rom, but had a other device hard bricked some time ago doing this. That's why i tried to only flash the FW
PS : if you can help, I've only one issue to solve yet : I've flashed magisk 26.1, i could have bank & pro apps to work correctly, the only app that I cannot is the FAI tv (error P531 'can't reach my account' (even if i'm well connected), probably root detected.. thanks ! (ofc it's on the deny list, with magisk modules such as Universal Safetynet Fix, zygisk ....)
And edit 2 : I forgot to thank you for this thread !
Common way to flash rom with upgrade (not update) is clean install.
Also, magisk handles safetynet with no problem. No need for that. And zygisk is not module.
For that specific application, check that it is fully selected in zygisk since sometimes all checkboxes for application is not selected.
You're welcome