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
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!
Hi,i have flashed pie beta update .121. Want back to oreo, but cannot install via dload and erecovery. Any recovery for emui 9. Which images must flash via fastboot?
Is your bootloader unlocked?
Yes, bootloader is unlocked. When is lock no difference
Cisuwek said:
Yes, bootloader is unlocked. When is lock no difference
Click to expand...
Click to collapse
Since the bootloader is unlocked you can use this: https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
It works for me
Replace the TWRP image on the images folder with this one: https://forum.xda-developers.com/huawei-p20-lite/development/recovery-testing-t3783587
After flashing twrp and restarting, vol+ doesn't work, boot normal way.
Cisuwek said:
After flashing twrp and restarting, vol+ doesn't work, boot normal way.
Click to expand...
Click to collapse
Flash p20 lite twrp, of success, restart phone, when there are 3 options, press power biton to boot, press vol up 3 sec to enter erecovery etc, and do nothing for 5 secons aitomatocaly boot in System you need to press vol up 3 seconds, then, when you are in e recovery, use option emergency backup, or somthing like that, then phone will reboot to emergency System mode, press option factory reset or somthing like that, second option from top if im coretly remeber, after that you will be in twrp recovery.
So,. If want to use downy, replace downy twrp with p20 lite one, do all what downy said, but, where you need to boot in twrp, do as writed i, and continue with downy after you are in twrp. Good luck
OK, do it in same way, it works. Earlier flashed this twrp, but after few seconds phone restart to system. Working and don't know why
Did you manage to downgrade?
Yes, thanks a lot.
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.