Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
What's going on I had my watch rooted tried, make it back to stock tried it, rooted it and once more tried it I get error 7 everytime
I'm using Ubuntu 14
I can't even sideload
Drivers are all working
But for some reason my Linux machine won't talk to my watch
Can someone help all I need is some codec
I'm sure this has been answered before (infact, I remember answering this exact question).. The stock recovery has ADB broken, so sideloading doesn't work, nor does ADB's shell. The reason you're getting error 7 is because you re-rooted, which changes app_process32, which the update is looking to patch and finds that it doesn't have what it expected there. That said, here's something you can do.
Follow the instructions found somewhere else on these to push the update to /cache/recovery with the watch rooted, I'm not sure if the stock recovery image has an apply /sdcard/update.zip option, but you may be able to get away with pushing the update there.
If you're using the /sdcard/update.zip option, make sure that the update is pushed. If your watch is rooted, you need to unroot it manually by using the image found in the Restore Tools image. (If you're on 5.1 I believe it's 49Ksystem.img but I can't remember.), you'll be doing fastboot flash system <system-image>, then reboot into recovery and hit the apply update.zip option. You're done.
If stock recovery does NOT have an apply update.zip option, you need to search on the G Watch forum here, there is a proceedure that involves pushing the ZIP to /cache/ and writing a recovery script into /cache/recovery. You will need to stage that, but instead of rebooting when the instructions tell you, you need to reboot to the bootloader (adb reboot-bootloader) and preform the step I stated above, reflashing your current version's system image. Once finished, simply reboot and the OS will start updating automatically.
NOW! The Easy Way!
Download the latest LG G Watch Restore Tool package (I think it's 9.8 now), it has been updated with the latest Android Wear image. So all you need to do is start it and run Return to Stock, your watch will be restored to 5.1.1
Hi,
For those who didn't receive the OTA by now and are on stock, non-rooted, here's the link : (rename to update.zip, update it via settings/update or update via recovery (update or adb sideload) etc.....)
Don't know if it'll work when on stock N-B06 (can't test it because i'm on custom ROM ). Otherwise downgrade to B05 again and upgrade to B08.
EDIT : For those where update.zip not show up (which is a common issue, don't panic, you can wait for the FULL update later on...) try :
1. rename to update.up or fota_B08_B12_ssl.up or A2017GV1.2.0B08.zip
2. try to update over recovery. Inthere try to adb sideload or update via SD
2a : ADB sideload : boot phone into recovery, setup ADB, put zip in ADB folder (you know...or drag it later on in terminal...), open terminal in ADB folder (shift+rightclick open terminal here), type adb devices (there has to be your "device-number" and recovery),on phone apply ADB update, then type command : adb sideload nameofyourzip.zip and enter. Done !
3. don't forget to try either on intSD or extSD
4. wipe cache in recovery and try again...
AFH link : https://androidfilehost.com/?fid=962021903579488106
updated in DownloadCenter : https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
don't just HIT&RUN....there's a :good: button for some reason
Hi,
my Device is on stock B05 and non-rooted. I've downloaded it. renamed und put it in to root of the internal Memory - still no Update found...
Same for me. I've tried place update.zip in internal storage and sd card but update not found.
Adb sideload works
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
dodo34 said:
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
Click to expand...
Click to collapse
I did that to but as always installation failed. What i did is to boot into recovery and choose there adb sideload. On your computer you send valid file with adb sideload update zip to the phone. Of course you have to have valid adb files installed on computer and know your way how to use power shell.
Can someone extract the modem of this rom and upload it here?
That would be really nice.
some new features spotted ?
Angelo_0 said:
some new features spotted ?
Click to expand...
Click to collapse
No new features. However, I have the impression that the fingerprint scanner is quicker. Anyone else?
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
no full rom?
how to enable VoLTE ?
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Same for me.
I needed to sideload the OTA (not an OTA anymore :silly.
And nothing relevant too in rom. It's enough for me anyway : security patch is already good to have.
Enjoy!
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Updated through ota (from b05). Indeed, things seem a bit faster. Most noticable for me is the fingerprint sensor.
Too early to confirm, but battery seems better than B05.
i think screen dpi a bit lower .so thats good
and ram performance noticable better
Hi
I am actually on B06, if I make a downgrade to B05 I loose all my data?
no .
Is there any TWRP version of this update available?
Upgraded to B08. Method:downgraded to B05 and then updated from recovery. Till now all is ok
Anyone got aboot from B05 (emmc_appsboot.mbn)? I am rooted stock. I restored untouched system and stock recovery but I get an aboot error on flash. I flashed aboot downgrade to B01 back in April to get fastboot back : https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Try grabbing the required update files from the teammt site, using the huawei update extractor to grab the partitions you need and then manually flashing with fastboot.
I have the mate 10 pro and usually after getting into a bootloop I flash the kernel, system & recovery_ramdisk then everything starts working as it should
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
I meant for the original rom, not the 8.0 one, probably should have clarified that in my post
Raptorta said:
No don't do that, if you are on 7.1 do not flash files from an 8.0 rom because there is more to an oem update then the kernel and sys partition.
If you are in twrp you can flash noCheck recovery. Then you can take your update.zip, hw.zip and data.zip (the 3 files you download from firmware finder, newer firmware might only have 2 files do to an updated data structure by huawei) and send commands to install them in the nocheck recovery. This way every partition will be updated to 8.0 base, this is like the erecovery method but better.
Click to expand...
Click to collapse
Well, okay.
I have the 7.0 structure of EMUI 5.1, and right now all I have is the update.zip for the 8.0 Oreo filmware of my EXACT model. I don't have hw or data.
So, I have a couple of questions...
From what I understand, you are trying to solve the problem using method 3, making it Oreo based. If so, how do I go about doing that?
Okay, sure, I can flash noCheck, but finding update, hw, and data for my model, let alone the 7.0 version is pretty hard.
Also, when I find it, what exactly do I have to do???
"Send commands to flash the files" whaaaaat??
All I have rn is adb, fastboot, and on my phone I have TWRP, eRecovery (won't work) and the update.app thingy
Maybe I could format the sdcard to ExFAT, move the 8.0 update.app and install it using the dload method?
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Raptorta said:
Okay so whats your exact model number and your region number (Cxxx). Maybe there is something on Firmware finder.
As for the commands:
You can push files to internal memory with ADB, For example if we have all 3 files and no check recovery we could push them with commands (Taken from the EMUI downgrade script cuz im lazy right now, Thanks to @ante0, @Atarii, @dkionline, @frantm, @Last****ingdroid, @mankindtw, @Pretoriano80, @shimp208, @zanooda123)
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
adb push ZIPS-HERE/update_data_public.zip /data/update/HWOTA/update_data_public.zip
adb push images/nocheck.img /data/update/nocheck.img
After that we can send shell commands to queue updates into buffer for the recovery so when the device reboots into recovery mode these commands are executed (this is used for official OTA's as well)
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
adb shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
After this we push our nocheck recovery to the recovery partition overwriting TWRP
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
After this all we have to do is reboot the device to recovery and the buffered commands run, installing the original firmware through the original recovery resulting in a perfect installation of the firmware with partition table overwrites if necessary.
This most might have become a little complicated, but I think this is the best way to update your system.
Click to expand...
Click to collapse
Okay, so here goes again.
My exact build number is RNE-L21C432B137, and my region number is +972 (country).
Anyways, by "ZIPS-HERE" what do you mean? This post isn't very well explained. Sure, you did include some major details, but I can't really understand it.
Also, I'm still wondering, is the dload method still a viable option? Thank you!
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Raptorta said:
Okay so you have an rne-l21c432
https://pro-teammt.ru/firmware-database/?firmware_model=Rne-l21c432&firmware_page=0
From here you can download firmwares for your device.
If you want to try the dload method you can but you should look for the exact same firmware (b137) to be safe, format your sdcard and follow the instructions for that method.
But for that you need the stock recovery which you can get by extracting it from the firmware. After that you can flash it the same way you flashed twrp.
Click to expand...
Click to collapse
Okay, could you tell me step by step, what to do?
I'm unable to format sd card. I need a reader.
Right this second, I'm on TWRP. What do I do?
In the site you've linked, I can find 6 versions of the software.
These are the names of it:
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 161084)
RNE-L21C432B137CUSTC432D001 (2.96GB, FullOTA-MF, v: 160963)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 134022)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 134021)
RNE-L21C432B137 (465.45MB, OTA-MF, v: 133902)
RNE-L21C432B137 (2.96GB, FullOTA-MF, v: 133901)
I have no idea what "v" stands for.
So, what do I download, and what do I do? Please help.
Also, could you use "English"? Meaning, explain it step by step.
Like, give examples, ect...
EXAMPLE:
Flash the custom rom using TWRP
Example:
Tap LineageOS from the selection menu in "Install" in TWRP
Swipe to install
Thank you so much!
UPDATE: I cannot download anything.
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Literally, every single link I go to, nothing. This site is useless.
Do you have Discord by any chance? Talking via a forum is really inefficient. If so, send me in PM's your discord.
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?