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
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!
Hello, I need help with my OPX.
I cannot enter Android or recovery, only Fastboot. Also, Fastboot on my PC can detect my device, but ADB cannot.
I had CM 13 and TWRP 3.0.2.0 installed on it, and now I was going to install LineageOS 14.1. I was first going to update TWRP to 3.0.3.0 because I thougt why not. I installed the new version with TWRPs image flashing and then it rebooted itself to Android. Then I was going to enter recovery again to install Lineage, the problem was that I couldn't even start the recovery. So now I tried to install TWRP with Fastboot, but it told me that the bootloader was locked which I thought was strange since I had unlocked it before.
So I tried to unlock the bootloader with Fastboot using "fastboot oem unlock" which it reported that it did and now I couldn't even enter Android.
But when I use "fastboot oem device-info", it says false to both unlocked and tampered and I still couldn't flash or boot into a recovery with Fastboot.
So now I can only boot into Fastboot Mode.
EDIT 2: Never mind, I fixed it with https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Can I remove this thread somehow?
You needed to flash OOS3 ROM or system partion before flashing 3.0.3 and Lineage
Yepp, I noticed. Found out later that it was because of the older bootloader. I had no idea about that before.
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Fixed by re-flashing original boot.img
zz305 said:
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Click to expand...
Click to collapse
Remove the "system_ext.." line from fstab, this may solve your issue if is the same issue for xperia 1ii. See link https://github.com/topjohnwu/Magisk/issues/3752
For fastboot command fail, does your device have fastbootd?
zz305 said:
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Click to expand...
Click to collapse
Reflash the whole FW again.