Related
Today I wanted to install the lineage os, but, to ensure, I installed the stock rom in my moto g4 plus.
I wiped dalvik, system, data and cache.
Then I flashed the rom and the gapps, but when I did the reboot the cell phone was in an infinite loop, but not normal, the bootanimation of the lineage appears but it never stops.
what do I do??
Sorry for the spelling mistakes, I used google translate
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
robot_head said:
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
Click to expand...
Click to collapse
I can't acces my custom recovery and can't install trough my computer
advanced_gamerBR said:
I can't acces my custom recovery and can't install trough my computer
Click to expand...
Click to collapse
Which stock ROM and custom recovery did you install, by the way?
echo92 said:
Which stock ROM and custom recovery did you install, by the way?
Click to expand...
Click to collapse
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
advanced_gamerBR said:
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
Click to expand...
Click to collapse
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
echo92 said:
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
Click to expand...
Click to collapse
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Thank you for helping me, I was able to access TWRP when my battery ran out, which interrupted the loop
advanced_gamerBR said:
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Click to expand...
Click to collapse
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 [edit: minutes] (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
echo92 said:
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 seconds (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
Click to expand...
Click to collapse
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
advanced_gamerBR said:
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
Click to expand...
Click to collapse
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
echo92 said:
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
Click to expand...
Click to collapse
I've re-flashed the stock rom and it's working well
Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.
Managed to brick my A1. The only screen its able to go to is either fastbook, or recovery. And even then, doesn't always necessarily boot into recovery, have to plug into computer and go into command prompt (fastboot boot oreo_3.2.2_recovery.img) to get it into TWRP.
Currently can't seem to flash *any* roms, I have a stock rom ("tissot_100108_stock" cant remember where i got it from). Which successfully flashes, but then on reboot gets stuck on the Android One screen. Longest i have waited before giving up is an hour. Even when i flash this rom and reboot, i get a message on TWRP saying "No OS installed"
Tried doing this: [wont let me post link] (MiFlash) method and got an error, basically does not work.
Super frustrated, at my wits end, would just like to flash stock rom and sell this thing or let it sit in a drawer at this point. Thanks in advance.
same problem here...
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
cantras said:
I have the exact same issue and also came here for that to ask for help.
Xiaomi Mi A1 was running 8.1 OTA updated and then I tried to flash Lineage, but it did not work. I wiped my phone and now it can't install anything, not via TWRP nor with Mi Flash.
I hope we can find a solution.
Click to expand...
Click to collapse
hopefully! i posted on the xiaomi subreddit but no help. i was on 8.0 when i started this whole misadventure.
I got somewhere, I think.
I went into TWRP, switched from B to A booting. It then starts Android but gets stuck in the boot screen of Android one with the colored bar.
I then tried MiFlash again, going directly to the folder which containts the .bat files. It started flashing it finally.
I am back to a working system.
Let me know if it works for you.
you guys should try flashing the latest stock rom 8.1 July running the bat file of your choice located in the factory image through fastboot
the different custom recoveries and miflash are sometimes buggy
run the script directly on fastboot
Sent from my Nexus 6 using Tapatalk
I think we need a concise guide to how to get TWRP up and running on the K88 Trek 2 HD because I'm stuck and I don't want to flash the wrong thing and brick it
1 - Downloaded jasminetool, jasmine-twrp-7.1-r3.img, and zadig-2.4.exe
2 - Enabled USB debugging on K88
3 - Rebooted to EDL mode via adb reboot edl
4 - Used zadig-2.4.exe to install WinUSB driver
5 - Used jasminetool read recovery stockrecovery.img and got success - img file is 49,152kb
6 - Used jasminetool write recovery jasmine-twrp-7.1-r3.img (24,576kb?) and got success
7 - System reboots and restores stock recovery
I tried preventing the automatic reboot and when I try to go to recovery with volume+ and pwr it just flips up the logo and reboots like there's a problem, I presume the system is restoring the stock recovery because of this. System is Android 6.0.1 kernel 3.10.84
What should I do?
Also, my goal is to get a normal dialer for cell phone calling on the tablet and I'm just assuming that AOKP does since no one answered when I asked in the rom thread so if someone could also answer that question for me before I go to all this effort for no real reason that would be great
Currently operating under the assumption I need to manually update to official 7.1 (jasmine-7.1.1b15-full.zip) via the stock recovery then repeat the above steps since I now notice that version matches the twrp version
Link:https://r.tapatalk.com/shareLink?ur...share_tid=3825775&share_fid=3793&share_type=t
evilwise said:
Currently operating under the assumption I need to manually update to official 7.1 (jasmine-7.1.1b15-full.zip) via the stock recovery then repeat the above steps since I now notice that version matches the twrp version
Click to expand...
Click to collapse
Enviado desde mi K88 mediante Tapatalk
juniorgerman said:
Link:https://r.tapatalk.com/shareLink?ur...share_tid=3825775&share_fid=3793&share_type=t
Click to expand...
Click to collapse
Thanks, yeah I did get TWRP running just fine once I upgraded to a 7.1 stock rom. Now I guess I'll just be awaiting a rom that actually can dial on the cellular network. Seems like a great device now that it has recovery hopefully we'll see a lot more development on it as people get to be aware of it.
Hi guys,
Easy way to flash TWRP from computer for Mi 8 SE.
Download suitable file from below.
Twrp 3.2.3-1227 Compatible with Android 9 (Beta v8.12.27 and upper versions)
https://www.mediafire.com/file/qtdm3qlivcn4gmw/MI8_SE_TWRP_Yukleme_Araci_81227.zip/file
Twrp 3.2.3-1102 Compatible with Android 8.1 (Lower versions than Beta v8.12.27)
https://www.mediafire.com/file/bsvuaxcg1vghayz/MI8SE_TWRP_Yukleme_Araci.zip/file
1. Your phone bootloader should be unlocked.
2. Make sure USB drivers are installed to PC.
3. Turn on USB Debugging. Settings - More - Developer Options - Usb debugging
4. Press Volume down + power button and reboot to fastboot mode.
5. Connect your USB cable to PC
6. Unzip downloaded package and run twrp-yukleme.bat file.
7. Press enter to continue. When it's done enter to exit program.
8-For steady TWRP install Magisk16.4 when you boot into TWRP.
Thanks to by.Trabzonlu from miuiturkiye
downloaded multiple times
unpacking gives a bug
I tried both links
olinen said:
downloaded multiple times
unpacking gives a bug
I tried both links
Click to expand...
Click to collapse
Thanks for your report.
Links and zips are updated. It should unzip fine now :good:
it's ok, just that I had to run the program first and only after that I joined the mobile in the fastboot. Otherwise, he made a mistake
Thx :good:
9
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me
Alimataei said:
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me
Click to expand...
Click to collapse
TWRP 3.2.3 12-17 works for android 9 ?
TacoNikky said:
TWRP 3.2.3 12-17 works for android 9 ?
Click to expand...
Click to collapse
1102 also works for Pie.
I try to install this recovery but nothing happens at all I have installed the rom miui.eu 10.2.2.0 apparently this rom mr deleted the recovery that had already installed before installing this rom:crying:
Have someone trying treble gsi rom? How to proper install? Thanks in advance.
TWRP-3.3.0-0423 whit magisk 19.0 root For Xiaomi mi8 SE
Download Link:
https://mega.nz/#!CrhTmKgY!PE7lXdLtCzPqYO55ulCx2faFLVqPi6mpXXaYOnbbB8s
Could it be possible that this TWRP will work on mi 9 se, too?
Sent from my [device_name] using XDA-Developers Legacy app
putti71 said:
Could it be possible that this TWRP will work on mi 9 se, too?
Click to expand...
Click to collapse
This is mi8se forum!! TWRP is specific for each phone (different kernel, processor...) so there's no way you could install this TWRP img on another phone than Sirius
Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?
Hi! Is there an updated twrp for miui 11 android 10. First time to install this.
greendra8 said:
Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?
Click to expand...
Click to collapse
Same as mine. How's your device now?
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Hi guys. Im getting the error after flashing twrp. At first it works. I will flash rom so i reset it and wipe al data. But it didn't boot into recovery mode. It stays at fastboot. I just dl this installer from somewhere here in xda so i didint know thatmagisk should be flashed afterward. Pls help. I . getting error authentication failed
Trojan00 said:
Same as mine. How's your device now?
Click to expand...
Click to collapse
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.
greendra8 said:
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.
Click to expand...
Click to collapse
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?
Trojan00 said:
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?
Click to expand...
Click to collapse
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.
greendra8 said:
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.
Click to expand...
Click to collapse
Bro i downloaded the stock fastboot firmware. But in mi flash it says can not found file flash_all.bat