I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
Related
Trying to install TWRP to flash a custom ROM, but still without success.
After trying the first few times, holding Vol Up + Power either booted the stock recovery or just booted android.
Then I tried to boot recovery directly through adb commands, and since then recovery is in a bootloop even if I flash TWRP again.
Is there any sollution? I also tried installinh through the TWRP app, but cant flash because it requires root and in order to get rooted I need TWRP...
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
-FliP- said:
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
Click to expand...
Click to collapse
Interesting. Have you tried Androbench?
So which version are You running right now?
Ricky_Karmator said:
So which version are You running right now?
Click to expand...
Click to collapse
I dont even remember to be honest. I think I used the base 3.1 version and got it to detect storage by starting it with the boot adb command. If I run twrp by holding power and vol up, it never detected storage.
I got the same problem with my device X820 6/64 with 19S rom, any TWRP is able to read/write on the internal storage I install TWRP from 3.0 till 3.1.1.1 . What can i do?
Thx
Aj
I re-unlocked my device a few days ago after a long time of using MIUI. Unfortunately, I am now facing a peculiar problem I had not faced the previous time I unlocked my device.
I cannot seem to replace MIUI stock recovery with official TWRP.
If I use fastboot flash recovery xxx.img, the terminal does confirm that the action was successful. Yet, when I reboot into recovery, I am greeted by Mi-Recovery 3.0 instead of TWRP.
My initial thought was that maybe there was some restriction in MIUI that prevented the stock recovery from being replaced, so I flashed RR 5.8.5-FINAL. I still cannot flash TWRP.
Some other info:
The MIUI build I was on: MIUI 9 7.9.21 Global Beta
My phone: RN3 SD 2GB/16GB variant, Fpc fingerprint sensor
The temporary workaround I used to flash RR was directly booting into TWRP using fastbooot boot xxx.img
NOTE: I did a standard wipe (factory reset, followed by wiping System, Data and Cache) when I flashed RR.
As you might imagine, using fastboot to boot into TWRP every time I want to flash something is quite tiring and so if anyone can help me to permanently flash TWRP, I'd be really grateful. Thanks in advance.
PS: If this question has already been answered, then please guide me to the relevant thread and I will take down this one.
This problem also happened to my friend's Redmi Note 3 MTK. I don't know if it's going to work on KENZO or not.
The solution is to flash the TWRP recovery image through fastboot ==> Turn off the device by holding down the power button (DISCONNECT PHONE FROM PC) ==> Boot the recovery using button combinations
This should let you boot into TWRP and stays permanent after the first session
Flashing Through Fastboot/EDL Mode
Flashing Twrp through Fastboot is the permanent way of flashing the recovery...The method is very simple and can be done even on locked bootloader but the thing in locked bootloader is that once you have flashed the TWRP the internal storage is inaccessible because the data is encrypted so you need to wipe->format data ...then press "yes" ..by typing yes the internal storage will be formatted completely so make sure you have a backup ...and do copy the ROM file in SD card for flashing ...after wiping process press install then select SD card and flash the ROM and gapps and enjoy the TWRP...
Refer this link for flashing process youtu.be/rCONN1_IPuU(please add https:// before the link)
Hope this solves your problem...
same problem !! did you find any solution !!!
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.
Hi,
I know I must be doing something dumb, but I am unable to install any rom on my MI A3. I unlocked my bootloader and installed TWRP. I tried installing the havoc os rom on my phone and it wouldn't boot after that (kept going straight into fastboot). So I went back to TWRP and wiped my internal storage and tried installing it again but the same problem kept happening. Now I cannot install any rom ( I have tried Lineage OS and crDroid). I performed the following steps to install a rom:
1. Copy the zip file to internal storage from my laptop
2. Clicked on install
3. Chose the file I just transferred
4. Did the swipe to confirm flash thing
5. It does the flash process without any errors, but then says do you really want to reboot, there is no OS installed.
Even if I try to reboot, it goes straight to fastboot. Checking my internal storage through TWRP, I can see that my system folder is empty.
EDIT: I realised that I need to flash it twice because of the A/B partition thing. I tried doing that too. Now, TWRP no longer says that there is no OS installed and I can see that there are some files in system/. However, I still cannot boot into the OS. It goes straight to fastboot.
EDIT AGAIN: I am able to boot after flashing the stock fastboot rom. So at least I can use my phone for now. However, I would still like to use Havoc OS. Any help is appreciated.
I tried a couple more ROMs. Pixel experience also gets stuck at fastboot and Lineage OS gets stuck in a boot loop
pranav-dahiya said:
Hi,
I know I must be doing something dumb, but I am unable to install any rom on my MI A3. I unlocked my bootloader and installed TWRP. I tried installing the havoc os rom on my phone and it wouldn't boot after that (kept going straight into fastboot). So I went back to TWRP and wiped my internal storage and tried installing it again but the same problem kept happening. Now I cannot install any rom ( I have tried Lineage OS and crDroid). I performed the following steps to install a rom:
1. Copy the zip file to internal storage from my laptop
2. Clicked on install
3. Chose the file I just transferred
4. Did the swipe to confirm flash thing
5. It does the flash process without any errors, but then says do you really want to reboot, there is no OS installed.
Even if I try to reboot, it goes straight to fastboot. Checking my internal storage through TWRP, I can see that my system folder is empty.
EDIT: I realised that I need to flash it twice because of the A/B partition thing. I tried doing that too. Now, TWRP no longer says that there is no OS installed and I can see that there are some files in system/. However, I still cannot boot into the OS. It goes straight to fastboot.
EDIT AGAIN: I am able to boot after flashing the stock fastboot rom. So at least I can use my phone for now. However, I would still like to use Havoc OS. Any help is appreciated.
Click to expand...
Click to collapse
My problem is that I can't install havoc os. I tried all the methods....
Same for me, first time I installed Pixel Experience like you did and worked well, then I tried again and I can't install no more custom ROMs, always getting error 1 in recovery, or not installing TWRP at all. I was able to boot phone again by fastbooting Stock Android 10 v11.0.11.0 April.
But I really enjoyed PE and I wanted to install it.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img