So the story begins when I tried to relock my phone after having issues with my bank app so I tried to lock my rog phone, after trying multiple commands such as fastboot oem lock and others only one worked which was "fastboot oem asus-csc_lk". The command succeeded but it then shows boot_b unbootable and boot_a unbootable. I could no longer run any of the flash commands and can't get back into android. I am still able to run the boot command like "fastboot boot something.img". The flash commands gets phone locked error.
kevinone27 said:
So the story begins when I tried to relock my phone after having issues with my bank app so I tried to lock my rog phone, after trying multiple commands such as fastboot oem lock and others only one worked which was "fastboot oem asus-csc_lk". The command succeeded but it then shows boot_b unbootable and boot_a unbootable. I could no longer run any of the flash commands and can't get back into android. I am still able to run the boot command like "fastboot boot something.img". The flash commands gets phone locked error.
Click to expand...
Click to collapse
Maybe boot to recovery and do a clean flash?
I am unable to boot to recovery or flash
kevinone27 said:
I am unable to boot to recovery or flash
Click to expand...
Click to collapse
Didn't you say you can boot to an image target?
I can run a command that is "fastboot boot recovery.img" but it won't actually boot into said image or just stuck there for days.
kevinone27 said:
I can run a command that is "fastboot boot recovery.img" but it won't actually boot into said image or just stuck there for days.
Click to expand...
Click to collapse
We’re you full stock when you locked?
PM me if you really can't figure it out. I'll try to help you when I'm free (probably tomorrow).
Arealhooman said:
We’re you full stock when you locked?
Click to expand...
Click to collapse
I'm not sure if it's running full stock, but after my attempt at running a custom OS I went and reflashed the stock OS from the official asus support website.
kevinone27 said:
I'm not sure if it's running full stock, but after my attempt at running a custom OS I went and reflashed the stock OS from the official asus support website.
Click to expand...
Click to collapse
It should be 100 percent stock before locking. Can you unlock your BL again?
Unfortunately no, none of my fastboot commands worked (even the oem ones) and I am unable to unlock via apk due to being unable to access my android os.
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
I can not vouch for the software though.
Arealhooman said:
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
Click to expand...
Click to collapse
Thanks, I will give it a try tomorrow.
Arealhooman said:
I saw someone have a similar problem and they said using this tool (free version) and using it to boot into Fastboot help. I doubt it can hurt.
Click to expand...
Click to collapse
I gave the free version a try unfortunately it won't detect the device unless I go to fastboot mode. The free version seems to only have Samsung and requires it to be unlocked.
I also managed to run twrp temporarily on slot_A which probably means that it wasn't fully stock. TWRP isn't able to do much though with the lock state it's currently in.
Is there any other way to bypass the lock state?
My problem is solved, I don't know exactly what happened, but I left my phone in it's endless reboot between slot_a and slot_b until it ran out of battery. After I charged it back from 0% the problem seems to have been fixed, it started the encrypting process and new phone setup.
Related
How long should fastboot oem unlock take?
I'm following these instructions to unlock phone (then get CM7 running on it).
I ran fastboot oem unlock command with ID (have JDK and SDK installed and added the tools).
Been sitting in command promt for about 10 minutes now... How long should this take? What can/should I do now?
Got tired of waiting after over hour, pulled battery, booted up.
I get Unlocked message at top of screen when it starts booting but then it gets into infinite boot showing Motorola screen then black screen over and over... any thoughts?
I believe now you have to flash recovery through fastboot, and then use the recovery to flash a ROM.
ravilov said:
I believe now you have to flash recovery through fastboot, and then use the recovery to flash a ROM.
Click to expand...
Click to collapse
And hope waiting that hour didn't drain the battery because it doesn't charge in fastboot.
Recovery would not start at all either, so I could not flash new ROM.
I ended up being able to do fastboot and delete user data, this made phone bootable again.
Then installed CWM and flashed ROM.
All is good now, was a little scare though
Thanks,
I'm not very good at this, I've been an iPhone user for the longest time. I did not turn fastboot off before I flashed twrp 2.6.3.0. I'm stuck on the booting screen, I can bring up the boot loader screen but the phone will not actually boot up all the way. Any help is appreciated...is there a way I can save this?
zhooper21 said:
I'm not very good at this, I've been an iPhone user for the longest time. I did not turn fastboot off before I flashed twrp 2.6.3.0. I'm stuck on the booting screen, I can bring up the boot loader screen but the phone will not actually boot up all the way. Any help is appreciated...is there a way I can save this?
Click to expand...
Click to collapse
your recovery is old, use 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
your recovery is old, use 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ok, I got that much but it still doesn't boot. I know I need an OS, but after the hassle I've been through I would like to go back to stock. But can't seem to find the right places to go for that, any advice?
zhooper21 said:
Ok, I got that much but it still doesn't boot. I know I need an OS, but after the hassle I've been through I would like to go back to stock. But can't seem to find the right places to go for that, any advice?
Click to expand...
Click to collapse
Sure use the fastboot getvar all command to get your phones info and find your RUU here >> http://www.androidruu.com/index.php?developer=M7
or in the HTC1Guru link in my signature
clsA said:
Sure use the fastboot getvar all command to get your phones info and find your RUU here >>
or in the HTC1Guru link in my signature
Click to expand...
Click to collapse
I'm actually still having troubles with getting it back to the stock RUU. I am running on a Mac so I know the commands are different, any help there?
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you
Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Has anyone found a method to close the bootloader again? I'm thinking of opening it but I'm worried that I won't find a method to close it if necessary.
zero5liters said:
Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Click to expand...
Click to collapse
try "fastboot oem asus-csc_lk". After wipe data.
sakun-ice said:
try "fastboot oem asus-csc_lk". After wipe data.
Click to expand...
Click to collapse
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
zero5liters said:
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
Click to expand...
Click to collapse
If you haven't tried it, you can try it with:
-fastboot oem asus-back
-fastboot oem asus-csc_lk
-fastboot flashing lock
-fastboot flashing lock_critical
-fastboot oem lock
-fastboot oem lock_critical
-fastboot flash !frp-partition! default_key.bin
-fastboot oem asus-lock
No. Didnt work. 'Command not supported in default implemantation' All of these commands.
I did not try the *critical commands and the "frp partition". I had not time to read me in on that. And i dont want to brick the phone complete.
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
No,
i tried it but fastboot doesnt recognize the command.
But thanks. I now startet the "Repair" @ asus.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
Yeah ! works for me too
OTA update working ?
rafik25 said:
OTA update working ?
Click to expand...
Click to collapse
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
schizophaser said:
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
Click to expand...
Click to collapse
Same, though I expected that since I rooted.
For any one wondering how to update, just take the firmware file from ASUS's site, place it in your phone's internal storage, then either wait a few seconds for the update notification to pop up or restart your phone (you should see it then). Follow the prompts from there.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
sakun-ice said:
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
Click to expand...
Click to collapse
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
schizophaser said:
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
Click to expand...
Click to collapse
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
sakun-ice said:
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
Click to expand...
Click to collapse
Yes, that should be enough.
schizophaser said:
Yes, that should be enough.
Click to expand...
Click to collapse
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
sakun-ice said:
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
Click to expand...
Click to collapse
I can't say much about this. I don't think it's going to be a problem, but of course you're doing it at your own risk.