Question How to flash stock firmware/ROM obtained from Asus website? - Asus Zenfone 9

Hello I've downloaded latest stock firmware/ROM from: https://dlcdnets.asus.com/pub/ASUS/...2202-ASUS-32.2050.2050.34-1.1.1-2210-user.zip
But unable to find any guide or tool on how to install it? From searching I understand there's supposed to be a flashfile_AFT.cmd, but can't find it in the zip. I've unlocked bootloader already. thanks

Flashing a working device? Just copy to root dir and reboot.

The instructions said to choose the zip from recovery, but stock recovery doesn't have an option to "install from zip". I only managed to flash the stock firmware after installing twrp.
Hermann2306 said:
Flashing a working device? Just copy to root dir and reboot.
Click to expand...
Click to collapse
That's also what instructions said, but I never got the notification you are supposed to get. Also, we are more likely to want to flash the stock firmware on a non-working device and I really can't find how we are supposed to do it with stock firmware.

For the updatenotification you maybe have to activate something like "apply updates on reboots / automatic updates" in developer options.
If the device only boots to fastboot you need a raw firmware file with the flashall.bat (I think it was WW-AI2202-32.2004.2004.84-REL-2206-M2.13.33.11-ASUS_1.1.1-user-20220722.zip for example). You can find it on romdevelopers.

All I had to do was take the firmware zip, plop it into my 'home' directory (i.e. not the actual root directory!), and I got the notification that an update was available via that zip. Standard installation after that.
I had and continue to have root access through Magisk, though I did have to apply that 'after update' magisk function before rebooting to complete the update. Rebooting without doing that loses your root access.

Yes, i mean that folder. Its "root" If you use the standard filemanager.

ok this will update the phone but if a phone was bricked, does any stock ROM file exist that can be flashed via fastboot?
Or is there a script which can be used to flash the contents inside payload.bin through fastboot? there are lots of files if payload.bin is extracted, not sure if everything it meant to be flashed?

Related

[Q] ACER Z3/z130 Europ is there a CWM recovery & zip file of the original recovery

[Q] ACER Z3/z130 Europ is there a CWM recovery & zip file of the original recovery
I've misteriously bicked my phone an remain locked in the boot proces....
Time to flash a new stock rom
as I'm flashing I prefer CMW as recovery above the unclear asus one (although I would like to be able to reflash the old one [warranty issues)
Can anyone give me a pointer scanned all of google (possibly the wrong way)
Thanks in advace]
dreuzel said:
I've misteriously bicked my phone an remain locked in the boot proces....
Time to flash a new stock rom
as I'm flashing I prefer CMW as recovery above the unclear asus one (although I would like to be able to reflash the old one [warranty issues)
Can anyone give me a pointer scanned all of google (possibly the wrong way)
Thanks in advace]
Click to expand...
Click to collapse
http://us.acer.com/ac/en/US/content/drivers - Click on O.S.
You'll find your stock system there. Instructions for loading it are included in the zip downloaded. I believe the EMEA Gen1 is for the generic worldwide version, but you might want to verify that. I know that the ORGFr one is for Orange France and the little "s" at the end would signify single SIM versions.
Found this guide to install recovery:
One. Loads Famaroot Just "Framaroot-1.9.1.apk" follow the link here.
http://forum.xda-developers.com/attachment.php?s=e12cbb38af7dd8a173308bb ...
The. Apk to be installed on the Z3 - Z3s / Once installed, it's ordered by phone root app Famaroot.
Two. TWRP 2.4.4.0 files stored on your SD-Card llllllll2510 to post the link here.
https://docs.google.com/file/d/0B0XQigIT17uEcDQtaDJ3U0UtOWc/edit?pli=1
PS. Files Name TWRP24Recovery_Z130_D10-02-14.img.
Do NOT paste it in a folder deep secret I do not find.
Three. Install app "[ROOT] Recovery Tools - Flasher" on the phone to me.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Then, with a flash TWRP 2.4.4.0 [ROOT] Recovery Tools - Flasher by.
Select top (Flash Recovery) and select the top (Other from Storage).
Then browse to the file TWRP24Recovery_Z130_D10-02-14.img. Flash to order
At the end of the process [ROOT] Recovery Tools - Flasher will ask you to reboot into recovery-mode or not.
I answered yes to the reboot to check the flash recovery ... we just finished it.
NOTE ***: It may cause damage to the machine. Or insurance
You must accept the risks in the operation of your own.
I found this on a forum that was in a foreign language to me and used Google Translate to get this info. You can find the original thread here:
http://droidsans.com/node/153986
For returning to stock for warranty issues, just use the original firmware you downloaded from Acer.
Tried the first part flashing the ROM using the provided stock Roms.
That failed it downloads but as soon as first real install occurs it rejects and aborts install access or accept error.
And returns the key part of the file name
I think? No expert at all ? The stock ROM updates do not match the previous ROM on my z30. Do not exactly know the specs of my original ROM proximus.... ??? Would have preferred gen ROM overriding all that stuff?
Or do I need to force adb/ fastboot only to load the system partition.???? But what is the adb/ fastboot command then exactly do I need to expand the zip a second time? After extract zip and instruction PDF?
Will delay cwm tarp after first signs of life of the phone.
Thanks for your answer
sometimes I know.
often I do not know.
Its always good to be able to ask.

How to export the OTA file

I've got the OTA file on my watch, but I cannot flash it since I am rooted, and I have a custom recovery. What I want to know is, how does one get that file out of their watch onto a computer, and how would I go about putting it into a flashable zip?
Apoplectic1 said:
I've got the OTA file on my watch, but I cannot flash it since I am rooted, and I have a custom recovery. What I want to know is, how does one get that file out of their watch onto a computer, and how would I go about putting it into a flashable zip?
Click to expand...
Click to collapse
The OTA should be a package named update.zip, I think you can flash this package directly from recovery. I´ve uploaded my update.zip on this thread:
http://forum.xda-developers.com/g-watch/help/5-0-2-update-lwx49k-t3034438
I´ve tried to flash throught TWRP and it does not work, maybe from stock recovery...

[GUIDE] Flash updates on rooted device

DISCLAIMER:
before doing anything to your device do a backup, im not responsable for any damage to your device
all needed files: http://www.mediafire.com/download/d9egpgwlh2a2c65/Desire610.zip
1) from device open xposed app and uninstall the framework ( you will install it back when the update is finished)
2) now extract debuggerd from the zip i provided and transfer it to your phone, copy it to system>bin folder with a filemanager ( i used root browser) overwrite the existing one and give permissions rwxr-xr-x
3) now put adb folder (extract it because is zipped) to disk c in your pc and put there the stock recovery
4) power off your device, then with power and lower volume key reboot it do fastboot mode
5) connect your phone to usb. over adb folder hold shift and right click it, choose open the command window here
6) a window will pop up write there: fastboot flash recovery recovery.img wait until its done
7) now reboot and finally flash the update
8) now you need twrp and root back. for twrp redo all the 3-4-5-6 steps ( put the twrp recovery in the adb folder)
9) for root download from xda the flashable zip of supersu and flash it with recovery ( before that remove any updates of supersu if you have any)
10) open xposed and install the framework back
11)done.
my english is bad so if you dont understand something let me know
what update is this? is it the stagefright patch or something else?
MGfusion said:
what update is this? is it the stagefright patch or something else?
Click to expand...
Click to collapse
yes for the ota that fixes stagefright, and for the future ones
Stuck
porozex said:
DISCLAIMER:
before doing anything to your device do a backup, im not responsable for any damage to your device
1) from device open xposed app and uninstall the framework ( you will install it back when the update is finished)
2) now extract debuggerd from the zip i provided and transfer it to your phone, copy it to system>bin folder with a filemanager ( i used root browser) overwrite the existing one and give permissions rwxr-xr-x
3) now put adb folder (extract it because is zipped) to disk c in your pc and put there the stock recovery
4) power off your device, then with power and lower volume key reboot it do fastboot mode
5) connect your phone to usb. over adb folder hold shift and right click it, choose open the command window here
6) a window will pop up write there: fastboot flash recovery recovery.img wait until its done
7) now reboot and finally flash the update
8) now you need twrp and root back. for twrp redo all the 3-4-5-6 steps ( put the twrp recovery in the adb folder)
9) for root download from xda the flashable zip of supersu and flash it with recovery ( before that remove any updates of supersu if you have any)
10) open xposed and install the framework back
11)done.
my english is bad so if you dont understand something let me know
Click to expand...
Click to collapse
Hey man need some help here. I followed all your steps but still can't manage to update my device. when it starts to update in recovery mode it gets upto 40% and then a red triangle appears. And then I am still in my old software (1.29.707.1)
adnan.rakib said:
Hey man need some help here. I followed all your steps but still can't manage to update my device. when it starts to update in recovery mode it gets upto 40% and then a red triangle appears. And then I am still in my old software (1.29.707.1)
Click to expand...
Click to collapse
If you have jmz kernel flash the stock one and overwrite again debuggered, if still dosent work get the debuggered file of your stock untouched Rom ( 100% clean no root,removed system files etc). If still fails that means you removed some system files from your device and ota blocks update
porozex said:
If you have jmz kernel flash the stock one and overwrite again debuggered, if still dosent work get the debuggered file of your stock untouched Rom ( 100% clean no root,removed system files etc). If still fails that means you removed some system files from your device and ota blocks update
Click to expand...
Click to collapse
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
vacs03 said:
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
Click to expand...
Click to collapse
Maybe you remove some apps from the system? If yes install them back from the at&t version here on this forum with the odex files. The only way to update is to have a 100% untouched Rom and a clean debuggered file
Need some help here
vacs03 said:
hi,
I flashed the stock kernel, stock recovery and pasted the debuggered you attached but it still fail on 40%...I don't know where to get the ruu for the eu rom...any ideas?
Click to expand...
Click to collapse
How did you flash the stock kernel?
adnan.rakib said:
How did you flash the stock kernel?
Click to expand...
Click to collapse
You can use the zip from jmz kernel and past there the stock lib files and kernel from a backuped stock Rom, then flash

[TWRP][RECOVERY] Asus ZenPad 8.0 Z380M (locked bootloader ok)

This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?

Help. Phone keeps booting into twrp recovery after update

I did a noobish thing and tried to get the ota update, it says I have the update but now the phone keeps booting into twrp recovery. Is there any way to fix this? And is there a code like LG has to fix it?
anth2387 said:
I did a noobish thing and tried to get the ota update, it says I have the update but now the phone keeps booting into twrp recovery. Is there any way to fix this? And is there a code like LG has to fix it?
Click to expand...
Click to collapse
I had the same issue bro. I seriously spent the last 3 days getting this **** fixed. I flashed all 4 of the stock roms, 2-3 different ways before I figured out the way that works 100% YOU'RE WELCOME!
1. What you have to do is download the stock Android 6.0 (USA) rom (google "KIW-L24, Android 6.0.1,EMUI 4.0,C567D003,United States" you can find it on a site called "GizRom." It's a fast download. )
2. Then you must download the Huwaei Update Extractor tool (google "HuaweiUpdateExtractor_0.9.9.3")
3. After that you must unzip the stock rom and open the UPDATE.APP file in the Update Extractor Tool.
Extract Boot.Img and Recovery.img
4. Flash them using these commands in a command prompt (I assume you have ADB tools installed.)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
5. After that is done, you must extract the "DLOAD" folder from the stock rom file you downloaded onto an SD CARD and place into your phone.
6. Once you have the SD CARD in your phone, press and hold VOLUME UP + VOLUME DOWN + POWER. The stock recovery will then install the stock ROM.
It'll take forever, so will the first few times it restarts/boots after installing the rom. Be patient. It will work.
7. Once you get back into Android, you can then run the updater tool to upgrade to the latest OTA. With everything stock, it'll work fine.

Categories

Resources