Related
I had stuck on ASUS logo, after I do a lot of researches, a lot of trials and errors for 4 hours. I managed to fix them and I wanted to share how I did here.
Easiest way to root lollipop WW-12.2.2.27
use KingRoot from http://www.kingroot.net/down ,It is android app which will run exploit to root the device successfully.
Not Kingoroot Kingoroot was unable to root. Towelroot v1 works only on Kitkat, but not lollipop.
To boot into fastboot mode
adb reboot bootloader
OR turn off device, press and hold power and volume up, until asus logo appear, and stuck at asus logo, that is fastboot mode, to exit fastboot with buttons, press and hold vol down and power button.
To restore stock recovery and ROM after you install TWRP or CWM, or unbrick device
First, note that stock recovery from http://forum.xda-developers.com/showpost.php?p=59055653&postcount=29, does not work for me (maybe everyone else as well).
I flashed it using fastboot flash recovery recovery.img, when I try to boot into recovery using, vol down and power, then select enter recovery, it stucks at asus logo.
First you need to flash TWRP_2.8.7.0.img from http://quarx2k.ru/asus_padfone_s/recovery/
using fastboot flash recovery TWRP_2.8.7.0.img It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, now you can go ahead and boot to recovery.
Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo. But now, we are going to need TWRP_2.8.7.0 to unlock bootloader.
Let's unlock bootloader
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP
You can check bootloader status with fastboot oem device-info
Before unlock :
(bootloader) Device unlocked: false
After unlock
(bootloader) Device unlocked: true
Let's flash stock Kitkat Firmware
You have to unlock bootloader becuase, well it is complicated.
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is http://datbak.com/links/padfone_s/asus_t00n_twrp_2_7_1_1.img
But this recovery has another bug, if you flash recovery and try to boot to recovery, you will get blank screen, but TWRP is indeed working, you touch the screen and it vibrates back. Anyway you have tofastboot flash recovery asus_t00n_twrp_2_7_1_1.img because it will be needed later for upgrading Kitkat to Lollipop.
If you don't unlock bootloader, you will not be able to boot into recovery directly without flashing to recovery partition Now let's get into fastboot mode, and fastboot boot asus_t00n_twrp_2_7_1_1.img, by booting into this recovery directly via fastboot without flashing it first, you will not get black screen bug of this recovery., if you boot to this recovery from recovery partition, you will get black screen as I told previously.
Now let's flash downgrade to 4.4.2 firmware from http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-99.99.99.0-user-wipedata.zip with TWRP 2.7.1.1.
This is for only WW SKU, not TW SKU. And all userdata will be wiped.
Browse all firmwares and there is TW SKU downgrade here : https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/
Ok, now reboot to system, and yeah, it finally boots now.
The recovery is still TWRP, not stock one, let's upgrade to lollipop and restore stock recovery using TWRP. Simply place http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-12.2.2.27-user.zip to root of Internal Memory, unplug usb, press confirmation in notification to begin install lollipop. After device reboot, it will stay blank screen for 5 minutes, don't worry, it is updating to lollipop, after upgrade is done, it will reboot, and recovery will be restored to stock recovery now.
Bootloader is still unlocked.
Another method to root is
fastboot flash recovery asus_t00n_twrp_2_7_1_1.img (recovery is restored to stock now remember)
then flash https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 with TWRP.
To lock bootloader again, boot into fastboot
then fastboot oem reset-dev_info
But I wouldn't recommend you to lock bootloader, you will lose ability to boot to TWRP recovery without replacing stock recovery, unless you are going to send your device to service center and claim warranty.
Files, fastboot and recoveries and bootloader unlock and super su for rooting
asus_t00n_twrp_2_7_1_1.rar https://mega.nz/#!355UmTCb!0Jn-0wlbGHG7lir8u9vq1l8BrR3dsepDdigqfJ9wRPk
twrp_2.8.7.0.rar https://mega.nz/#!GwRRBBjT!8ms39GK62XHairHOrxlmNJCwA-bDeaKA816Cg4lsQr0
Will this work for S Plus model?
It wont, using files from this thread might brick the device.
Sent from my SM-N910C using XDA Free mobile app
Hi im a noob so ill get straight to the point.
You said "Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo."
I have two question as follow:
1. So can i use twrp to flash stock rom or not?
2. Because I'm still at Kit Kat, I dont need to unlock bootloader and flash Kit Kat firmware right?
3. If so, Can I follow the tutorial until flashing the TWRP? but which TWRP that I need to install?
4. All these tutorial to unbrick needs to be done before you brick your phone right? What should i do if i already brick my phone?
Kindly advise.
ChevanLemon said:
Hi im a noob so ill get straight to the point.
You said "Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo."
I have two question as follow:
1. So can i use twrp to flash stock rom or not?
2. Because I'm still at Kit Kat, I dont need to unlock bootloader and flash Kit Kat firmware right?
3. If so, Can I follow the tutorial until flashing the TWRP? but which TWRP that I need to install?
4. All these tutorial to unbrick needs to be done before you brick your phone right? What should i do if i already brick my phone?
Kindly advise.
Click to expand...
Click to collapse
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is asus_t00n_twrp_2_7_1_1.img
If you are bricked, but you can still access fastboot mode, then you can unbrick and reflash stock firmware to your phone
First of all, Thank you so much for this GUIDE
Here are my doubts, and hoping for confirmation from you. My Padfone S is running well on latest kitkat firmware, rooted with SuperSu and TWRP 2.7.1.1 installed. Now, I wished to upgrade to Lollipop firmware.
Can I use the TWRP 2.7.1.1 to clean install the lollipop firmware instead of the stock recovery because I wished to wipe date, cache as well as SYSTEM before flashing?
My concern is I afraid if wipe the SYSTEM then the TWRP 2.7.1.1 would not be able to flash the Lollipop firmware successfully. Do I need to unlock bootloader in my case?
If I can do so, then can I still use the Flashify to flash TWRP 2.7.1.1 on the lollipop firmware, or I must use "fastboot flash recovery TWRP_2.8.7.0.img" method.
Thanks in advance for your kindly reply.:laugh:
Bootlooped
When I am upgrading my SuperSU and it requires a reboot,it automatically boot looped itself.
What should I do?
Linux4ever85 said:
Will this work for S Plus model?
Click to expand...
Click to collapse
Yes it work. Mine is Asus Padfone S Plus. Got bootloop problem. I have followed ninekaw guide. Thanks Ninekaw. U have save my precious padfone s plus
ninekaw9 said:
I had stuck on ASUS logo, after I do a lot of researches, a lot of trials and errors for 4 hours. I managed to fix them and I wanted to share how I did here.
Easiest way to root lollipop WW-12.2.2.27
use KingRoot from http://www.kingroot.net/down ,It is android app which will run exploit to root the device successfully.
Not Kingoroot Kingoroot was unable to root. Towelroot v1 works only on Kitkat, but not lollipop.
To boot into fastboot mode
adb reboot bootloader
OR turn off device, press and hold power and volume up, until asus logo appear, and stuck at asus logo, that is fastboot mode, to exit fastboot with buttons, press and hold vol down and power button.
To restore stock recovery and ROM after you install TWRP or CWM, or unbrick device
First, note that stock recovery from http://forum.xda-developers.com/showpost.php?p=59055653&postcount=29, does not work for me (maybe everyone else as well).
I flashed it using fastboot flash recovery recovery.img, when I try to boot into recovery using, vol down and power, then select enter recovery, it stucks at asus logo.
First you need to flash TWRP_2.8.7.0.img from http://quarx2k.ru/asus_padfone_s/recovery/
using fastboot flash recovery TWRP_2.8.7.0.img It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, now you can go ahead and boot to recovery.
Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo. But now, we are going to need TWRP_2.8.7.0 to unlock bootloader.
Let's unlock bootloader
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP
You can check bootloader status with fastboot oem device-info
Before unlock :
(bootloader) Device unlocked: false
After unlock
(bootloader) Device unlocked: true
Let's flash stock Kitkat Firmware
You have to unlock bootloader becuase, well it is complicated.
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is http://datbak.com/links/padfone_s/asus_t00n_twrp_2_7_1_1.img
But this recovery has another bug, if you flash recovery and try to boot to recovery, you will get blank screen, but TWRP is indeed working, you touch the screen and it vibrates back. Anyway you have tofastboot flash recovery asus_t00n_twrp_2_7_1_1.img because it will be needed later for upgrading Kitkat to Lollipop.
If you don't unlock bootloader, you will not be able to boot into recovery directly without flashing to recovery partition Now let's get into fastboot mode, and fastboot boot asus_t00n_twrp_2_7_1_1.img, by booting into this recovery directly via fastboot without flashing it first, you will not get black screen bug of this recovery., if you boot to this recovery from recovery partition, you will get black screen as I told previously.
Now let's flash downgrade to 4.4.2 firmware from http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-99.99.99.0-user-wipedata.zip with TWRP 2.7.1.1.
This is for only WW SKU, not TW SKU. And all userdata will be wiped.
Browse all firmwares and there is TW SKU downgrade here : https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/
Ok, now reboot to system, and yeah, it finally boots now.
The recovery is still TWRP, not stock one, let's upgrade to lollipop and restore stock recovery using TWRP. Simply place http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-12.2.2.27-user.zip to root of Internal Memory, unplug usb, press confirmation in notification to begin install lollipop. After device reboot, it will stay blank screen for 5 minutes, don't worry, it is updating to lollipop, after upgrade is done, it will reboot, and recovery will be restored to stock recovery now.
Bootloader is still unlocked.
Another method to root is
fastboot flash recovery asus_t00n_twrp_2_7_1_1.img (recovery is restored to stock now remember)
then flash https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 with TWRP.
To lock bootloader again, boot into fastboot
then fastboot oem reset-dev_info
But I wouldn't recommend you to lock bootloader, you will lose ability to boot to TWRP recovery without replacing stock recovery, unless you are going to send your device to service center and claim warranty.
Click to expand...
Click to collapse
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP --> link dead
Hi thank for your guidance on how restoring stock rom . Im having trouble detecting my phone when in fastboot mode, as you said to boot up into fastboot hold vol up and power and we will stuck at asus logo , but after i connect my pc and using adb cmd fastboot devices it didnt detect any devices and cant proceed to next step when i need to fastboot boot twrp 2.7.1.1
Currently im using twrp 2.8.7.0 , i want to use stockcrom because i need to use my padfone station (since any custom rom is not compatible with padfone station), any suggestions for this problem ? Thanks in advabce
So I accidentally booted up my device after wiping my ROM (I was going to install CM) and now I can't get back into TWRP to even access my backup. When I hold vol up I go into Huawei's eRecovery, on vol down it goes into the bootloader. I can't seem to get into TWRP anymore and fastboot doesn't seem to have the option to boot into recovery like adb does.
Found the stock ROM that I needed here: http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
can you
Code:
fastboot boot (your twrp.img)
?
yrbef91 said:
can you
Code:
fastboot boot (your twrp.img)
?
Click to expand...
Click to collapse
I'm not sure what I did but I got into TWRP but after wiping everything from fastboot (because I thought I would try to flash a ROM from there) so now I don't have my backup. Now I'm looking for a lollipop ROM (preferably stock) because I never got this to marshmallow and CM13 isn't flashing.
@BryanTheStrange
you should wipe first, then flash the ROM and GApps from TWRP.
I think you can restore to stock using dload folder method. There is a thread disscussing it.
Hey!
I Have a Kate running latest global developer that i unlocked officially through the mi unlock program.
I have been trying to install TWRP ( unoffical twrp, Alka, coffee) through ADB ( fastboot flash recovery twrp.img) for some days now but i wont work!!
ADB dont displays any errors and says everything finished but when i try to boot to recovery it's still stock xiaomi recovery??
What might be the problem and how do i fix it?
BTW, adb reports that the phone is unlocked (fastboot oem device-info).
Are you trying to boot TWRP straight after flashing it. If your booting the official rom first, then that is restoring stock recovery.
After flashing TWRP, manually boot the device with Vol + and Power button.
Alternatively boot TWRP with "fastboot boot <twrp.img>" and from TWRP reboot to recovery again so you actually boot the version on the device.
the newest dev rom has "feature" to revert your recovery back to stock when you boot the OS. so be prepared. after you flash your twrp, immediately boot to TWRP and wipe /system to install other OS.
corkiejp said:
Are you trying to boot TWRP straight after flashing it. If your booting the official rom first, then that is restoring stock recovery.
After flashing TWRP, manually boot the device with Vol + and Power button.
Alternatively boot TWRP with "fastboot boot <twrp.img>" and from TWRP reboot to recovery again so you actually boot the version on the device.
Click to expand...
Click to collapse
IvanKurnia said:
the newest dev rom has "feature" to revert your recovery back to stock when you boot the OS. so be prepared. after you flash your twrp, immediately boot to TWRP and wipe /system to install other OS.
Click to expand...
Click to collapse
THANKS! That was the problem. Now everything works.
Hi all,
Currently running Oreo (via OldDroid manual update) then LOS 15.1 (Berkley unofficial) on top, which is great but would like NFC, buttons, flashlight.
What is the best method to reinstate this functionality? I have tried the rollback for OldDroid rollback to no avail. I believe this method assumes you are rooted, which i am not.
Happy to be on EMUI 5 if necessary as i believe i can now update to Oreo OTA.
Cheers
Can i provide further pertinent information or ask elsewhere to get replies?
What did you do in the fist place to go from stock oreo to LOS 15.0 ; any links ?
Thank you.
I flashed the system image using "fastboot flash system system.img" via article https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Cheers
I think, once unrooted, you'll have to flash back stock system.
oslo83 said:
I think, once unrooted, you'll have to flash back stock system.
Click to expand...
Click to collapse
Great, thank you. I am not rooted so I extracted the system.img from STF-L09SC432B360a (from http://pro-teammt.ru/firmware-database/?firmware_model=STF-L09&firmware_page=0) using this guide https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Then using that stock emui 8 system image:
"fastboot flash system system.img"
I receive the following error:
error: cannot load 'SYSTEM.img'
Any ideas?
Cheers
Another attempt at system.img extract using my windows box and the windows software referred to in https://forum.xda-developers.com/mat...files-t3756733.
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
I performed this reset and device booted to TWRP some commands took place but too quick (saw selinux buts thats it). Device rebooted twice then loaded Huawei eRecovery where the only option is :
Download latest version and recovery
Restore system with wifi
Entered wifi details
Getting package info from server
Getting package info failed.
Booting into TWRP the 'Factory Reset' option performs the same process that i saw when Huawei eRecovery recommended the factory data reset. Some i'm confident in what happened at that point now. Unsure as to what to try at this point. The phone does not boot into EMUI and will only boot to Huawei eRecovery.
The bootloader is unlocked, as per the process to install LineageOS 15.1 in the link in the OP. I've not checked if its still unlocked, but guess that could be causing a problem?
Just checked and bootloader is unlocked.
Interestingly the process to re lock it from the Huawei site (https://emui.huawei.com/en/unlock_step) shows that you have to use the same command to lock the bootloader as to lock it again:
Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.
If i follow those instructions i get the below error:
Code:
fastboot oem unlock **************** <-my 16 digit code
...
FAILED (remote: already fastboot unlocked)
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Thanks. So I can leave the boot loader unlocked at this point and run stock emui? I'll flash stock recovery. Perhaps that will suggest factory reset and then I'll be able to boot.
Thanks again.
oslo83 said:
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Click to expand...
Click to collapse
In order to revert to the stock recovery is it necessary to flash all three recovery images from the update.app file? :
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Looking at flashing the recovery_ramdisk image with the stock version i have extracted using the below:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Noticed the stock recovery_ramdisk i extracted has a filename of 'RECOVERY_RAMDIS.img', not ending in 'K' for 'RAMDISK. Presumably i can simply rename my recovery_ramdisk to "RECOVERY_RAMDISK.img" unless a 15 character filename is a limitation, or adjust my fastboot command to :
Code:
fastboot flash recovery_ramdisk RECOVERY_[B]RAMDIS[/B].img
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
mightyjcb said:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
Click to expand...
Click to collapse
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
oslo83 said:
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
Click to expand...
Click to collapse
Many thanks @oslo83 followed that and just as you said hardware functioning correctly once again!
One further question for future reference, am i now in a position to apply OTA updates when released?
Cheers
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
mightyjcb said:
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
Click to expand...
Click to collapse
You need to flash stock recovery and do a factory reset in stock recovery.
oslo83 said:
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
Click to expand...
Click to collapse
Great, i should be able to meet this criteria quite easily then :
+ I've never rooted the device
+ I have reverted to stock recovery
+ I flashed the stock kernel over the top of the button fix kernel mentioned earlier in this thread.
Thanks again for your help, much appreciated.
zxz0O0 said:
You need to flash stock recovery and do a factory reset in stock recovery.
Click to expand...
Click to collapse
That seemed to do the trick! Ta.
I have a problem that i never make it into recovery again. I am used to adb/fastboot, this is my 5th device and i happily used different custom roms as lineage, havoc, crdroid for about 7 years and thus am familiar with the concepts of a/b, recovery, adb/fastboot and so on.
Now, when i "flash_all" with stock from here (V10.3.17.0.PFQEUXM) on my a3, i suppose both slots a and b are overwritten with stock. interestingly this stock rom only boots in a-slot, not in b-slot.
when i now just "fastboot flash recovery twrp...." with 3.3.1.2 and hit the manual enter to recovery (power + vol up), i just get a "no command" error - no twrp in sight.
i also tried this with flash_all V11.0.2.0.QFQEUXM rom (a10) and fastboot flash recovery twrp 3.3.1-17 Q from mauronofrio - same result.
anyone knows what i did wrong?
basically i didnt enter team win recovery for some good amount of tries which slightly terrifies me at this point. (help)
Should i use the global versions instead of the europe ones? Do i need to use "fastboot flash BOOT twrp.." instead of "fastboot flash recovery twrp.."?
I am also happy for suggestions where i could pose this issue more appropriate.
//update: i am now in stock rom and could root it with flashing a magisked boot.img but still cannot enter twrp recovery (-> "no command").
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
thanks @garylawwd
garylawwd said:
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
Click to expand...
Click to collapse
So to be sure: i have stock 11.0.3.0 europe from here installed and i am in slot a now and i cannot go into twrp because it says "no command".
i go to fastboot now, then
Code:
fastboot flash boot twrp.img
with a recent twrp that can run android 10 from here and then power + vol up without switching slots.
garylawwd said:
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
Click to expand...
Click to collapse
how can i flash a boot.img from twrp? i thought, i can only flash .zips from twrp? Also do i need to take spacial measures to be able to read internal memory in twrp?
//edit: i tried to flash named twrp but it wouldnt boot up into recovery, instead went straight into fastboot. so i flashed boot with stock boot again. no solution in sight.
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
_mysiak_ said:
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
Click to expand...
Click to collapse
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
tutankpusch said:
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
Click to expand...
Click to collapse
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
_mysiak_ said:
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
Click to expand...
Click to collapse
Thanks @mysiak_d
I used for example this method with this recovery bc it should work with android 10.
straight into fastboot instead recovery :/